What is the key difference between Bloomfilter and Nodedex?

Bloomfilter belongs to the Developer Tools category with local stdio execution, while Nodedex belongs to the Developer Tools category with local stdio execution.

How do I install Bloomfilter or Nodedex in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Bloomfilter and Nodedex free or paid?

Bloomfilter operates under a Free / Open Source model (No auth required). Nodedex operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Bloomfilter lists 10 tools with 0 views and 9 GitHub stars. Nodedex lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Bloomfilter and Nodedex together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Bloomfilter or Nodedex in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Bloomfilter and Nodedex free to use, or do they require API keys?

Bloomfilter is listed under a Free / Open Source model with No auth required . Nodedex operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Bloomfilter and Nodedex at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both bloomfilter and nodedex as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Bloomfilter has a Quality Score of 53 /100 ( Good ) with 0 views, 0 installs, and 9 GitHub stars. Nodedex holds a Quality Score of 31 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Bloomfilter vs Nodedex

In-depth architectural comparison of the Bloomfilter and Nodedex MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Bloomfilter

Developer Tools · Local stdio

Quality: 53/100 (Good) | Auth: No auth required

Nodedex

Developer Tools · Local stdio

Quality: 31/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Bloomfilter if you need specialized Developer Tools tools running via a local process. Choose Nodedex if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Bloomfilter when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: search_domains, get_pricing, get_domain_info.

Explore Bloomfilter Details

Choose Nodedex when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Nodedex Details

Feature & Specification Comparison

Specification	B Bloomfilter Developer Tools	N Nodedex Developer Tools
Summary	Service that lets AI Agents search, register, and configure domains	Your project's decision history for agents: decisions, dead-ends, constraints - queryable, local.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Bloomfilter Tools (10)

search_domains

get_pricing

get_domain_info

register_domain

renew_domain

get_account

list_dns_records

add_dns_record

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Bloomfilter Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "bloomfilter": {
      "command": "npx",
      "args": [
        "-y",
        "@bloomfilter/mcp-server"
      ]
    }
  }
}

Nodedex Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "nodedex": {
      "command": "npx",
      "args": [
        "-y",
        "nodedex"
      ]
    }
  }
}

Frequently Asked Questions

Bloomfilter is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Nodedex belongs to Developer Tools using local stdio subprocess. Select Bloomfilter when you need capabilities focused on developer tools and Nodedex when you require tools for developer tools.

More alternatives to Bloomfilter More alternatives to Nodedex Developer Tools category hub