MCP server

ChatGPT

1. 1Turn on developer mode: Settings › Apps › Advanced settings › Developer mode.
2. 2Go to Settings › Apps › Create. Name it MailCheap, enter https://news.carolekorngold.com/mcp as the MCP server URL and pick OAuth as the authentication.
3. 3Click Scan Tools, sign in to MailCheap in the window that opens and click Allow. Then click Create.
4. 4In a chat, pick MailCheap from the + menu, or name it in your message.

Developer mode is on ChatGPT on the web, for Business, Enterprise and Edu workspaces, where an admin may have to allow it first. On Pro, ChatGPT only uses the read-only tools for now.

Claude

1. 1Go to Customize › Connectors and click Add custom connector.
2. 2Enter https://news.carolekorngold.com/mcp. If Claude asks how it identifies itself, keep Use Claude's published identity. Click Add.
3. 3Click Connect, sign in to MailCheap and click Allow.
4. 4The connector works in claude.ai, Claude Desktop and the mobile apps. Turn it on or off in a chat from + › Connectors.

On Team and Enterprise plans, an owner adds it once in Organization settings › Connectors › Add › Custom › Web, then each member clicks Connect under Customize › Connectors. The Free plan has one custom connector.

Grok Bot

1. 1In a chat, ask Grok Bot to add the custom MCP server https://news.carolekorngold.com/mcp.
2. 2Sign in to MailCheap when it asks, and click Allow.

Claude Code

claude mcp add --transport http --scope user mailcheap https://news.carolekorngold.com/mcp \
  --header "Authorization: Bearer $MAILCHEAP_API_KEY"

The shell puts the key in Claude Code's settings when the command runs. --scope user makes the server available in every project; run /mcp in Claude Code to check it's connected.

Codex

[mcp_servers.mailcheap]
url = "https://news.carolekorngold.com/mcp"
bearer_token_env_var = "MAILCHEAP_API_KEY"

Codex reads the key from MAILCHEAP_API_KEY each time it starts, so export it in your shell profile. The same server from the terminal: codex mcp add mailcheap --url https://news.carolekorngold.com/mcp --bearer-token-env-var MAILCHEAP_API_KEY

Cursor

{
  "mcpServers": {
    "mailcheap": {
      "url": "https://news.carolekorngold.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MAILCHEAP_API_KEY}"
      }
    }
  }
}

Cursor reads MAILCHEAP_API_KEY from the environment it was opened in. If it isn't set there, put the key itself after Bearer, and keep the file out of version control.

Connected apps

An app you allow gets the same access as a full access key, in your account only. The API keys page lists connected apps with when they were last used. Revoke one there and its tokens stop working right away; it has to ask you again to come back.