stdio-context7
Provides access to Express documentation and code examples, allowing users to fetch up-to-date library documentation.
Provides access to MongoDB documentation and code examples, allowing users to fetch up-to-date library documentation.
Provides access to Next.js documentation and code examples, allowing users to fetch up-to-date library documentation.
Provides access to React documentation and code examples, allowing users to fetch up-to-date library documentation.
Provides access to Supabase documentation and code examples, allowing users to fetch up-to-date library documentation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@stdio-context7 what's the latest documentation for React?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
STDIO Context7 MCP Server
Alternative Context7 MCP implementation built to work with Claude Code via Docker MCP Toolkit
An alternative implementation of the Context7 MCP server, designed to work seamlessly with Claude Code via Docker MCP Toolkit. This version provides up-to-date library documentation and code examples through STDIO transport, addressing connectivity issues with the original Context7 server in Docker MCP environments.
π Claude Code Plugin
This repository is also a Claude Code plugin marketplace. Installing the plugin registers the stdio-context7 MCP server with Claude Code, Cowork, and the Claude desktop app chat.
/plugin marketplace add tobymarsden/stdio-context7-mcp-server
/plugin install stdio-context7@stdio-context7-mcp-serverOr, for local development of the plugin:
claude --plugin-dir /path/to/stdio-context7-mcp-serverThe plugin runs a self-contained bundle, plugin/server.cjs, with node ${CLAUDE_PLUGIN_ROOT}/plugin/server.cjs. It needs only Node.js 20 or newer on the PATH: no Docker, no npx, no network install. Rebuild the bundle after changing src/ with:
npm run build:pluginTo use a Context7 API key for higher rate limits, set CONTEXT7_API_KEY in the environment the Claude app inherits. The key is optional.
The plugin files are:
.claude-plugin/plugin.json- plugin manifest.claude-plugin/marketplace.json- marketplace manifest.mcp.json- MCP server definition used by the pluginplugin/server.cjs- bundled server (built fromsrc/bynpm run build:plugin)
Differences from the upstream npm package
This fork fixes three things that stop @dolasoft/stdio-context7-mcp-server@1.0.1 working as a plugin MCP server:
resolve-library-idsent?q=to the Context7 search API, which now requires?query=and returned 400, surfaced as "Library not found".The server exited after 5 minutes idle. Hosts such as the Claude desktop app keep stdio servers alive between calls and do not restart them, so the tools disappeared. The idle timeout is now off unless
INACTIVITY_TIMEOUT_MSis set.Log output went to stdout, which is the MCP JSON-RPC channel. All console output now goes to stderr when using the stdio transport.
Related MCP server: Context7 MCP Server
π― Purpose
This is an alternative MCP server to the original Context7, specifically created to solve connectivity issues with Docker MCP Toolkit. Built with the specific goals of:
Docker MCP Toolkit Compatible: Works reliably with Claude Code via Docker Desktop's MCP infrastructure (where the original doesn't)
Claude Code Optimized: First-class support for Claude Code IDE workflows
Enhanced STDIO Transport: Direct, efficient communication via standard input/output
Production-Ready Security: Enterprise-grade Docker image with SBOMs, provenance, and signing support
Universal Compatibility: Works with all MCP-compatible AI assistants (Claude, Cursor, Windsurf, etc.)
β¨ Features
π³ Docker MCP Toolkit Native: Built for Docker Desktop MCP integration
π€ Claude Code First: Optimized for Claude Code IDE workflows
π Library Resolution: Resolve library names to Context7-compatible IDs
π Documentation Retrieval: Fetch up-to-date documentation and code examples
π― Topic Filtering: Focus on specific topics within libraries
β‘ STDIO Transport: Fast, local integration with MCP clients
π³ Production Docker: Multi-arch with SBOMs, provenance, and security hardening
π Enterprise Security: Non-root user, minimal attack surface, Alpine Linux base
π Multi-Architecture: Supports amd64 and arm64 platforms (Intel, AMD, Apple Silicon)
π Universal Compatibility: Works with Cursor, Windsurf, and other MCP clients
Installation
Prerequisites
Node.js >= 20.8.1
npm >= 10.0.0
Docker (optional, for containerized deployment)
npm Installation
npm install -g @dolasoft/stdio-context7-mcp-serverDocker Installation
# Pull the official image
docker pull dolasoft/stdio-context7-mcp:latestUsage
CLI Arguments
--api-key <key>: Context7 API key for authentication (optional, get one at context7.com/dashboard for higher rate limits)
MCP Client Configuration
π³ Docker MCP Toolkit (Recommended)
This server is built for Docker MCP Toolkit and integrates seamlessly with Claude Code. Using Docker provides the most reliable and secure deployment option.
For Docker Desktop MCP:
{
"mcpServers": {
"stdio-context7": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--stop-timeout",
"10",
"dolasoft/stdio-context7-mcp:latest"
]
}
}
}π€ Claude Code
This server is optimized for Claude Code via Docker MCP Toolkit. Add to your MCP configuration:
{
"mcpServers": {
"stdio-context7": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--stop-timeout",
"10",
"dolasoft/stdio-context7-mcp:latest"
]
}
}
}With API Key (for higher rate limits):
{
"mcpServers": {
"stdio-context7": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--stop-timeout",
"10",
"dolasoft/stdio-context7-mcp:latest",
"--api-key",
"YOUR_CONTEXT7_API_KEY"
]
}
}
}Get your free API key at context7.com/dashboard
Pro tip: Add this to your CLAUDE.md for automatic Context7 usage:
## Context7 Integration
Use the stdio-context7 MCP server for library documentation and code examples.
Always use `resolve-library-id` first, then `get-library-docs`.Other MCP Clients
For Claude Desktop, Cursor, Windsurf, or any MCP-compatible client:
{
"mcpServers": {
"stdio-context7": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--stop-timeout",
"10",
"dolasoft/stdio-context7-mcp:latest"
]
}
}
}With API Key:
{
"mcpServers": {
"stdio-context7": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--stop-timeout",
"10",
"dolasoft/stdio-context7-mcp:latest",
"--api-key",
"YOUR_CONTEXT7_API_KEY"
]
}
}
}Available Tools
1. resolve-library-id
Resolves a general library name into a Context7-compatible library ID.
Parameters:
libraryName(required): The name of the library to search for
Example:
{
"libraryName": "react"
}Response:
Found library: React
Library ID: /facebook/react
Description: A JavaScript library for building user interfaces2. get-library-docs
Fetches documentation for a library using a Context7-compatible library ID.
Parameters:
context7CompatibleLibraryID(required): Exact library ID (e.g.,/mongodb/docs)topic(optional): Focus docs on a specific topic (e.g., "routing", "hooks")tokens(optional): Max tokens to return (default: 5000, minimum: 1000)
Example:
{
"context7CompatibleLibraryID": "/facebook/react",
"topic": "hooks",
"tokens": 3000
}Response:
# React Documentation
A JavaScript library for building user interfaces
## Topic: hooks
This section focuses on hooks in React.
## Getting Started
Here you would find comprehensive documentation and examples for React.Using with AI Assistants
In Cursor or Claude Desktop
Simply mention the library in your prompt and ask the AI to use context7:
Create a Next.js middleware that checks for a valid JWT. use context7Or reference a specific library ID:
Implement authentication with Supabase. use library /supabase/supabaseSupported Libraries
This server uses the real Context7 API and supports all libraries available in the Context7 ecosystem. Simply use the resolve-library-id tool to find any library, including:
React (
/facebook/react) - UI libraryNext.js (
/vercel/next.js) - React frameworkExpress (
/expressjs/express) - Node.js web frameworkMongoDB (
/mongodb/docs) - Database documentationSupabase (
/supabase/supabase) - Backend platformAnd thousands more...
The server fetches up-to-date documentation directly from Context7's live API.
Security
The Docker image is built with enterprise-grade security:
Non-root user (UID 1001)
Multi-architecture: amd64, arm64
SBOMs & Provenance: Full supply chain transparency
Alpine Linux: Minimal attack surface
Regular updates: Automated security patches
Troubleshooting
Server not responding?
Verify Docker is running:
docker psCheck MCP client logs for connection errors
Ensure correct image:
docker pull dolasoft/stdio-context7-mcp:latest
Library not found?
Always use
resolve-library-idfirst to find the correct library IDEnsure library ID format is correct (e.g.,
/org/repo)
License
MIT License - see LICENSE file for details
Acknowledgments
Powered by Context7 API by Upstash
Built with Model Context Protocol
Built for the MCP community and Docker MCP Toolkit
Available Tools
2 toolsget-library-docsB
Fetches documentation for a library using a Context7-compatible library ID.
Inputs: context7CompatibleLibraryID (required), topic, tokens.
resolve-library-idB
Resolves a general library name into a Context7-compatible library ID.
Inputs: libraryName (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one resolves a library name into an ID, the other fetches docs using that ID. There is no overlap or ambiguity between them.
Both tools follow the same verb_noun pattern with snake_case (resolve-library-id, get-library-docs). Naming is consistent and predictable.
With only 2 tools, the server feels thin for a general-purpose documentation service, especially as it may need more discovery tools. However, for a focused workflow (resolve then fetch), this count is borderline acceptable.
The core workflow of resolving a library ID and fetching its docs is covered without dead ends. A minor gap is lack of searching or listing libraries, but the stated purpose is fetch docs, so the surface is nearly complete.
Maintenance
Related MCP Connectors
@latest documentation and code examples to 9000+ libraries for LLMs and AI code editors in a singlβ¦
Find open-source libraries and fetch contextual code snippets by version to accelerate developmentβ¦
Provide your AI coding tools with token-efficient access to up-to-date technical documentation forβ¦
Versioned documentation registry and semantic search for AI tools and coding assistants.
Related MCP Servers
- AlicenseCqualityDmaintenanceProvides real-time access to up-to-date library documentation and code examples for any programming library. Helps AI coding assistants deliver accurate, current information instead of relying on outdated training data.110 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceProvides access to the Context7 API for searching up-to-date documentation, code examples, API references, and troubleshooting help across thousands of programming libraries and frameworks. Enables developers and AI agents to quickly find accurate documentation, compare libraries, get migration guides, and resolve coding issues.-
- AlicenseNot gradedqualityDmaintenanceProvides LLMs with up-to-date, version-specific documentation and code examples from library sources directly into prompts, eliminating outdated code generation and hallucinated APIs.MIT
- AlicenseNot gradedqualityDmaintenanceProvides up-to-date, version-specific documentation and code examples for software libraries directly to LLMs, enabling resolution of library identifiers and retrieval of relevant documentation with code snippets.MIT