English Français العربية

Agent Index

Registre officiel Recherche et web

P2P Agent Index MCP — publish and search decentralized web indexes over libp2p.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @agent-idx/client
Claude Code 
claude mcp add agent-index -e 'AGENT_INDEX_DIRECTORY_URL=<AGENT_INDEX_DIRECTORY_URL>' -- npx -y @agent-idx/client@0.4.5
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "agent-index": {
            "command": "npx",
            "args": [
                "-y",
                "@agent-idx/client@0.4.5"
            ],
            "env": {
                "AGENT_INDEX_DIRECTORY_URL": "<AGENT_INDEX_DIRECTORY_URL>"
            }
        }
    }
}

Variables d'environnement

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

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. @agent-idx/client
  2. Install (npx)
  3. CLI
  4. MCP tools
  5. Develop from source
  6. Publish to npm (maintainers)

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

ToolDescription
get_network_setupStart here — directory URL, configured peers, Active Nodes sections, blind-test flow
publish_indexStore a page summary and advertise agent-supplied keywords
search_indexDiscover peers by keywords, fetch records for query, return merged JSON
query_peer_indexQuery a known peer ID directly (bypasses DHT; uses relay hole-punch when needed)
add_keywordsAdd keywords to this peer's advertised topic list
remove_keywordsRemove keywords from this peer's advertised topic list
set_keywordsReplace the peer's advertised keyword list
find_peers_by_keywordDHT/registry discovery only — peer IDs and multiaddrs
get_peer_statusLocal peer ID, configured routing/relay, keyword and record counts
get_peer_profileFetch 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.

Questions fréquentes

Qu'est-ce que Agent Index ?

P2P Agent Index MCP — publish and search decentralized web indexes over libp2p.

Comment installer Agent Index ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add agent-index -e 'AGENT_INDEX_DIRECTORY_URL=<AGENT_INDEX_DIRECTORY_URL>' -- npx -y @agent-idx/client@0.4.5. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Agent Index ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Agent Index est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Agent Index ?

Il est publié par agent-idx. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.