smartmcp
PyPI package: smartmcp-router (CLI: )
Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
PyPI package: smartmcp-router (CLI: )
A semantic tool routing proxy for AI agents. Indexes all MCP tools with FAISS embeddings, surfaces only what's relevant. 97% context reduction.
smartmcpIntelligent MCP tool routing that reduces context bloat by serving only the tools your AI actually needs.
In my own setup with 8 MCP servers and 224 tools, every AI request was loading ~66,000 tokens of tool schemas before the model even started thinking. With smartmcp, that dropped to ~1,600 tokens. A 97% reduction on every request.
Token counts estimated at ~4 characters per token. Actual counts vary by model tokenizer.
Most MCP setups expose every tool from every server to the AI at once. With 5+ servers, that's 50–200+ tool schemas crammed into the context window before the AI even starts thinking. smartmcp fixes this.
smartmcp is a proxy MCP server that sits between your AI client and your upstream MCP servers. It indexes all available tools using semantic embeddings and exposes a fixed two-tool surface: search_tools to discover the right upstream tool and call_discovered_tool to invoke it. The tool list never changes mid-session, so smartmcp works even with clients that ignore notifications/tools/list_changed.
AI Client (Claude Desktop / Cursor / your agent)
↕ stdio
smartmcp (proxy server)
↕ stdio (one connection per server)
[github] [filesystem] [google-workspace] [git] [memory] [puppeteer] ...
smartmcp uses a two-phase flow: discover, then call.
search_tools and call_discovered_tool. It calls search_tools with a natural language query, for example search_tools({ "query": "create a GitHub issue" }).search_tools returns structured JSON. Each match includes the exact target identifier, the upstream server and name, the description, the relevance score, and the full upstream input_schema.input_schema from the search response and constructs valid arguments.call_discovered_tool({ "target": "<exact target from search>", "arguments": { ... } }). smartmcp resolves the target (for example github__create_issue), routes the call to the correct upstream server, and returns the result. Arguments are forwarded to the upstream tool unchanged.The intelligence is in the discovery step. The AI still does its own parameter construction based on the schema returned by search_tools. smartmcp just narrows down which tools it sees, and the static two-tool surface means the flow works even with clients that snapshot tools/list once and never refresh.
pip install smartmcp-router
Requires Python 3.10+.
Recommended on macOS, especially Apple Silicon: install with pipx so SmartMCP gets an isolated environment that cannot inherit a stale torch or torchvision from other projects. This avoids the most common class of install issues (see Troubleshooting).
pipx install smartmcp-router
Create a smartmcp.json with your upstream MCP servers (same format as Claude Desktop / Cursor config):
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/home/user/documents"]
},
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
},
"slack": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-slack"],
"env": {
"SLACK_BOT_TOKEN": "xoxb-your-token-here"
}
}
},
"top_k": 5,
"embedding_model": "all-MiniLM-L6-v2"
}
Add smartmcp as your single MCP server entry. It now manages all your upstream servers defined in smartmcp.json.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"smartmcp": {
"command": "smartmcp",
"args": ["--config", "/path/to/smartmcp.json"]
}
}
}
Add to your .cursor/mcp.json:
{
"mcpServers": {
"smartmcp": {
"command": "smartmcp",
"args": ["--config", "/path/to/smartmcp.json"]
}
}
}
Point your MCP client at smartmcp the same way you would any stdio MCP server:
smartmcp --config /path/to/smartmcp.json
Your AI now sees two tools: search_tools and call_discovered_tool. When it needs to do something, it searches and then invokes:
AI calls:
search_tools({ "query": "read files from disk" })smartmcp returns: JSON with up to top-k matches. Each match includes a
target(such asfilesystem__read_file), the upstream tool'sdescription, and the fullinput_schema.AI sees: The complete parameter definitions inside each match. It picks the right one, builds
argumentsagainst that match'sinput_schema, and callscall_discovered_tool({ "target": "filesystem__read_file", "arguments": { ... } }).smartmcp proxies the call to the filesystem server unchanged and returns the result.
search_tools.search_tools includes the upstream input_schema, so the AI can construct calls correctly without any further tools/list refresh.notifications/tools/list_changed (such as Qwen Code and similar agents).torchvision::nms does not exist or Could not import module 'BertModel'If smartmcp crashes at startup with one of these errors:
RuntimeError: operator torchvision::nms does not exist
ModuleNotFoundError: Could not import module 'BertModel'. Are this object's requirements defined correctly?
This is a torch / torchvision ABI mismatch in your Python environment, not a smartmcp bug. SmartMCP itself does not depend on torchvision. The mismatch usually appears after pip install --upgrade walks transitive dependencies forward (newer sentence-transformers -> newer transformers -> newer torch) while leaving an older torchvision in place. Newer transformers eagerly imports the vision pipeline during BertModel autoload, so the mismatched torchvision extension fails to register the nms operator and the whole import chain breaks. Apple Silicon users see this more often because mixing arm64 and x86_64 wheels makes the mismatch more likely.
Try these fixes in order:
Remove torchvision. SmartMCP does not need it:
pip uninstall -y torchvision
Reset the torch stack so torch and torchvision share an ABI:
pip uninstall -y torch torchvision torchaudio
pip install --upgrade torch
Recreate a clean venv (most reliable on Apple Silicon):
python3 -m venv ~/.venvs/smartmcp
source ~/.venvs/smartmcp/bin/activate
pip install --upgrade pip
pip install smartmcp-router
Installing with pipx (see Installation) avoids this class of issue altogether by giving SmartMCP its own isolated environment.
smartmcp is early-stage and actively improving. Contributions are welcome, especially around search accuracy, embedding strategies, and support for new transports.
If you have ideas, find bugs, or want to add features, open an issue or submit a PR on GitHub.
A semantic tool routing proxy for AI agents. Indexes all MCP tools with FAISS embeddings, surfaces only what's relevant. 97% context reduction.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Smart stdio पर लोकल चलता है।
पिछली जाँच 2026-10-28 को हुई। A semantic tool routing proxy for AI agents. Indexes all MCP tools with FAISS embeddings, surfaces only what's relevant. 97% context reduction.