How do I install Agent Index?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Agent Index need an API key?

The publisher lists these environment variables: AGENT_INDEX_DIRECTORY_URL.

What transport does Agent Index use?

Agent Index runs locally over stdio.

When was Agent Index last checked?

Last checked 2026-11-09. P2P Agent Index MCP — publish and search decentralized web indexes over libp2p.

Agent Index MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @agent-idx/[email protected]

Credentials from the publisher

AGENT_INDEX_DIRECTORY_URL — URL of the network Active Nodes directory (routing/relay multiaddrs)

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1AGENT_INDEX_DIRECTORY_URL=<value> claude mcp add io.github.agent-idx-mcp -- npx -y @agent-idx/client@0.4.5

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.agent-idx-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "@agent-idx/[email protected]"8      ],9      "env": {10        "AGENT_INDEX_DIRECTORY_URL": "<value>"11      }12    }13  }14}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.4.5
API key

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

@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.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Agent Index?

Does Agent Index need an API key?

What transport does Agent Index use?

When was Agent Index last checked?

Documentation

@agent-idx/client

Install (npx)

CLI

Options

MCP tools

Develop from source

Publish to npm (maintainers)