How to Use the Context7 MCP in Cline

Q: How does Context7 supply live library documentation to Cline?

Context7 uses resolvelibrary to find the correct library path and querydocs to pull the documentation. Cline reads these code examples directly, allowing it to write accurate code without web browsing.

Pull up-to-date library code examples directly into Cline using this dedicated MCP Server to build and test code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Context7 MCP to Cline

Create your Vinkius account to connect Context7 to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Context7 with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Pinned versioning for Cline operations

The `resolve_library` tool maps generic library names to their exact deterministic paths in Cline. Cline uses these paths to ensure it references the correct version of a library when writing or editing your local files. This prevents Cline from generating code using mismatching API versions. Cline runs this tool automatically when you mention a framework in the sidebar. This ensures the files Cline creates match your actual project dependencies instead of outdated API specs. You get working code on the first run.

Inserting verified documentation into Cline context

The `query_docs` tool pulls specific code examples and documentation directly into Cline's active context window. Cline reads the returned markdown to understand complex library features before writing test suites or component code. This keeps Cline accurate. This prevents Cline from generating hallucinated methods. You get working code on the first run because Cline references the actual documentation instead of guessing. You do not have to double-check every import.

End-to-end code generation with this MCP Server

The `resolve_library` and `query_docs` tools combine in this MCP Server to allow Cline to fetch documentation, write components, and run tests in a single run. Cline calls the resolution tool to locate the package, queries the documentation, and then writes the code directly to your project. This happens entirely within VS Code. You do not need to copy-paste code from browser tabs. Cline handles the entire process, ensuring your code aligns with the latest library guidelines. Your terminal tests pass without issue.

Setup guide

Set up Context7 MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type context7-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Context7 refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "context7-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Context7. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Context7 now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Context7 MCP in Cline

Context7 uses `resolve_library` to find the correct library path and `query_docs` to pull the documentation. Cline reads these code examples directly, allowing it to write accurate code without web browsing.

Open the Cline sidebar, click the MCP Servers icon, and add the server URL under the Remote Servers tab. You can also add it manually to your `cline_mcp_settings.json` file.

No, Context7 requires an active connection to fetch the latest documentation and code examples. This ensures Cline always receives real-time, accurate library data rather than cached, outdated files.

Standard web search tools return HTML noise and ads. This tool returns structured code examples and clean API documentation, which prevents Cline from wasting context window space on useless web page elements.

All library IDs and documentation queries are sent through an encrypted, zero-trust connection to an ephemeral V8 sandbox. Vinkius processes these requests instantly and destroys the session data immediately after returning the results to Cline.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript