Trigger on event
- Listen for a new event
- Parse and validate the payload
- Take an action with the linked tool
2 tools available
Context7 MCP pulls up-to-date, version-specific documentation and code examples straight from the source — and places them directly into your prompt
Connect Context7 MCP to Definable to automate repetitive tasks, sync data with the rest of your stack, trigger on real-world events. Personas call Context7 MCP's 2 tools directly from chat or scheduled flows. You can wire it into any persona to read, write, and react when an event fires.
Every Context7 MCP action below is a callable tool any Definable persona can invoke.
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'query-docs' to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.
Anything Context7 MCP exposes through its API. Common developer tools & devops workflows on Definable include automate repetitive tasks, sync data with the rest of your stack, trigger on real-world events. Personas can call any of the 2 Context7 MCP tools directly, then chain the result into another integration without you writing code.
Context7 MCP uses API_KEY on Definable. You connect once from the integrations page, scoped to the permissions you choose, and from then on any persona that has the integration enabled can act on your behalf. Tokens are encrypted at rest and rotated automatically.
Yes — every Definable plan, including Starter, includes access to all 2 Context7 MCP tools. You only need a separate Context7 MCP subscription if Context7 MCP itself charges per seat or per API call.
Every call from a persona to Context7 MCP is logged with the user, persona, prompt, and response. Tokens never leave Definable's secrets vault, scopes are configurable per persona, and you can revoke access at any time from the integration page.
Sign up for Definable, open the integrations page, find Context7 MCP, and connect via OAuth or API key. You can immediately attach Context7 MCP to any persona and start running workflows. The free Starter plan includes 5,000 credits/month.
Definable exposes all 2 Context7 MCP actions as callable tools — including `Query-docs`, `Resolve-library-id`. Each tool gets a typed parameter schema so personas know exactly how to call it.
Wire it up in minutes. No coding required.