MCP Server Setup Guide
Connect GlockApps to your AI assistant

Paste one address into Claude, ChatGPT, or any MCP-compatible client. Nothing to install, nothing to run. Find your client below for the exact steps.

Before you start

You need three things, all on your GlockApps account.

  • An account. If you do not have one, start a free trial. Your first tests are free.
  • API access on your plan. The connector uses the GlockApps API, so your plan has to include it.
  • Your API key. It is on your account page. Copy it before you begin; you will be asked for it once, on a GlockApps page, and not again.
Your API key is never shared with the AI provider. Connecting opens a GlockApps page that asks for it, and the key stays on your GlockApps account. If it is ever reissued, the connection keeps working.

Each inbox placement test started through the connector costs one point, exactly as it does in the app.

ClaudeClaude
ChatGPTChatGPT
and any other MCP-capable client

Claude (web and mobile)

  1. Open Settings, then Connectors.
  2. Choose Add custom connector.
  3. Paste the connector address. Leave the optional Client ID and Client Secret fields empty: the connector registers itself.
  4. Select Connect. A GlockApps page opens.
  5. Paste your API key and approve. That is the only time you need it.
On Team and Enterprise plans a custom connector has to be added by an Owner or Primary Owner.

Claude Desktop

Through the Connectors panel. In the chat window, open Settings then Connectors, choose Add custom connector, paste the address and complete the same authorisation as above. This is the simpler route and the one to prefer.

Through the config file. If you would rather declare it in configuration, add this to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows, then quit and reopen Claude Desktop.

{
  "mcpServers": {
    "glockapps": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.glockapps.com/mcp"]
    }
  }
}

mcp-remote bridges the config file to a remote server and opens your browser for the GlockApps authorisation step. It needs Node.js 18 or newer. No API key goes in the file.

Claude Code (CLI)

Add the server from the command line:

claude mcp add --transport http glockapps https://api.glockapps.com/mcp

Then run /mcp inside Claude Code and select GlockApps to authorise. Your browser opens the GlockApps page that asks for your API key.

If you have already connected GlockApps in Claude on the web, that authorisation does not carry over to the CLI; each client authorises once.

ChatGPT

  1. Open Settings, then Connectors.
  2. Choose Add and paste the connector address.
  3. Select Connect, then paste your API key on the GlockApps page that opens.

Connector support varies by ChatGPT plan. If you cannot find the Connectors screen, your plan does not include custom connectors yet.

Cursor

Through settings. Open Cursor Settings, then Tools & MCP, and choose Add new MCP server. Select the Streamable HTTP type, name it glockapps and paste the connector address as the URL.

Through the config file. Edit ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{
  "mcpServers": {
    "glockapps": {
      "url": "https://api.glockapps.com/mcp"
    }
  }
}

Restart Cursor. The tools appear in Agent mode, and the first call opens the GlockApps authorisation page.

Any MCP-compatible client

The connector is a remote MCP server over Streamable HTTP at the address above. It authenticates with OAuth 2.1 and advertises its endpoints through the standard discovery documents, so a conformant client needs nothing beyond the URL. There is no client ID or secret to obtain: the connector registers clients dynamically.

  • Transport: Streamable HTTP
  • Server URL: https://api.glockapps.com/mcp
  • Authentication: OAuth 2.1, authorisation code with PKCE

Clients that cannot open a browser can reach it through mcp-remote, as in the Claude Desktop section above.

First prompts to try

Once the connector is attached, ask in plain language. A good first move is to confirm it can see your account.

  • "Start an inbox placement test and give me the seed addresses."
  • "Has the test started receiving? Where is it landing so far?"
  • "Why did this campaign go to spam at Outlook?"
  • "Compare this test with the one from yesterday. Did the SPF fix work?"
  • "Give me a shareable link to the full report."
Starting a test gives you a seed list and a marker. You still have to send your campaign to those addresses from the system you are testing, with the marker attached. GlockApps does not send the campaign, and a test that never receives a tagged send reports nothing.

Troubleshooting

The connector says API access is not enabled

Your plan does not include API access. Upgrade to a plan that does, and the connection starts working without reconnecting.

It says there are not enough points

Each test costs one point. Top up your balance, or run the test from Inbox Insight instead.

The test never finishes and shows nothing

Almost always a missing marker. The send has to carry the header or body line the connector gave you, or GlockApps cannot match it to the test. Delete the test, which returns the point while no results have arrived, and send again with the marker.

Results are still trickling in hours later

Normal. Most providers report within ten minutes, but smaller ones accept mail slowly and can keep arriving for hours, occasionally a day.

My API key was reissued

Nothing to do. The connector reads the key from your account on each request rather than storing a copy, so a new key is picked up within a minute.

The client cannot find the server

Check the address for a trailing slash or a missing "s" in https. If your client asks for a transport, it is Streamable HTTP, not SSE.

Still stuck? Contact support and tell us which client you are connecting from.

Test Email Deliverability with Your AI Assistant

Connect the GlockApps MCP server to your AI assistant and get 2 free spam tests to try it out. Run your first test and see where your email lands.