mcp-context
Click on "Install 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., "@mcp-contextsearch for user authentication flow in my project"
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.
mcp-context
Local Model Context Protocol (MCP) server with semantic search (RAG) over code repositories. Exposes the context of multiple projects to external AI clients — Claude.ai, Gemini, Claude Code — eliminating the need to manually repass context at each session.
Stack: Python · FastMCP · Qdrant · sentence-transformers · Next.js · Docker · Cloudflare Tunnel
Prerequisites
Make sure the items below are installed before continuing:
Tool | Minimum version | Check |
Python | 3.11 |
|
Docker | 24.0 |
|
Docker Compose | 2.20 |
|
Node.js | 18.0 |
|
npm | 9.0 |
|
Git | any |
|
cloudflared | any |
|
A Cloudflare account with an active domain is required for remote connectivity (Phase 3).
Related MCP server: MCP Codebase RAG Server
Installation
# 1. Clone the repository
git clone https://github.com/ericlimabr/mcp-context.git
cd mcp-context
# 2. Copy the environment variables file
cp .env.example .env
# 3. Run setup — installs Python dependencies via uv and starts Qdrant
make setupNote on
GITHUB_TOKEN: The.envfile includes aGITHUB_TOKENvariable for read access to repositories. To get this token, go to your GitHub Settings > Developer settings > Personal access tokens. Generate a new token and paste it into your.envfile.
Configuration
1. Environment variables
Edit the .env file created in the previous step:
# Root path where your projects are stored on the machine
PROJECTS_ROOT=/home/your-user/projects
# Access password for the administrative panel
ADMIN_PASSWORD=choose-a-strong-password2. Configure Cloudflare Tunnel
# Authenticate cloudflared with your Cloudflare account
cloudflared tunnel login
# Create the permanent tunnel
cloudflared tunnel create mcp-context
# Associate with your subdomain (replace yourdomain.com)
cloudflared tunnel route dns mcp-context mcp.yourdomain.comCreate cloudflared/config.yml in the project root (this file is gitignored). Replace <id> with the UUID printed by the tunnel create command above:
tunnel: mcp-context
credentials-file: /home/your-user/.cloudflared/<id>.json
ingress:
- hostname: mcp.yourdomain.com
service: http://localhost:17800
- service: http_status:4043. Create the frontend
This step is only needed once. It creates the Next.js project and removes the internal .git/ automatically:
make frontend-setup4. Index the first project
Open the frontend, add a project path and trigger indexing:
make frontend
# Access http://localhost:17801Or run the indexer directly from the terminal:
make indexRunning locally (development)
To start the MCP server with auto-reload (recommended while developing):
make devThis starts Qdrant, the Cloudflare Tunnel, and the MCP server with hot-reload enabled. The server restarts automatically on every file change in server/.
To start all services in the background (MCP server, frontend, tunnel, Qdrant):
make server-devAvailable services:
Service | URL |
MCP Server | |
Frontend (admin + dashboard) | |
Qdrant (API) |
Real-time logs are available in logs/:
tail -f logs/server.log # MCP server
tail -f logs/frontend.log # frontend
tail -f logs/tunnel.log # Cloudflare Tunnel
make qdrant-logs # QdrantTo stop everything:
make stopLocal deploy (all services in containers)
To run the project fully containerized — useful for simulating the production environment or having everything start together with Docker:
# First time: build the images
make prod-build
# Start all containers
make prod-up
# Stop everything
make prod-down
# Real-time logs
make prod-logsWarning: make sure
PROJECTS_ROOTin.envpoints to the correct directory before runningprod-up. The MCP server container mounts that path to access local files.
Make commands
Command | Description |
| First run: installs deps via uv and starts Qdrant |
| Creates the Next.js project in |
| Starts Qdrant + tunnel + MCP server with auto-reload |
| Starts all services in the background |
| Stops all dev services |
| Starts only the MCP server (port 17800) |
| Starts only the Next.js frontend (port 17801) |
| Starts only the Cloudflare Tunnel |
| Runs the indexing worker |
| Starts Qdrant via Docker Compose |
| Stops Qdrant |
| Qdrant logs in real time |
| Build of all Docker images |
| Starts all containers |
| Stops all containers |
| Logs of all containers in real time |
Repository structure
mcp-context/
├── server/ # MCP Server (FastMCP/SSE, port 17800)
│ ├── main.py # Entrypoint and MCP configuration
│ ├── tools/ # MCP tool definitions (planned)
│ ├── resources/ # MCP resource definitions (planned)
│ └── embeddings.py # Local embedding model loading (planned)
├── indexer/ # Project indexing worker (planned)
│ ├── worker.py # Orchestrates indexing
│ ├── chunker.py # Function-scope chunking
│ └── qdrant_client.py # Qdrant client abstraction
├── apps/
│ └── frontend/ # Next.js app — admin panel + dashboard (port 17801)
│ # Generated by make frontend-setup
├── cloudflared/ # Cloudflare Tunnel config (gitignored)
│ └── config.yml
├── docs/
│ ├── ARCHITECTURE.md # Detailed system architecture
│ ├── DECISIONS.md # Architecture decisions
│ ├── ENDPOINTS.md # Endpoints documentation
│ └── ROADMAP.md # Implementation phases
├── logs/ # Service logs in dev (gitignored)
├── .pids/ # Process PIDs in dev (gitignored)
├── qdrant_data/ # Persisted Qdrant data (gitignored)
├── config.json # Project configuration (gitignored)
├── .env # Environment variables (gitignored)
├── .env.example # Environment variables template
├── docker-compose.yml # Qdrant for development
├── docker-compose.prod.yml # All services for local deploy
├── Makefile # Command shortcuts
├── pyproject.toml # Python project and dependencies (uv)
├── CONTEXT.md # Project context for LLMs
└── README.md # This fileKnown limitations
The server depends on the local machine being on to work remotely via Cloudflare Tunnel
The Qdrant index reflects the state of the code at the time of the last indexing — configure a
post-commithook to keep the index updated automatically after each commitBinary files, images and assets are not indexed
The embedding model (
jina-embeddings-v2-base-code, ~160 MB) is automatically downloaded on the first run viasentence-transformers
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceLocal-first MCP server for semantic + keyword hybrid code search. Zero external services, no API keys required.Last updatedMIT
- Flicense-qualityDmaintenanceProvides semantic vector search over local codebases via MCP, enabling hybrid search (dense + sparse + RRF) for any MCP client like GitHub Copilot or Claude Desktop.Last updated8
- Flicense-qualityBmaintenanceA local MCP server that enables LLM clients like Claude to perform semantic code search and answer questions about a codebase using tree-sitter parsing and sqlite-vec vector storage.Last updated
- -license-qualityDmaintenanceMCP server for semantic code search and explanation. Allows AI agents to search, ask questions, and manage memory about a codebase with local embeddings and LLM integration.Last updated
Related MCP Connectors
An MCP server that gives your AI access to the source code and docs of all public github repos
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ericlimabr/mcp-context'
If you have feedback or need assistance with the MCP directory API, please join our Discord server