Context7 MCP Server Stack
Description
# Context7 MCP Server Stack A multi-server Message Control Protocol (MCP) implementation with Caddy reverse proxy, providing real-time documentation access and context preservation across coding sessions. ## Features - Real-time documentation access via Context7 MCP - Web search…
About
# Context7 MCP Server Stack A multi-server Message Control Protocol (MCP) implementation with Caddy reverse proxy, providing real-time documentation access and context preservation across coding sessions. ## Features - Real-time documentation access via Context7 MCP - Web search capabilities via BraveSearch MCP -…
Details
- Author
- james-simmonds
- Downloads
- 165
- Categories
- Remote MCP, Other
Jump to
- Real-time documentation access via Context7 MCP
- Web search capabilities via BraveSearch MCP
- Context preservation across coding sessions
- Major AI coding assistant integration support
- Scalable Docker-based architecture with Caddy reverse proxy
- Easy extensibility for additional MCP servers
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Context7 MCP Server StackCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Build and start the stack with docker-compose up -d, then check overall health at http://localhost/health and individual server health at /context7/health and /bravesearch/health. Stop the stack with docker-compose down. For VS Code integration, add the provided configuration to .vscode/settings.json.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"context7 mcp server stack": {
"context7-mcp-server": {
"command": "docker",
"args": [
"ps"
]
}
}
}
}McpServers
{
"context7-mcp-server": {
"command": "docker",
"args": [
"ps"
]
}
}Context7 MCP Server Stack
A multi-server Message Control Protocol (MCP) implementation with Caddy reverse proxy, providing real-time documentation access and context preservation across coding sessions.
Features
- Real-time documentation access via Context7 MCP
- Web search capabilities via BraveSearch MCP
- Context preservation across sessions
- Major AI coding assistant integration support
- Scalable Docker-based architecture with Caddy reverse proxy
- Easy extensibility for additional MCP servers
Quick Start
1. Build and start the stack:
docker-compose up -d
2. Check server status:
curl http://localhost/health
3. Access individual MCP servers:
# Context7 MCP
curl http://localhost/context7/health
# BraveSearch MCP
curl http://localhost/bravesearch/health
4. Stop the stack:
docker-compose down
Integration
VS Code Configuration
// .vscode/settings.json
"mcp.servers": {
"Context7": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@upstash/context7-mcp@latest"],
"protocolVersion": 1
}
}
Health Checks
Each server includes built-in health checks that run every 30 seconds. You can monitor the container health status using:
docker ps
Architecture
System Components
1. Caddy Reverse Proxy
- Routes traffic to appropriate MCP servers
- Handles path-based routing (/context7, /bravesearch)
- Provides unified health check endpoint
2. Context7 MCP Server
- Runs on port 7681 internally
- Provides documentation and context services
3. BraveSearch MCP Server
- Runs on port 7682 internally
- Provides web search capabilities
All services use a dedicated Docker network (mcp-net) for enhanced security and isolation.
Adding New MCP Servers
To add a new MCP server to the stack:
1. Create a new directory for your MCP server
2. Add a Dockerfile and implementation
3. Add the service to docker-compose.yml
4. Update the Caddyfile with a new route
5. Rebuild and restart the stack
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
