MCP Zero Ddfa0050

MCP搜索检索

提供方 jorgecotillo

搜索检索 stdio · 本地进程 Token 社区 / 第三方 VS Code
查看接入方式

MCP-Zero是一种用于AI代理语义工具发现的算法,通过两阶段分层搜索和嵌入技术,实现高效、低延迟的工具匹配。

一句话选型结论

按资料字段整理

MCP Zero Ddfa0050 属于搜索检索类 MCP 服务器,stdio · 本地进程,Token,可直接接入 VS Code,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类搜索检索 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

搜索检索
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

AI工具发现Python本地部署语义搜索嵌入技术两阶段搜索MCP协议

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
pip install -r requirements.txt

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
联网搜索取证

让模型查最新资料并给出出处。

资料聚合

把一个主题的网页、文档集中抓回来整理。

情报与竞品检索

按关键词持续检索行业动态和竞品信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在搜索检索场景里让模型直接调用外部能力的人。
  • 已经在用 VS Code 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Zero Ddfa0050当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Brave Search 433812ff 2 未标注 未标注 无 2026-05-17
Sequentialthinking 1 SSE · 服务端推送 远程部署 有 2026-05-18
Baidu Netdisk 未标注 未标注 未标注 无 2026-05-17
ragflow 未标注 stdio · 本地进程 本地部署 有 2026-04-11
mindsdb (430e18) 未标注 未标注 未标注 有 2026-05-17

服务器档案

搜索检索
字段来自项目仓库与公开索引,中文说明由本站标注
提供方jorgecotillo上游标注的维护方 jorgecotillo
分类搜索检索本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

9.1 KB
来自项目仓库与上游目录的原文,未做删改

MCP-Zero: Active Tool Discovery for AI Agents

Standalone demonstration of the MCP-Zero algorithm for semantic tool discovery with real MCP servers

Author: Jorge Cotillo
Team: Spark Fabric Platform
Date: December 2025


🎯 What is MCP-Zero?

In Simple Terms:
MCP-Zero is an algorithm (not a tool) that helps AI agents find the right tool from thousands of options—like Google search for AI tools.

The Analogy

  • Without MCP-Zero: Giving AI a 1,000-page phonebook → "find the right number"
  • With MCP-Zero: AI describes what it needs → Gets the exact tool instantly

🤔 What It Is vs What It's NOT

✅ MCP-Zero IS:

  • An algorithm/concept from academic research (like "binary search")
  • A method for semantic tool discovery using embeddings
  • A 2-stage hierarchical search (servers → tools)
  • Scalable to 10,000+ tools without performance issues

❌ MCP-Zero is NOT:

  • ❌ An installable library from PyPI (pip install mcp-zero doesn't exist)
  • ❌ A ready-to-use VS Code extension (yet)
  • ❌ Part of the official MCP SDK
  • ❌ A replacement for MCP protocol—it enhances it
  • ❌ Currently integrated into GitHub Copilot (as of December 2025)

📁 Repository Structure

Core Implementation

  • mcp_zero_core.py - Core algorithm (2-stage hierarchical routing)
  • mcp_client.py - MCP protocol client & VS Code settings parser
  • mcp_server_connector.py - Real MCP server connections (stdio/SSE)
  • demo_mcp_zero.py - Interactive demonstration

Documentation

  • README.md - This file

🚀 Quick Start

1. Install Dependencies```powershell

pip install -r requirements.txt


### 2. Run the Demo```powershell
# Run with real MCP servers (default - connects to your configured servers)
python demo_mcp_zero.py

# Or run with mock data (fast, no server connections)
python demo_mcp_zero.py --mock

The demo will:
1. Load your MCP servers from VS Code configuration
2. Create embeddings for all tool descriptions
3. Let you type queries to see semantic matching in action
4. Show 2-stage hierarchical search (servers → tools)


🤖 Why "MCP-Zero"? Understanding the Value

The Name Explained

MCP-Zero = Model Context Protocol with Zero context overhead

The "Zero" emphasizes:
- ✅ Zero Context Bloat: Load ZERO unnecessary tools into LLM
- ✅ Zero-Shot Discovery: Find tools without LLM seeing everything
- ✅ Near-Zero Latency: Sub-second search vs. slow LLM processing

💎 The Problem MCP-Zero Solves

Without MCP-Zero (Traditional Approach):```
User: "analyze Spark job performance"

  1. Load ALL MCP tools → 100,000+ tokens
  2. Send massive context to GPT-4 → $3.00 per query
  3. Takes 30+ seconds to process
  4. May hit token limits (fails with 1000+ tools)
  5. LLM gets confused by too many options

**With MCP-Zero:**```
User: "analyze Spark job performance"

1. Semantic search → finds spark_runtime_investigator (0.6s)
2. Load only top 5 relevant tools → 500 tokens
3. Send tiny context to GPT-4 → $0.015 per query
4. Fast response (< 2 seconds total)
5. LLM focuses on perfect match

📊 Real Impact

Metric Traditional MCP-Zero Improvement
Tokens/Query 100,000+ ~500 99.5% reduction
Cost/Query $3.00 $0.015 200x cheaper
Latency 30+ sec < 2 sec 15x faster
Max Tools ~100 10,000+ 100x scale

🛠️ How MCP-Zero Works

Prerequisites: Key Concepts

🔢 Embeddings: "Coordinates for Meaning"

Embeddings convert text into numbers that capture semantic meaning:```
"Spark performance" → [0.72, -0.15, 0.89, ... 384 numbers]
"analyze jobs" → [0.68, -0.12, 0.91, ... 384 numbers]
"pizza delivery" → [-0.23, 0.67, -0.45, ... 384 numbers]


Similar meanings = similar numbers. This lets computers mathematically compare concepts.

#### 📐 Cosine Similarity: Measuring Semantic Distance

Measures how &quot;parallel&quot; two embedding vectors are:```
Query: &quot;analyze Spark job performance&quot;
Tool 1: &quot;Analyze Spark job metrics&quot;     → 0.872 (very similar!)
Tool 2: &quot;Query database by email&quot;       → 0.215 (somewhat related)
Tool 3: &quot;Send email notification&quot;       → 0.044 (not related)
  • Score near 1.0 = very similar
  • Score near 0.0 = unrelated
  • Score near -1.0 = opposite

💾 Embedding Caching: Performance Critical

Key: Embeddings are computed once at startup, not per query.```python

At Startup (One-Time):

for tool in all_tools:
tool.embedding = model.encode(tool.description)

Cache to disk

At Query Time (Fast):

query_embedding = model.encode(user_query)
similarities = cosine_similarity(query_embedding, cached_tool_embeddings)


**Why This Matters:**
- Tool descriptions don&#x27;t change → embeddings are static
- Only query embedding computed at runtime
- Dramatically faster repeated queries

#### 📝 Tool Description Quality: Accuracy Critical

**MCP-Zero&#x27;s accuracy depends on clear tool descriptions.**

| ❌ Bad (Vague) | ✅ Good (Clear) |
|----------------|-----------------|
| &quot;Process data&quot; | &quot;Query Azure SQL database using T-SQL&quot; |
| &quot;Handle requests&quot; | &quot;Investigate Spark job performance bottlenecks&quot; |
| &quot;Run analysis&quot; | &quot;Execute Kusto KQL queries for log analysis&quot; |

**Impact:**```
Query: &quot;analyze Spark performance&quot;
Bad description: &quot;analyzer&quot; → 0.12 similarity (poor match)
Good description: &quot;Spark job performance analyzer&quot; → 0.85 (excellent!)

The Algorithm

Stage 1: Server-Level Matching

  1. User query: "I need to analyze Spark job performance"
  2. Convert to embedding: Transform query into 384 numbers
  3. Compare: Calculate cosine similarity against all server descriptions
  4. Filter: Return top-5 most relevant servers

Stage 2: Tool-Level Matching

  1. Narrow search: Only look at tools in top-5 servers (not all 10,000!)
  2. Compare: Calculate similarity for each tool in top servers
  3. Boost scores: Multiply by server relevance: final = similarity × (0.7 + 0.3 × server_score)
  4. Return best: Single tool with highest score

Result

Input: "analyze slow Spark job"
Output: spark_runtime_investigator (similarity: 0.872)
Tokens: 500 (vs 100,000 traditional)


🎮 GitHub Copilot Integration Status

⚠️ Important: MCP-Zero is NOT in GitHub Copilot (Yet)

Current State (December 2025):
- ✅ GitHub Copilot supports MCP protocol via @mcp commands
- ❌ Copilot does NOT use MCP-Zero optimization
- ❌ Copilot still loads ALL tools (traditional approach)

👀 Demonstrating the Problem: How to See Copilot Loading All Tools

You can visualize how Copilot currently loads ALL tools without MCP-Zero optimization:

Step 1: Check Your MCP Servers```
@mcp list servers

This shows all your configured MCP servers (e.g., scout-docker, kusto-mcp, playwright, etc.)

**Step 2: Ask Copilot to List All Tools**```
@mcp list all available tools

Copilot will load and display ALL tools from ALL servers. Watch the response - with multiple servers, this can be hundreds of tools in the context.

Step 3: See the Problem with a Query@mcp I need to analyze Spark job performance issues from the last 7 days

What Happens (Without MCP-Zero):
1. Copilot loads ALL tools from ALL servers into its context
2. With 5 servers and ~80+ tools, this is 8,000+ tokens
3. LLM must scan through everything to find relevant tool
4. Slower response, higher cost, potential confusion

Visual Comparison:

Approach What Gets Loaded Tokens Time
Current Copilot ALL 81 tools from 5 servers ~8,100 3-5 sec
With MCP-Zero Only 5 relevant Spark tools ~500 <1 sec
Savings 94% fewer tools 94% reduction 3-5x faster

Try This Demo Flow:

  1. Run @mcp list all available tools → See the massive list
  2. Run python demo_mcp_zero.py → Enter same query (uses real servers by default)
  3. Compare: Copilot shows 111 tools, MCP-Zero shows only top 5 matches

This visual comparison demonstrates why MCP-Zero's semantic filtering is valuable at scale.


What This Repository Demonstrates

This is a standalone implementation showing what MCP-Zero could do if integrated:

  • ✅ Connects to YOUR real MCP servers
  • ✅ Semantic search finds the right tool from 81+ tools
  • ✅ 2-stage hierarchical matching (servers → tools)
  • ✅ Shows 94% token reduction potential

What It Does NOT Do:
- ❌ Does NOT modify GitHub Copilot's behavior
- ❌ Does NOT inject tools into Copilot's context
- ❌ Does NOT replace Copilot's native MCP support


📚 References

Research

  • Paper: MCP-Zero: Active Tool Discovery
  • Authors: Xingyu Feng et al.
  • Research Code: https://github.com/xfey/MCP-Zero

Protocol

  • MCP Specification: https://modelcontextprotocol.io/

📄 License

MIT License


🙏 Acknowledgments

  • Research paper by Xingyu Feng et al.
  • MCP Protocol by Anthropic
  • This is an independent implementation demonstrating the algorithm

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP Zero Ddfa0050 怎么安装?

在客户端按下面的安装命令接入:pip install -r requirements.txt。装完在客户端配置里引用同一个包或端点。

MCP Zero Ddfa0050 怎么在 VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Zero Ddfa0050 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Zero Ddfa0050 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

MCP Zero Ddfa0050 支持哪些客户端?

资料标注支持 VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP Zero Ddfa0050 能提供哪些能力?

资料显示能力标签包括 Python、VS Code、搜索。具体工具清单以官方文档为准。

MCP Zero Ddfa0050 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

MCP Zero Ddfa0050 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。