Context7 (local) logo

Context7 (local)

Beta

Upstash's Context7 brings version-accurate library documentation into the agent's context from Upstash's API.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx, Docker
Platform
macOS
Publisher
Upstash

How it works

Every agent request passes through Ferentin policy before it reaches Context7 (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @upstash/context7-mcp or docker run -i --rm mcp/context7.

Ferentin's endpoint agent finds Context7 (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Context7 (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Context7 (local)

Upstash's Context7 brings version-accurate library documentation into the agent's context from Upstash's API.

Frequently asked about Context7 (local)

How do I connect Context7 (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Context7 (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Context7 (local) integration generally available?
The Context7 (local) integration is currently beta on Ferentin.