MCPFind
A context-efficient proxy that replaces individual tool schemas with three meta-tools for semantic search, schema retrieval, and tool routing. It enables agents to manage hundreds of backend tools while maintaining a constant context footprint of approximately 500 tokens.
README
MCPFind
Context-efficient MCP tool proxy with semantic search. MCPFind sits between any MCP client and your backend MCP servers, replacing hundreds of tool schemas in the agent's context with just 3 meta-tools (~500 tokens).
Agent (Claude Desktop, Cursor, Claude Code, etc.)
│ Sees only: search_tools, get_tool_schema, call_tool
▼
MCPFind Proxy
├── Vector search over all tool descriptions
├── Per-agent MFU cache for personalized ranking
└── Routes calls to the correct backend server
│
├──▶ Gmail MCP Server
├──▶ GitHub MCP Server
├──▶ Slack MCP Server
└──▶ ... N servers
Why
As MCP toolspaces grow, every tool schema gets dumped into the agent's context:
| Tools | Context tokens | Effect |
|---|---|---|
| 10 | ~2K | Fine |
| 50 | ~10K | Manageable |
| 200 | ~40K | Agent picks wrong tools |
| 1000 | ~200K | Unusable |
MCPFind keeps context at ~500 tokens regardless of how many tools exist behind it. Agents discover tools via semantic search, pull schemas on demand, and call tools through the proxy.
Install
# With uv (recommended)
uv tool install mcpfind
# With pip
pip install mcpfind
No API key needed — MCPFind uses local embeddings by default.
Quick Start
1. Run the setup wizard
The easiest way to get started:
mcpfind setup
This walks you through choosing an embedding provider and adding popular MCP servers (GitHub, Slack, Filesystem, PostgreSQL, Brave Search, Playwright, and more). It generates a mcpfind.toml config file for you.
Or create a config file manually
Create mcpfind.toml:
[proxy]
# Uses local embeddings by default — no API key needed
embedding_provider = "local" # or "openai"
embedding_model = "all-MiniLM-L6-v2" # or "text-embedding-3-small" for openai
mfu_boost_weight = 0.15
mfu_persist = true
default_max_results = 5
[[servers]]
name = "github"
command = "uvx"
args = ["mcp-server-github"]
env = { GITHUB_TOKEN = "${GITHUB_TOKEN}" }
[[servers]]
name = "filesystem"
command = "uvx"
args = ["mcp-server-filesystem", "/path/to/allowed/dir"]
2. Verify your setup
# List all tools discovered from your backend servers
mcpfind list-tools --config mcpfind.toml
# Test semantic search
mcpfind search "create a pull request" --config mcpfind.toml
3. Run the proxy
mcpfind serve --config mcpfind.toml
This starts MCPFind as a stdio MCP server. Point your MCP client at it instead of individual servers.
Adding MCP Servers
Each backend server is a [[servers]] entry in your config file:
[[servers]]
name = "gmail" # Unique name (used in search results and call_tool)
command = "uvx" # Command to launch the server
args = ["mcp-gmail"] # Arguments passed to the command
env = { GMAIL_TOKEN = "${GMAIL_TOKEN}" } # Environment variables (supports ${VAR} expansion)
Examples
GitHub:
[[servers]]
name = "github"
command = "uvx"
args = ["mcp-server-github"]
env = { GITHUB_TOKEN = "${GITHUB_TOKEN}" }
Filesystem:
[[servers]]
name = "filesystem"
command = "uvx"
args = ["mcp-server-filesystem", "/home/user/documents"]
Slack:
[[servers]]
name = "slack"
command = "uvx"
args = ["mcp-server-slack"]
env = { SLACK_BOT_TOKEN = "${SLACK_BOT_TOKEN}" }
Custom / local server:
[[servers]]
name = "my-server"
command = "python"
args = ["-m", "my_mcp_server"]
env = { MY_API_KEY = "${MY_API_KEY}" }
Client Configuration
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"mcpfind": {
"command": "mcpfind",
"args": ["serve", "--config", "/path/to/mcpfind.toml"],
"env": {
"GITHUB_TOKEN": "ghp_..."
}
}
}
}
Claude Code
Add to your .mcp.json:
{
"mcpServers": {
"mcpfind": {
"command": "mcpfind",
"args": ["serve", "--config", "/path/to/mcpfind.toml"]
}
}
}
Cursor
Add to your MCP settings:
{
"mcpServers": {
"mcpfind": {
"command": "mcpfind",
"args": ["serve", "--config", "/path/to/mcpfind.toml"]
}
}
}
How It Works
MCPFind exposes exactly 3 tools to the agent:
-
search_tools— Find relevant tools by natural language query (e.g., "send an email"). Returns tool names, servers, and descriptions ranked by semantic similarity + usage frequency. -
get_tool_schema— Pull the full input schema for a specific tool before calling it. Keeps schemas out of context until actually needed. -
call_tool— Execute a tool on a backend server. MCPFind validates and routes the call to the correct server.
Agent workflow
Agent: search_tools("send an email")
→ [{"server": "gmail", "name": "send_email", "score": 0.94}, ...]
Agent: get_tool_schema(server="gmail", tool="send_email")
→ {"type": "object", "properties": {"to": ..., "subject": ..., "body": ...}}
Agent: call_tool(server="gmail", tool="send_email", arguments={...})
→ "Email sent!"
MFU Cache
MCPFind tracks which tools each agent uses most frequently. Frequently used tools get a ranking boost in search results via the mfu_boost_weight config option (default: 0.15). This means 85% of the ranking comes from semantic similarity and 15% from usage frequency.
Set mfu_persist = true to save usage data across restarts (stored in mfu.db).
Configuration Reference
[proxy]
embedding_provider = "local" # "local" (default) or "openai"
embedding_model = "all-MiniLM-L6-v2" # Model name (provider-specific)
mfu_boost_weight = 0.15 # Frequency boost weight (0.0-1.0)
mfu_persist = true # Persist usage data to SQLite
default_max_results = 5 # Default number of search results
[[servers]]
name = "server-name" # Required: unique identifier
command = "command" # Required: executable to launch
args = ["arg1", "arg2"] # Optional: command arguments
env = { KEY = "value" } # Optional: environment variables (${VAR} expansion supported)
CLI Reference
# Interactive setup wizard
mcpfind setup
# Start the proxy server (stdio MCP transport)
mcpfind serve --config mcpfind.toml
# List all discovered tools from backend servers
mcpfind list-tools --config mcpfind.toml
# Test semantic search
mcpfind search "query" --config mcpfind.toml --max-results 10
Development
# Clone and install
git clone https://github.com/jcgs2503/mcp-lens.git
cd mcp-lens
uv sync
# Run tests
uv run pytest -v
# Lint and format
uv run ruff check .
uv run black --check .
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。