MCP2ANP
MCP ↔ ANP 桥接服务,让支持 MCP 的客户端像调用本地工具一样使用 ANP 智能体。
快速开始
第一步:获取 API Key
在使用 MCP2ANP 之前,你需要先获取一个 API Key:
- 访问 DID-HOST 并登录账户
- 新建 DID Card,在创建流程中勾选"生成 API Key"
- 将生成的私钥与 API Key 安全保存(它们仅显示一次,丢失后无法恢复)
验证 API Key(可选):
curl -sS -H "X-API-Key: YOUR_API_KEY" \
"https://didhost.cc/api/v1/mcp-sk-api-keys/verify" | jq .
第二步:使用官方托管(推荐)
在 Claude 中直接使用官方托管端点,无需安装和配置:
claude mcp add --transport http mcp2anp-remote https://agent-connect.ai/mcp2anp/mcp \
--header "X-API-Key: YOUR_API_KEY"
将 YOUR_API_KEY 替换为你在第一步中获取的 API Key。
第三步:本地启动服务器(可选)
如果你需要自托管服务器,可以按照以下步骤操作:
3.1 安装依赖
git clone git@github.com:agent-network-protocol/mcp2anp.git
cd mcp2anp
uv venv --python 3.11
uv sync
3.2 配置 DID 凭证
方式 1: 使用默认凭证(开发测试)
直接启动,使用项目提供的默认公共 DID 凭证:
uv run python -m mcp2anp.server
方式 2: 通过环境变量配置(推荐生产环境)
# 设置 DID 文件路径
export ANP_DID_DOCUMENT_PATH="docs/did_public/public-did-doc.json"
export ANP_DID_PRIVATE_KEY_PATH="docs/did_public/public-private-key.pem"
# 启动服务
uv run python -m mcp2anp.server --log-level INFO
方式 3: 在 Claude 中添加本地服务器
# 将仓库根目录赋值给变量(替换为你的实际路径)
MCP2ANP_DIR=/Users/yourname/mcp2anp
claude mcp add mcp2anp \
--env ANP_DID_DOCUMENT_PATH=$MCP2ANP_DIR/docs/did_public/public-did-doc.json \
--env ANP_DID_PRIVATE_KEY_PATH=$MCP2ANP_DIR/docs/did_public/public-private-key.pem \
-- uv run --directory $MCP2ANP_DIR python -m mcp2anp.server
第四步:运行官方 Demo
运行官方演示脚本,查看完整的使用示例:
uv run python examples/mcp_client_demo.py
Demo 会演示:
- 列出可用工具
- 调用
anp.fetchDoc获取智能体描述文档 - 调用
anp.invokeOpenRPC执行 OpenRPC 方法
Metadata
Release files for iflow-mcp_agent-network-protocol-mcp2anp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_agent_network_protocol_mcp2anp-0.1.0.tar.gz | 17.1 kB | Without provenance | Details for iflow_mcp_agent_network_protocol_mcp2anp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_agent_network_protocol_mcp2anp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_agent_network_protocol_mcp2anp-0.1.0-py3-none-any.whl |
Total release size: 38.8 kB
Release files / iflow_mcp_agent_network_protocol_mcp2anp-0.1.0.tar.gz
| Download URL | iflow_mcp_agent_network_protocol_mcp2anp-0.1.0.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e81c3dcb0266baff746321fcef750f2d2838f28acb4691396d2620cd562b3d3
|
|
BLAKE2b-256 checksum How to use checksums |
56f603d6b46662268775ca2680e06f576044aca45da60971b4f7c567ec967544
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.2 {"installer":{"name":"uv","version":"0.10.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_agent_network_protocol_mcp2anp-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_agent_network_protocol_mcp2anp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 21.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
865b65a23f1e8961e72b9c5f4ef6b2c2ccd49d09b1f1dcde3230ed45a6138a65
|
|
BLAKE2b-256 checksum How to use checksums |
cc4fa4abc698346166c3867b286ed334471686ab4b9888366fdb632394f8d236
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.2 {"installer":{"name":"uv","version":"0.10.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_agent-network-protocol-mcp2anp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.