Connect Context7 docs

Agents read current, version-specific documentation for thousands of libraries and frameworks; no account or key is needed, just press Add.

Once Context7 docs is connected, an agent can look up the current documentation for a library or framework instead of guessing from memory, pull the section about a specific topic (say "middleware" for Express or "server actions" for Next.js), and tell you which version it read. That cuts down on made-up method names and outdated examples.

Before you start

Nothing on the Context7 side. The public server at mcp.context7.com works without an account.
Requests without a key share a public rate limit. Context7 offers free keys at context7.com/dashboard for higher limits, but this integration does not take one; the shared limit is usually fine for a team.
You must be an owner or admin of the woble workspace.

Connect it

Open Marketplace, choose the Integrations tab, find Context7 docs and press Add.
There is nothing to sign in to and nothing to paste. Press Save.
The card says Connected and the agent panel lists two tools: one that resolves a library name to a Context7 id, and one that fetches documentation for that id, optionally narrowed to a topic.

Or ask an agent

Type @ruby connect Context7 docs in any chat. The same connect card appears in the conversation. Only owners and admins can complete it.

Try it

"@atlas check the Context7 docs for Drizzle ORM and show me how to write a transaction with the current API."
"@atlas which version of the Tailwind docs did you read, and does it still support the JIT flag?"

If it does not connect

"Rate limited" or "too many requests": the shared public limit is exhausted for the moment. Wait a minute and try again.
The library is not found: Context7 indexes public projects, and some names differ from the npm or PyPI name. Ask the agent to search with the GitHub owner/repo name. Missing libraries can be submitted at context7.com.
The server is down or unreachable: press Test connection in Marketplace → Connected. If it keeps failing, Remove and add it again; there is no token to expire, so a persistent failure is on the Context7 side.

Disconnect

Marketplace → Connected → Context7 docs → Remove. Agents lose the documentation tools immediately. Nothing was stored, so there is nothing else to clean up.