ChatterBeamDevelopers
MCP

Model Context Protocol

Connect ChatGPT, Codex, Claude, or another Streamable HTTP MCP client to ChatterBeam’s tool catalog.

Server URL

https://chatterbeam.com/mcp

The endpoint serves both modern MCP 2026-07-28 and the established 2025 handshake revisions. It returns the same { data, meta } envelope as REST and publishes titles, input/output schemas, plus read-only, destructive, and open-world annotations.

Automatic protocol negotiation

Modern clients discover the stateless protocol with server/discover. Existing clients continue to use initialize without changing their configuration.

OAuth-capable clients

  1. Add the MCP server URL.
  2. The client discovers ChatterBeam OAuth and presents its HTTPS metadata URL as its client ID. Legacy clients may dynamically register instead.
  3. ChatterBeam validates the client document, exact callback URI, resource audience, and PKCE challenge.
  4. Sign in, verify the displayed client and callback hostnames, review scopes, and approve access.
  5. The connection appears in Dashboard → Developer → Connections after first use and can be revoked there.
No keys in prompts

Use OAuth for user-facing clients. Only trusted server-side clients should attach a scoped API key header.

Other MCP clients

Generic configuration
{
  "mcpServers": {
    "chatterbeam": {
      "url": "https://chatterbeam.com/mcp",
      "headers": {
        "Authorization": "Bearer ${CHATTERBEAM_API_KEY}"
      }
    }
  }
}

Tool results

Successful calls contain a JSON text block and output-schema-backed structured output. Tool discovery is filtered to the connection’s granted scopes, so read-only agents do not see unavailable write tools. Errors expose only a safe code, message, and request ID. Every tool rechecks its scope, project role, resource boundary, and workspace rate bucket.

Safety

  • CIMD documents must use a public HTTPS URL, match their own client ID exactly, stay below 64 KiB, and declare only validated callback URIs.
  • OAuth requires PKCE S256 and binds every token to the MCP resource audience.
  • Authorization codes are single-use; refresh tokens rotate on every exchange.
  • The Account API access switch immediately blocks every machine credential.
  • Every tool independently enforces scope and minimum role.
  • Multiple keys and OAuth connections share workspace rate buckets.
  • Destructive and open-world operations carry MCP annotations.