> ## Documentation Index
> Fetch the complete documentation index at: https://docs.knotie-ai.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom MCP domain

> Serve the integration gateway MCP server from your own branded hostname (e.g. mcp.yourcompany.com) with Cloudflare-managed SSL.

## What this feature does

By default, the Knotie AI Pro integration gateway MCP server is reachable at `mcp.knotie-ai.pro`. With a **custom MCP domain**, partners on paid tiers can resell the MCP server under their own branded hostname — for example, `mcp.yourcompany.com`.

Clients and AI coding assistants that connect to your MCP server use your domain name, not Knotie's. SSL (the padlock in the browser) is handled automatically — you add one DNS record and Knotie takes care of the rest.

## Prerequisites

* An active paid-tier subscription with MCP access
* A domain you control, with permission to add DNS records (a CNAME record)
* The **Custom MCP Domain** option visible in your portal — if it doesn't appear, contact Knotie support to enable it for your account

## Good to know

Switching to a custom domain only changes the web address your customers see — nothing else about how MCP works changes:

* **Your existing tokens keep working.** Setting up a custom domain doesn't invalidate any tokens you've already created.
* **Tokens, limits, and credit charges stay the same.** Only the server address shown to customers is different.
* **Both addresses work.** Requests to your custom domain are handled the same as requests to the default `mcp.knotie-ai.pro`.

## Set up your custom MCP domain

### Step 1 — Enter your domain

1. In the Partner Portal, go to **AI Agents → MCP Tokens**.
2. Find the **Custom MCP Domain** card.
3. Enter the hostname you want to use (e.g. `mcp.yourcompany.com`).
4. Click **Save**.

Knotie registers your domain and starts setting up its SSL certificate. The status changes to **Pending**.

### Step 2 — Add the CNAME record

While status is Pending, the card shows the DNS record you need:

| Type  | Name                          | Value               |
| ----- | ----------------------------- | ------------------- |
| CNAME | `mcp` (or your chosen prefix) | `mcp.knotie-ai.pro` |

Add this record at your DNS provider (Cloudflare, GoDaddy, Namecheap, etc.). The record usually takes effect within a few minutes but can take up to 48 hours.

<Tip>
  If your DNS is managed by Cloudflare, set the CNAME to **DNS-only** (grey cloud) while you verify, so Cloudflare's proxy doesn't interfere.
</Tip>

### Step 3 — Verify the domain

Once the record has taken effect, click **Verify Domain** in the card. Knotie then:

1. Confirms your domain points to the right place.
2. Switches traffic for your domain over to the MCP server.
3. Changes the status to **Verified / Active**.

After verification, the MCP connection details shown in the portal update to use your custom domain.

## Using your custom MCP domain

After verification, use your branded hostname anywhere you previously used `mcp.knotie-ai.pro`. Your MCP Token snippet in the portal already shows the updated URL.

Example config for Cursor, Windsurf, or Claude Desktop:

```json theme={null}
{
  "mcpServers": {
    "knotie": {
      "url": "https://mcp.yourcompany.com/sse",
      "headers": {
        "Authorization": "Bearer <your-mcp-token>"
      }
    }
  }
}
```

You still connect with the same token as before — changing the domain doesn't change how tokens work.

## Removing a custom MCP domain

1. Go to **AI Agents → MCP Tokens → Custom MCP Domain**.
2. Click **Remove** (or **Delete Domain**).
3. Knotie removes the domain setup for you.
4. All traffic goes back to `mcp.knotie-ai.pro` automatically.

<Warning>
  Removing a custom MCP domain immediately breaks any client configurations pointing to that hostname. Inform customers before removing.
</Warning>

## Troubleshooting

| Symptom                                    | What to check                                                                                                                            |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Status stuck on **Pending**                | Confirm the CNAME was added in the right place and its value is exactly `mcp.knotie-ai.pro`. Allow up to 48 hours for it to take effect. |
| **Verify Domain** fails                    | Double-check the CNAME value has no extra characters or trailing slashes.                                                                |
| Custom domain option not visible           | The feature may not be enabled for your account. Contact Knotie support.                                                                 |
| SSL / security error right after verifying | It can take up to 15 minutes for the certificate to finish setting up. Wait and try again.                                               |
| Token errors on the custom domain          | Make sure you're using a valid MCP token. Switching domains doesn't change how you sign in.                                              |

## Related pages

* [MCP Tokens](/partner-portal/ai-agents/mcp/tokens) — Generate and manage MCP bearer tokens
* [MCP API reference](/api-reference/mcp/introduction) — Endpoint documentation
* [Whitelabel settings](/partner-portal/settings/whitelabel-settings) — Portal domain and branding configuration
* [Custom domains (customer portal)](/customer-management/custom-domain) — Setting up a custom domain for a customer's portal