---
title: "Buzz Dealer AI API and MCP Server"
description: "Connect to Buzz Dealer AI: the MCP server address, the REST API and its OpenAPI spec, OAuth sign-in with read, write and spend scopes, API keys and the skill."
canonical: https://buzzdealer.ai/developers
last_updated: 2026-10-22
---

# Buzz Dealer AI API and MCP Server

Everything a developer or an AI agent needs to connect: the MCP server, the REST API and its OpenAPI spec, sign-in, and where the listing lives.

## MCP server

Address: `https://mcp.buzzdealer.ai/mcp` (Streamable HTTP). Add it as a custom connector in Claude, ChatGPT, Cursor or any MCP client. Two tools work without signing in; everything else asks the person to sign in once. Step by step for each client: [Connect](https://buzzdealer.ai/connect).

Machine-readable: the [MCP server card](https://buzzdealer.ai/.well-known/mcp/server-card.json) and the [agent discovery record](https://buzzdealer.ai/.well-known/ard.json). The tools, read-only or spending: [tools reference](https://buzzdealer.ai/tools).

## REST API

Base URL: `https://api.buzzdealer.ai/v1`. The [OpenAPI 3.1 spec](https://buzzdealer.ai/openapi.json) describes every endpoint, the one error format, paging with limit, offset or cursor, and the 202 answers of long jobs. How the API changes: [versioning and deprecation policy](https://buzzdealer.ai/docs/api/deprecation). Concepts and money rules: [Docs](https://buzzdealer.ai/docs).

## Sign-in, scopes and API keys

MCP clients sign in with OAuth 2.1 (PKCE, dynamic client registration, client ID metadata documents). The person chooses the account and the brands, and what the connection may do:

- `read`: See your balance, budget frame, the catalog, quotes, orders, reports and Reputation Agent results. Changes nothing.

- `write`: Save quotes, answer the Reputation Agent's questions, set preferences, start a scan, and start, mark and rate fixes. Spends no credits.

- `spend`: Place orders and order audits, reports and paid rescans within your budget frame, using credits you already added. It can never pay or add credits.

Agents that cannot sign in use a personal API key, created by the account owner in the dashboard under Connections, sent as `Authorization: Bearer <key>` to the MCP server or the REST API. Every order is quoted first, and an agent never pays: it spends credits a person already added, inside the budget frame the person set. How we protect connections: [Security](https://buzzdealer.ai/security).

## For AI agents

- [llms.txt](https://buzzdealer.ai/llms.txt), with a file per section

- [The page written for AI agents](https://buzzdealer.ai/agents), in Markdown

- [The Buzz Dealer AI agent skill](https://buzzdealer.ai/docs/agent-skill) ([zip](https://buzzdealer.ai/downloads/buzzdealer-ai-skill.zip)): connecting, the order flow and the rules, for Claude, OpenClaw and Hermes

- Markdown versions of the main pages, such as [/index.md](https://buzzdealer.ai/index.md) and [/developers.md](https://buzzdealer.ai/developers.md)

## Source and MCP Registry

The listing source, with server.json, AGENTS.md, a Claude Code plugin, the agent skill and a typed client, is at [github.com/buzzdealer-ai/mcp](https://github.com/buzzdealer-ai/mcp). The server is in the official MCP Registry as `io.github.buzzdealer-ai/mcp` ([Registry entry](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.buzzdealer-ai/mcp)).

Questions: [support](https://buzzdealer.ai/contact). Who runs Buzz Dealer AI: [About](https://buzzdealer.ai/about).