mcp -bloomfilter

This MCP server wraps the Bloomfilter API and exposes its capabilities as MCP tools that AI agents can call via stdio JSON-RPC. It supports both free and authenticated operations: free tools let you search domains and view pricing, while authenticated tools allow domain registration, renewal, DNS management, and wallet/account queries using a wallet-based payment flow via the x402 protocol. The server authenticates against Bloomfilter using a Sign-In With Ethereum (SIWE) flow on the first authenticated tool call, and payments are handled automatically when a paid operation is requested. Tools include search_domains and get_pricing (free), and get_domain_info, register_domain, renew_domain, get_account, list_dns_records, add_dns_record, update_dns_record, and delete_dns_record (authenticated, with DNS mutations costing USDC). You can point an MCP client (Claude Desktop, Cursor, Windsurf, or other stdio-based clients) at the server to enable automated domain search, purchase, and DNS configuration through AI agents.

Prerequisites:

• Node.js 20+ installed on your system
• npm (comes with Node.js) or pnpm

Install and run from source:

1. Clone the repository: git clone https://github.com/BloomFilter-Labs/mcp-server-bloomfilter.git cd mcp-server-bloomfilter

2. Install dependencies: npm install

3. Build the project (if the repository provides a build step): npm run build

4. Run the server (example with a private key): BLOOMFILTER_PRIVATE_KEY=0xYOUR_PRIVATE_KEY npx @bloomfilter/mcp-server

Notes:

• The server runs as a stdio JSON-RPC service and is intended to be launched by an MCP client.
• If you want to run directly without building, you can rely on the npm package, using the quick-start command shown above.

Environment variables and configuration tips:

• BLOOMFILTER_PRIVATE_KEY is required for paid operations (register, renew, and DNS mutations). Without it, only search_domains and get_pricing are available.
• BLOOMFILTER_API_URL can be set to override the API base URL if needed; defaults to https://api.bloomfilter.xyz.
• The mcp config example includes the npm package name and the -y flag to auto-accept prompts when using npx. You can customize the env block to include your private key and any other needed variables.
• All payments are handled via the x402 protocol in USDC on Base (Ethereum L2). Ensure your wallet has sufficient USDC.
• This server uses SIWE to authenticate with Bloomfilter on the first authenticated call; no extra setup is required beyond providing the private key.
• For troubleshooting, ensure your environment has network access to Bloomfilter endpoints and that your wallet supports the necessary API interactions.