Context7 MCP integration for AI agents.
Connect AI agents to Context7 through 2 structured actions, including get documentation context and search libraries. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Context7 integration exposes
The Context7 Agent App exposes 2 provider-backed actions for developer tools and ai work. Its current contract lets an authorized agent retrieve relevant context7 documentation and code snippets for a library and search context7 for libraries ranked against a question or task. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Context7 account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Context7 capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_documentation_contextREADRetrieve relevant Context7 documentation and code snippets for a library.
INPUTS: libraryId / query / fast
search_librariesREADSearch Context7 for libraries ranked against a question or task.
INPUTS: libraryName / query / fast
INPUT CONTRACTS
Know what the action needs before it runs.
get_documentation_context
libraryIdREQUIRED- The Context7 library ID, such as /vercel/next.js.
queryREQUIRED- The original question or task used to rank results by relevance.
fastOPTIONAL- Whether to skip LLM reranking and return faster vector-search results.
search_libraries
libraryNameREQUIRED- The library name to search for.
queryREQUIRED- The original question or task used to rank results by relevance.
fastOPTIONAL- Whether to skip LLM reranking and return faster vector-search results.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Documentation Context
Retrieve relevant Context7 documentation and code snippets for a library. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_documentation_contextVerify with Search Libraries
Search Context7 for libraries ranked against a question or task. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
search_librariesSAFETY BOUNDARY
Operate Context7 with explicit limits
- Authorize Context7 with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Context7 data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Context7 rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Context7 task completed successfully.
CONNECTION MODEL
API key
Context7 API key sent as a Bearer token. Create and manage keys in the Context7 dashboard: https://context7.com/dashboard.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Context7.