semantic-mcp
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., "@semantic-mcpfind tools for image analysis"
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.
Semantic MCP
Semantic router for MCP ecosystems - Discover, manage, and execute tools across multiple MCP servers with progressive disclosure.
Overview
semantic-mcp is a FastMCP-based MCP server that provides semantic discovery and lifecycle management for other MCP servers. It connects to a discovery service for semantic search and manages server lifecycles locally via ZMQ-based IPC.
LLM Client (Claude/Cline)
│ MCP Protocol
▼
┌─────────────────────────────┐
│ semantic-mcp │
│ (FastMCP MCP Server) │
├─────────────────────────────┤
│ Discovery → mcp-index API │
│ Execution → ZMQ + Sessions │
└─────────────────────────────┘
│ │
▼ ▼
mcp-index MCP Servers
(Elasticsearch) (stdio/http)Related MCP server: one-mcp
Related Projects
mcp-index - Elasticsearch-based semantic discovery service for MCP servers. Required backend for
semantic-mcpto enable semantic search and server registry.
Installation
Option 1: uvx (Recommended)
uvx semantic-mcp serve --transport stdioOption 2: pip/uv
# Install from PyPI
pip install semantic-mcp
# Or with uv
uv pip install semantic-mcp
# Run
semantic-mcp serve --transport stdioOption 3: Docker
docker pull milkymap/semantic-mcp:0.2
docker run -d \
-p 8001:8001 \
-e DISCOVERY_URL=http://your-discovery-service \
-e DISCOVERY_API_KEY=your-key \
milkymap/semantic-mcp:0.2 serve --transport streamable-http --port 8001Option 4: From source
git clone https://github.com/milkymap/semantic-mcp
cd semantic-mcp
uv sync
uv run semantic-mcp serveConfiguration
Environment Variables
Variable | Description | Default |
| Discovery service API URL |
|
| API key for discovery authentication | None |
| Key to decrypt sensitive env vars in server configs | None |
| Path for large result offloading |
|
| Max tokens before content offloading |
|
| Max background tasks in queue |
|
| OpenAI API key (for image descriptions) | None |
MCP Client Integration
Claude Code / Cline (uvx)
Add to your .mcp.json or MCP config:
{
"mcpServers": {
"semantic-mcp": {
"command": "uvx",
"args": ["semantic-mcp", "serve", "--transport", "stdio"],
"env": {
"DISCOVERY_URL": "https://your-discovery-service",
"DISCOVERY_API_KEY": "your-api-key"
}
}
}
}Claude Desktop (Docker)
{
"mcpServers": {
"semantic-mcp": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "DISCOVERY_URL", "-e", "DISCOVERY_API_KEY",
"--add-host=host.docker.internal:host-gateway",
"milkymap/semantic-mcp:0.2", "serve", "--transport", "stdio"
],
"env": {
"DISCOVERY_URL": "http://host.docker.internal:8000",
"DISCOVERY_API_KEY": "your-key"
}
}
}
}Remote HTTP Server
Start the server:
semantic-mcp serve --transport streamable-http --host 0.0.0.0 --port 8001Client configuration:
{
"mcpServers": {
"semantic-mcp": {
"url": "http://your-server:8001/mcp"
}
}
}Available Operations
semantic-mcp exposes a single semantic_router tool with these operations:
Discovery (lightweight)
Operation | Description |
| Search for tools using natural language |
| Search for servers using natural language |
| List all registered servers |
| List tools on a server |
| Get server/tool counts |
Exploration (full details)
Operation | Description |
| Get detailed server information |
| Get full tool schema and description |
Lifecycle
Operation | Description |
| Start or shutdown a server |
| List currently running servers |
Execution
Operation | Description |
| Execute a tool on a running server |
| Check background task status |
| Cancel a running background task |
| List all background tasks |
| Retrieve offloaded content by reference ID |
Workflow
1. DISCOVER search_tools("your need") → Find relevant tools
↓
2. EXPLORE get_server_info(server) → Check capabilities
get_server_tools(server) → List available tools
↓
3. UNDERSTAND get_tool_details(server, tool) → Get full schema (REQUIRED)
↓
4. START manage_server(server, "start") → Start the MCP server
↓
5. EXECUTE execute_tool(server, tool, args) → Run the tool
↓
6. CLEANUP manage_server(server, "shutdown") → Stop when done (optional)Important rules:
Always call
get_tool_detailsbeforeexecute_toolto understand the schemaAlways call
manage_server(start)before executing toolsUse
in_background=truefor long-running operations, thenpoll_task_resultLarge responses are automatically offloaded; use
get_content(ref_id)to retrieve
Architecture
Component | Description |
RuntimeEngine | Core runtime managing ZMQ communication and server lifecycle |
DiscoveryClient | HTTP client for discovery service API |
ContentManager | Large result offloading (text chunking, images) |
BackgroundTasks | Priority queue for async tool execution |
FastMCP | MCP server framework exposing tools to LLMs |
Development
# Install with dev dependencies
uv sync --group dev
# Run tests
uv run pytest tests/ -vLicense
MIT
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.
Latest Blog Posts
- 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/milkymap/semantic-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server