Which AI clients can use the Context7 MCP server?

27 AI clients, including Cursor, VS Code, and Claude. Each connects to Context7 as a remote MCP server through Runlayer, which adds identity, policy, scanning, and audit to every call.

Which Context7 tools are available?

Context7 exposes 2 tools, including Query docs, Resolve library ID. 2 only read data. Admins choose which ones each group can call.

How does Context7 authenticate?

Sign in the way Context7 requires. Runlayer holds the credentials so they stay out of the client’s configuration.

Integrations / MCP servers

Context7

Give the model current, version-specific docs and code examples for the libraries you use.

Book a demo View documentation

Tools

2 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

Search 2 tools

Query docs
Read only
Tool name: query-docs
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.
Resolve library ID
Read only
Tool name: resolve-library-id
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.

Compatibility

Connect Context7 to the clients your teams already use

27 AI clients can connect to Context7 through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Context7 through Runlayer?

One approved path

Approve Context7 once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.