Context7 MCP
for LuumenAI
Version-specific library docs and code examples, pulled in mid-task
When a fix depends on how a library actually behaves in the version you run, Context7 MCP fetches the documentation for it. Use CONTEXT7_MCP_RESOLVE_LIBRARY_ID to pin the right library, then CONTEXT7_MCP_QUERY_DOCS for current docs and code examples. Both are read-only and answer immediately. Connected with an API key.
The Context7 MCP toolbox
2 tools, all read-only. They answer instantly, and every call is logged.
- ReadQuery-docsRetrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.
- ReadResolve-library-idResolves a package/product name to a Context7-compatible library ID and returns matching libraries.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
No. Every one of the 2 tools LuumenAI has for Context7 MCP is read-only, so it can answer questions from Context7 MCP but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to Context7 MCP is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Context7 MCP to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.