Agent Index vs Lilbee
A side-by-side look at the Agent Index and Lilbee MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Index for search & data extraction work as a local process; choose Lilbee for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Index when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AGENT_INDEX_DIRECTORY_URL. - You want tools like
get_network_setup, publish_index, search_index.
Choose Lilbee when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 49/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | AGENT_INDEX_DIRECTORY_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 63 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Agent Index | View Lilbee |
Tools & capabilities
Agent Index tools 10
get_network_setupStart here** — directory URL, configured peers, Active Nodes sections, blind-test flowpublish_indexStore a page summary and advertise agent-supplied `keywordssearch_indexDiscover peers by `keywords`, fetch records for `query`, return merged JSONquery_peer_indexQuery a known peer ID directly (bypasses DHT; uses relay hole-punch when needed)add_keywordsAdd keywords to this peer's advertised topic listremove_keywordsRemove keywords from this peer's advertised topic listset_keywordsReplace the peer's advertised keyword listfind_peers_by_keywordDHT/registry discovery only — peer IDs and multiaddrsget_peer_statusLocal peer ID, configured routing/relay, keyword and record countsget_peer_profileFetch ANP locators from another edge peer over libp2p
Lilbee tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agent Index
{
"mcpServers": {
"agent-index": {
"command": "npx",
"args": [
"-y",
"@agent-idx/client"
],
"env": {
"AGENT_INDEX_DIRECTORY_URL": "YOUR_AGENT_INDEX_DIRECTORY_URL_HERE"
}
}
}
}
Lilbee
{
"mcpServers": {
"tobocop2-lilbee": {
"command": "npx",
"args": [
"-y",
"lilbee"
]
}
}
}
Frequently asked questions
Agent Index is categorized under Search & Data Extraction and uses a local stdio subprocess. Lilbee belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Agent Index for search & data extraction work and Lilbee for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agent Index has no declared pricing — check the project's own site. Lilbee is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agent-index and tobocop2-lilbee as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Index has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Lilbee has 59/100 (Good) with 1 views, 0 installs and 63 GitHub stars.