Inside the AIyou already use.

1. In Claude, open Customize > Connectors (in some versions Settings > Connectors), click + and choose Add custom connector. On Team and Enterprise plans an owner adds it first under Organization settings > Connectors; members then click Connect.
2. Name: Buzz Dealer AI. Server URL:

3. Keep the sign-in settings Claude suggests (sign in, Claude's own OAuth client) and click Add, then Connect.
4. Sign in and approve. Your agent sees the tools at once.

When the client opens our sign-in page, sign in, choose the account, choose the brands it may use and whether it may order, then approve. You can revoke the connection in the dashboard under Connections.

Free Claude plans allow one custom connector. Claude Code: claude mcp add --transport http buzzdealer-ai https://mcp.buzzdealer.ai/mcp, then /mcp to sign in.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

Plans: Business, Enterprise and Edu get every tool, including ordering. Pro connects in read only mode: your agent can search, plan, check and follow orders, but cannot place them.

1. On Business, Enterprise and Edu, a workspace admin first allows it: Workspace settings > Permissions & roles > Developer mode (custom connectors).
2. In ChatGPT on the web, open Settings > Apps > Advanced settings and turn on Developer mode.
3. Click Create. Name: Buzz Dealer AI. MCP server URL:

4. Authentication: OAuth. Confirm that you trust the app and click Create.
5. Sign in and approve. In a chat, choose Developer mode and turn on Buzz Dealer AI.

When the client opens our sign-in page, sign in, choose the account, choose the brands it may use and whether it may order, then approve. You can revoke the connection in the dashboard under Connections.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

Add to Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "buzzdealer-ai": {
      "url": "https://mcp.buzzdealer.ai/mcp"
    }
  }
}

Cursor shows the server under Settings > MCP with a Login button: sign in and approve.

When the client opens our sign-in page, sign in, choose the account, choose the brands it may use and whether it may order, then approve. You can revoke the connection in the dashboard under Connections.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

Install in VS Code

Or add it to .vscode/mcp.json in your workspace (or run MCP: Add Server). VS Code opens our sign-in page in your browser:

{
  "servers": {
    "buzzdealer-ai": {
      "type": "http",
      "url": "https://mcp.buzzdealer.ai/mcp"
    }
  }
}

With a personal API key instead of signing in, VS Code asks for the key once and stores it securely:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "buzzdealer-key",
      "description": "Buzz Dealer AI API key",
      "password": true
    }
  ],
  "servers": {
    "buzzdealer-ai": {
      "type": "http",
      "url": "https://mcp.buzzdealer.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${input:buzzdealer-key}"
      }
    }
  }
}

Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

Gemini app

1. On gemini.google.com, open Settings > Connected Apps and, under Custom apps, click Add a custom app.
2. Server URL:

3. Sign in and approve. The app is then also available in Gemini on your phone.

Google offers custom apps on the web to adults in the US with a personal Google account and Keep Activity turned on.

Gemini CLI

gemini mcp add --transport http buzzdealer-ai https://mcp.buzzdealer.ai/mcp

The CLI finds our sign-in on its own. With an API key instead, add --header "Authorization: Bearer YOUR_API_KEY".

When the client opens our sign-in page, sign in, choose the account, choose the brands it may use and whether it may order, then approve. You can revoke the connection in the dashboard under Connections.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

1. Go to grok.com/connectors, click New Connector and choose Custom.
2. Name: Buzz Dealer AI. Server URL:

3. Complete the sign-in Grok opens, and approve.

When the client opens our sign-in page, sign in, choose the account, choose the brands it may use and whether it may order, then approve. You can revoke the connection in the dashboard under Connections.

On Grok Business and Enterprise an admin adds the connector in the console.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

1. In Perplexity, open Settings > Connectors and click Add custom connector (Pro, Max and Enterprise; on Enterprise an admin allows custom connectors first).
2. Name: Buzz Dealer AI. URL:

3. Transport: Streamable HTTP. Authentication: OAuth. Confirm the risk notice and save.
4. Sign in and approve.

When the client opens our sign-in page, sign in, choose the account, choose the brands it may use and whether it may order, then approve. You can revoke the connection in the dashboard under Connections.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

1. In Manus, open Settings > Integrations > Custom MCP Servers (named Connectors > Add custom MCP in newer versions).
2. Choose Import by JSON and paste this, with your key:

{
  "mcpServers": {
    "buzzdealer-ai": {
      "url": "https://mcp.buzzdealer.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Or use direct configuration: transport HTTP, the server URL above, and the header Authorization with the value Bearer followed by your key.

Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

1. In your Lindy agent, add an MCP server (Lindy can also set it up when you ask it in chat).
2. Server URL:

3. Add the header Authorization with the value Bearer followed by your API key, then approve the connection.

Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

1. In a Super Agent chat, open Tools (the wrench), click Add, then Add new MCP server.
2. Name: Buzz Dealer AI. Server type: StreamableHttp. Server URL:

3. Request header:

{"Authorization":"Bearer YOUR_API_KEY"}

Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

1. In Devin, open Customize > MCPs (formerly Settings > MCP Marketplace) and click Add custom MCP (organization admins).
2. Transport: HTTP. Server URL:

3. Authentication: an auth header, Authorization, with the value Bearer followed by your API key. Save and test the connection.

Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

Paste this into Muse, with your API key in place of YOUR_API_KEY:

Connect to the Buzz Dealer AI MCP server at https://mcp.buzzdealer.ai/mcp with the header "Authorization: Bearer YOUR_API_KEY". List its tools and test them by calling get_account_status and find_publications. Then save this connection and how to use it as a skill named "Buzz Dealer AI", so you can use it again. Ask me before every step that spends credits.

Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

openclaw mcp add buzzdealer-ai --url https://mcp.buzzdealer.ai/mcp --transport streamable-http --auth oauth
openclaw mcp login buzzdealer-ai

The login opens our sign-in page. Check it with openclaw mcp doctor buzzdealer-ai --probe.

Add our agent skill so OpenClaw knows the order flow: unzip the Buzz Dealer AI skill into ~/.openclaw/skills/ (or your workspace's skills folder).

When the client opens our sign-in page, sign in, choose the account, choose the brands it may use and whether it may order, then approve. You can revoke the connection in the dashboard under Connections.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

Add this to ~/.hermes/config.yaml and put your key in ~/.hermes/.env as BUZZDEALER_API_KEY:

mcp_servers:
  buzzdealer-ai:
    url: "https://mcp.buzzdealer.ai/mcp"
    headers:
      Authorization: "Bearer ${BUZZDEALER_API_KEY}"

To sign in with OAuth instead, leave out headers and add auth: oauth.

Add our agent skill: unzip the Buzz Dealer AI skill into ~/.hermes/skills/.

Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.

After we add new options, disconnect and reconnect the connector so your AI app sees them.

1. Create a key

Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.

2. Use it on the MCP server

Any MCP client that can send a header: the server URL and the header Authorization: Bearer followed by your key.

3. Or call the REST API

Base URL:

curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://api.buzzdealer.ai/v1/publications?region=UK&limit=5"

• Every endpoint is in the OpenAPI document; the tools are listed in llms.txt and on the tools page.
• POST /v1/orders takes an Idempotency-Key header, so a retry never places the same order twice.
• Rate limits per key: reading and ordering each have a limit per minute; over a limit the answer is 429 with retry-after.
• Errors are JSON with error, message and next_step. A revoked key answers 401 with error key_revoked.

After we add new options, disconnect and reconnect the connector so your AI app sees them.