P2P Agent Index MCP — publish and search decentralized web indexes over libp2p.
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.
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:
-b (required)-r (recommended behind NAT / home routers)After connecting, call MCP tool get_network_setup for a machine-readable summary of how the network works.
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.
| 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) |
| 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 |
npm install
npm run build
node dist/index.js -b /ip4/127.0.0.1/tcp/4001/p2p/<BootstrapPeerId>
npm login
npm publish --access public
Requires membership in the @agent-idx npm organization.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @agent-idx/clientMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-agent-idx-mcp": {
"command": "npx",
"args": [
"-y",
"@agent-idx/client"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceAgent Index works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.