domainkits

DomainKits MCP provides a suite of domain intelligence tools that you can access through natural language prompts. It combines search capabilities (to monitor new or expiring domains, check registrations, analyze ownership data, and perform reverse NS lookups), query tools (DNS, WHOIS, safety checks, keyword availability, and market pricing), analysis tools (SEO backlink and keyword data), trend helpers, bulk operations, and workflow guidance. Many workflows are designed to help you discover domains, analyze potential investments, monitor changes, and generate ideas with availability checks. You can interact with these tools in a conversational manner, asking for status updates, price estimates, or comprehensive domain analyses, and the MCP will route your request to the appropriate toolset and return structured results. Some capabilities require registered accounts, so you may need to sign up and obtain an API key to unlock higher usage tier features. The Quick Start examples show how to connect DomainKits to your MCP client via an API endpoint and optional headers for authentication.

To use DomainKits with the MCP interface, configure the domainkits server in your MCP client using the provided mcp-remote endpoint. Then invoke relevant tools like available, whois, dns, market_price, analyze, or brand_match through natural language prompts. For monitoring or recurring tasks, you can leverage the personal/memory tools to set up monitors, preferences, and strategies, enabling automated opportunity discovery and ongoing domain monitoring within your workspace.

Prerequisites:

• Node.js and npm (to use the npx-based command in the MCP config)
• Access to the DomainKits MCP API at https://api.domainkits.com/v1/mcp (and an API key if you plan to use header-based auth)

Step 1: Install Node.js and npm

• Visit https://nodejs.org/ and install the latest LTS version for your platform.

Step 2: Create your MCP config

• Create a JSON file (e.g., mcp_config_domainkits.json) with the following content:

{
  "mcpServers": {
    "domainkits": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.domainkits.com/v1/mcp",
        "--transport",
        "http-first"
      ]
    }
  }
}

Step 3: (Optional) Include API key for higher limits

• If you have an API key, you can pass it as a header:

{
  "mcpServers": {
    "domainkits": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.domainkits.com/v1/mcp",
        "--header",
        "X-API-Key: your-api-key-here",
        "--transport",
        "http-first"
      ]
    }
  }
}

Step 4: Run the MCP client

• With the config file saved, run your MCP client as you normally would (the exact command depends on your MCP client). The example uses npx to invoke the remote MCP endpoint. If your client expects a single file path, point it to mcp_config_domainkits.json or load the content accordingly.

Step 5: Verify connectivity

• Ensure the client can reach https://api.domainkits.com/v1/mcp and that your API key (if used) is accepted. Test with a simple prompt like: "Find available 3-letter .ai domains" to confirm tool access.

Notes and tips:

• The DomainKits MCP endpoint is https://api.domainkits.com/v1/mcp. You can pass an API key via the X-API-Key header to increase limits.
• Tools span multiple categories (Search, Query, Analysis, Trend, Bulk, and Workflow Guides). Some tools require user accounts or API access, so ensure your plan includes required features.
• If you primarily use this through an MCP client, the npx-based workflow shown in the Quick Start is the simplest integration path. You can also connect via Gemini CLI or other clients by pointing them to the same endpoint.
• For memory/personal tools (preferences, monitor, strategy, etc.), enable and configure memory storage in your MCP client if you need long-running tasks, saved settings, or automated monitoring.
• Rate limits and availability vary by tier. Start with a trial tier to explore capabilities and upgrade if you need more throughput and access to premium tools.
• If you run into issues, ensure your environment allows outbound HTTPS to the API endpoint and that any required API keys are correctly provided in headers.