Use in your agent

Wire buzzabout's MCP server into any MCP-capable client — Claude, Cursor, ChatGPT, your own SDK-built agent.

The buzzabout MCP server speaks the Model Context Protocol — any MCP-capable client can connect. This page covers the wiring for the most common hosts plus the SDK pattern for your own agent.

Endpoint

https://mcp.buzzabout-staging.com/mcp/

Streamable HTTP. Trailing slash required. See Authentication for x-api-key vs OAuth/JWT.

Wire it up

Settings → Developer → Edit Config opens claude_desktop_config.json. Add a buzzabout entry under mcpServers:

claude_desktop_config.json

{
  "mcpServers": {
    "buzzabout": {
      "transport": "streamable-http",
      "url": "https://mcp.buzzabout-staging.com/mcp/"
    }
  }
}

On first tool call Claude opens an OAuth tab. Sign in with your buzzabout account; Claude stores the JWT locally and replays it on subsequent calls.

Settings → Integrations → Add custom. Available on Team / Enterprise plans.

Field	Value
Name	`buzzabout`
URL	`https://mcp.buzzabout-staging.com/mcp/`
Auth	OAuth (Claude handles the redirect)

Settings → Cursor Settings → MCP → Add new MCP server.

~/.cursor/mcp.json

{
  "mcpServers": {
    "buzzabout": {
      "transport": "streamable-http",
      "url": "https://mcp.buzzabout-staging.com/mcp/",
      "headers": {
        "x-api-key": "bz_live_..."
      }
    }
  }
}

Cursor doesn't ship an OAuth flow for custom MCP servers — use the x-api-key path. Mint a key under Settings → API keys in the buzzabout web app.

Add the buzzabout MCP server as a Custom GPT action targeting the streamable-HTTP transport. Auth: Custom (header) → x-api-key: bz_live_....

ChatGPT's tool model exposes one tool per registered action — see Tools reference for the inventory.

For your own agent, use one of the official MCP SDKs.

agent.py

import asyncio
import os

from mcp import ClientSession
from mcp.client.streamable_http import streamablehttp_client


async def main() -> None:
    headers = {"x-api-key": os.environ["BUZZABOUT_KEY"]}

    async with streamablehttp_client(
        "https://mcp.buzzabout-staging.com/mcp/",
        headers=headers,
    ) as (read, write, _):
        async with ClientSession(read, write) as session:
            await session.initialize()

            tools = await session.list_tools()
            print(f"loaded {len(tools.tools)} buzzabout tools")

            result = await session.call_tool(
                "buzzabout__list_datasets",
                arguments={"limit": 5},
            )
            print(result.content)


asyncio.run(main())

A first prompt

Once the server is wired in, try this in any MCP-capable assistant:

"Create a new dataset called 'cold brew' and kick off a Reddit run for the search query 'cold brew' over the last week. When it's done, list the top 5 mentions sorted by engagement and summarise the hooks they use."

A typical agent loop:

buzzabout__create_dataset → returns a new dataset_id.
buzzabout__create_dataset_run with the search query.
buzzabout__get_dataset_run polled until status is completed.
buzzabout__list_mentions with the new dataset_id, sorted by engagement_rate, limit=5.
The agent summarises the mentions and renders citations.

Every tool call is visible in the host's UI — inspect what was sent and what came back.

Trim the tool surface

The MCP server registers ~32 tools across 9 groups. If you only need a subset, append ?groups=... to the connection URL:

https://mcp.buzzabout-staging.com/mcp/?groups=datasets,mentions,chat

The handshake tools/list response will only include the named groups. Full inventory and group names live in Tools reference.

Most MCP hosts (Claude Desktop, Claude.ai, Cursor, ChatGPT) also let the user toggle individual tools in their settings UI — useful for trimming further on a per-conversation basis.

Troubleshooting

Empty tool list or silent failure

Trailing slash? https://mcp.buzzabout-staging.com/mcp/ (with trailing slash). The unslashed /mcp redirects via 307, which strips the request body in many MCP clients.

Auth? OAuth tokens expire — sign out and back in via the host's integration settings. API keys can be revoked via the buzzabout web app's Settings → API keys.

Plan? API access is gated by plan tier. GET /v1/me returns plan.features.mcp — if it's false, the surface is disabled.

If the tools list is empty, the most likely causes are:

Auth failure — sign out and back in (OAuth) or check key validity (x-api-key).
Network proxy / firewall — outbound HTTPS to mcp.buzzabout-staging.com/mcp/ is blocked.
Account lacks access — your plan must include MCP.

Still stuck? Mail support@buzzabout.ai with the request id from any failed call.

Next steps

Tools reference — every tool the surface exposes.
Authentication — x-api-key vs OAuth details.
MCP overview — the surface at a glance.