agent-mcp-py

agent-mcp-py

A Python framework for building MCP servers with built-in bearer auth, conversation-depth guarding, usage logging, and sync-store registration, wrapping the official MCP SDK.

Category
访问服务器

README

agent-mcp-py

The convention layer every app in the ecosystem uses to expose itself as an MCP server. Wraps the official mcp Python SDK with bearer auth, a conversation-depth guard, usage logging, and sync-store registration already wired in.

See CLAUDE.md for the design spec and the ecosystem context.

This repo implements v0.1.0 — all seven modules, 175 tests, verified end to end against a live server over streamable HTTP.

app author writes                agent_mcp adds                     the SDK does
─────────────────                ──────────────                     ────────────
@mcp.tool(read_only=True)   →    bearer auth (401 at the edge)  →   tools/list
def get_balance(...)             depth guard (X-Agent-Depth)        tools/call
                                 confirmation gate (X-Confirmed)    resources/read
                                 usage row per call
                                 $ref-free JSON schema

Install

Consumed as a pinned git dependency — never from PyPI:

# pyproject.toml
agent-mcp-py = { git = "https://github.com/Johonnyy/agent-mcp-py", tag = "v0.1.0" }
# pip equivalent
pip install "agent-mcp-py @ git+https://github.com/Johonnyy/agent-mcp-py@v0.1.0"

The distribution is agent-mcp-py; the import is agent_mcp. Mismatched on purpose so the package name matches the repo.

Usage

from fastapi import FastAPI
from contextlib import asynccontextmanager
from agent_mcp import AgentMCPServer

mcp = AgentMCPServer(
    app_name="finance",
    version="0.1.0",
    sync_store_url=settings.sync_store_url,
    auth_keys_env="FINANCE_MCP_KEYS",   # comma-separated "name:token" pairs
)

@mcp.resource("finance://transactions/recent{?limit}")
def recent_transactions(limit: int = 20) -> list[dict]:
    """Every resource URI mirrors a real dashboard view — this is what the
    transactions table on the frontend renders from too."""
    return db.get_recent_transactions(limit)

@mcp.tool(read_only=True)
def get_balance(account: str) -> float:
    return db.get_balance(account)

@mcp.tool(read_only=False, requires_confirmation=True)
def create_invoice(customer_id: str, amount: float) -> dict:
    return db.create_invoice(customer_id, amount)

@asynccontextmanager
async def lifespan(app: FastAPI):
    async with mcp.lifespan():        # required — see "Mounting" below
        yield

app = FastAPI(lifespan=lifespan)
app.router.routes.extend(mcp.routes())        # MCP at /mcp
app.router.routes.extend(mcp.usage_routes())  # summary at /agent/usage

Both decorators return the function unwrapped, so the app's own HTTP handler calls the very same object the model calls — a tool mirrors a real user action rather than a parallel code path that drifts from it.

Mounting

Use mcp.routes(). app.mount("/mcp", mcp.asgi_app()) also works but has a sharp edge: Mount("/mcp") only matches /mcp/..., so a bare POST /mcp falls through to the host router's redirect_slashes and gets a 307 — and the real MCP client does not follow that redirect. routes() claims the exact path too, so both forms work. If you mount by hand, make sure every caller uses the trailing slash; agent_mcp.mcp_url() always produces it.

The lifespan is not optional. A mounted sub-app's own lifespan never runs, so the host must enter session_manager.run() or the very first request fails.

Layout

Path Role
depth.py stdlib-only leaf. Header constants, MAX_AGENT_DEPTH, DepthExceeded, next-hop threading
auth.py stdlib-only leaf. Bearer verification as pure functions
schema.py Tool-name rules, JSON-Schema $ref inlining
registry.py Peer discovery — PeerRecord, resolve(), refresh()
config.py AgentMCPSettings (env prefix AGENT_MCP_)
usage_log.py UsageSink protocol, SQLite default, /agent/usage data
errors.py The error taxonomy: what becomes a protocol error vs. isError text
decorators.py The signature surgery and the guard path
middleware.py Pure-ASGI auth gate, mount-path normalisation
sync_client.py register() / heartbeat_loop()
server.py AgentMCPServer — composes all of the above

Conventions this enforces

  • Query tools are read_only=True, risky ones requires_confirmation=True. Both are visible on the wire: readOnlyHint in standard annotations, and both flags in _meta under dev.johnny.agent-mcp/ (the SDK's ToolAnnotations silently drops unknown fields, so a custom one there would vanish). Enforcement always reads the in-process policy, never the wire.
  • Depth is capped at 5 hops via X-Conversation-Id / X-Agent-Depth. mcp.call_peer() threads them automatically and refuses an over-cap hop before it leaves the process.
  • Tool names must be snake_case, ≤40 chars, no __ — agent_runtime namespaces them <server>__<tool>, and the double underscore is the separator. Violations fail at import, not at call time.
  • Input schemas ship $ref-free. Pydantic emits $defs/$ref for nested models and several model providers reject them, so they are inlined at registration. A recursive model is refused with a message saying what to do instead.
  • Usage stays local. Rows go to this app's own database, never a shared one. The spawner aggregates by querying each app's /agent/usage.
  • No model names anywhere, and no LLM SDK dependency. If a resource needs a model, the host app passes in a callable. A test enforces this.

Error taxonomy

Failure What the caller sees
Missing/bad bearer token HTTP 401 at the ASGI edge
Malformed X-Agent-Depth MCPError(INVALID_PARAMS)
Inbound call over the depth cap MCPError(INVALID_REQUEST)
Outbound call_peer over the cap ordinary exception → isError: true
Missing X-Confirmed ordinary exception → isError: true
Any exception in a tool body isError: true
Sync store unreachable a logged warning, nothing else

The inbound/outbound asymmetry is deliberate: an outbound refusal happens inside a tool body, where a bad peer call must not take down an otherwise fine turn.

Interop with agent-runtime

agent_runtime imports agent_mcp.depth for the header constants and the cap, so it can pre-check client-side. That module is stdlib-only, and agent_mcp's __init__ is lazy (PEP 562) so importing it does not drag in mcp, pydantic, httpx2, starlette and uvicorn. There is a test that fails if this regresses.

Both libraries can write one SQLite file (agent_mcp_usage / agent_runtime_usage), sharing the join columns conversation_id, app_name, depth, and created_at (ISO-8601 UTC seconds, never epoch floats). WAL plus a busy timeout makes the co-tenancy safe.

Pin mcp>=2.0,<3. v2 renamed FastMCP to MCPServer and this package targets that API exclusively — it will not import under 1.x.

Local development

git clone https://github.com/Johonnyy/agent-mcp-py
cd agent-mcp-py

python -m venv .venv
.venv/Scripts/activate            # Windows;  .venv/bin/activate on Linux/macOS
pip install -e ".[dev]"
cp .env.example .env

pytest                            # whole suite, no network required
pytest tests/test_decorators.py   # the signature surgery
pytest tests/test_end_to_end.py   # a real uvicorn server over HTTP

The suite needs no API key and makes no outbound calls: the sync store is a fake, auth uses known-good/known-bad tokens, and the end-to-end file binds an ephemeral local port.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选