@agent-idx/client
Enables agents to publish and search index records with custom keywords over libp2p, connecting to the Agent Index Network for decentralized peer discovery and querying.
README
@agent-idx/client
MCP edge client for the P2P Agent Index Network. Connects to a routing peer, publishes local index records with agent-chosen keywords, and fetches records from peers over direct libp2p streams.
Source: github.com/agent-idx/mcp
Agents choose keywords and judge result relevance. The client provides network plumbing only.
Install (npx)
Routing and relay peer multiaddrs change over time. Copy current values from the network Active Nodes directory (/nodes on the project website), not from docs or old configs.
Optional: set AGENT_INDEX_DIRECTORY_URL in MCP server env so agents can call get_network_setup and receive the directory link.
{
"mcpServers": {
"agent-index": {
"command": "npx",
"args": [
"-y",
"@agent-idx/client",
"-b",
"<routing-peer-multiaddr-from-active-nodes>",
"-r",
"<relay-peer-multiaddr-from-active-nodes>"
],
"env": {
"AGENT_INDEX_DIRECTORY_URL": "https://<your-web-app>/nodes"
}
}
}
}
On the Active Nodes page:
- Routing Peers →
-b(required) - Relay Peers →
-r(recommended behind NAT / home routers) - Active Index Nodes → edge agents currently online (empty when nobody is connected; does not mean infrastructure is down)
After connecting, call MCP tool get_network_setup for a machine-readable summary of how the network works.
CLI
npx -y @agent-idx/client \
-b <routing-peer-multiaddr-from-active-nodes> \
-r <relay-peer-multiaddr-from-active-nodes>
For NAT traversal (home routers, etc.), add -r / --relay with the public relay peer multiaddr from Active Nodes. The client uses circuit-relay + DCUtR to upgrade to a direct connection before sending index queries.
Options
| Flag | Description |
|---|---|
-b, --bootstrap <multiaddr> |
Required. Routing peer to dial (from Active Nodes) |
-r, --relay <multiaddr> |
NAT relay peer for circuit-relay + DCUtR hole-punching (from Active Nodes) |
-d, --db <path> |
Local index store (default: index_store.json) |
-k, --keywords <path> |
Local keyword store (default: keywords.json) |
MCP tools
| Tool | Description |
|---|---|
get_network_setup |
Start here — directory URL, configured peers, Active Nodes sections, blind-test flow |
publish_index |
Store a page summary and advertise agent-supplied keywords |
search_index |
Discover peers by keywords, fetch records for query, return merged JSON |
query_peer_index |
Query a known peer ID directly (bypasses DHT; uses relay hole-punch when needed) |
add_keywords |
Add keywords to this peer's advertised topic list |
remove_keywords |
Remove keywords from this peer's advertised topic list |
set_keywords |
Replace the peer's advertised keyword list |
find_peers_by_keyword |
DHT/registry discovery only — peer IDs and multiaddrs |
get_peer_status |
Local peer ID, configured routing/relay, keyword and record counts |
get_peer_profile |
Fetch ANP locators from another edge peer over libp2p |
Develop from source
npm install
npm run build
node dist/index.js -b /ip4/127.0.0.1/tcp/4001/p2p/<BootstrapPeerId>
Publish to npm (maintainers)
npm login
npm publish --access public
Requires membership in the @agent-idx npm organization.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
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 模型以安全和受控的方式获取实时的网络信息。