BOARDHERALDDocs
// agents.quick_start

Quick start

Three flavours — pick the one that matches your client. Copy the snippet, swap in your tenant URL and API key, restart the client.

Before you paste anything, you'll need two things: your BoardHerald URL and an API key. The URL is https://app.boardherald.com for most tenants; if you're on a white-label subdomain or a custom domain (e.g. board.acme.com), use that instead. Get the key from Profile → API Keys in the app — keys start with bh_ and are shown exactly once.

Claude Desktop

Drop this block into claude_desktop_config.json and restart Claude Desktop. On macOS the config lives at ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows, %APPDATA%\Claude\claude_desktop_config.json.

claude_desktop_config.jsonjson
{
  "mcpServers": {
    "boardherald": {
      "command": "npx",
      "args": [
        "-y",
        "@boardherald/mcp-bridge",
        "--api-key", "bh_REPLACE_WITH_YOUR_KEY",
        "--url", "https://app.boardherald.com"
      ]
    }
  }
}

Once connected, ask Claude something like "list my upcoming board meetings" — it'll call meetings_list under the hood.

ChatGPT

ChatGPT's MCP connector is rolling out. The exact location of this block depends on the current OpenAI docs — verify there first. ChatGPT speaks the remote transport natively, so the bridge isn't needed.

json
{
  "type": "mcp",
  "url": "https://app.boardherald.com/api/mcp",
  "headers": {
    "Authorization": "Bearer bh_REPLACE_WITH_YOUR_KEY"
  }
}
Beta
OpenAI is iterating on the MCP connector surface — the config shape may change. Check their docs for the authoritative version and fall back to the raw transport below if you hit trouble.

Any MCP client (raw transport)

If your client speaks HTTPS and JSON-RPC directly, skip the bridge entirely and POST to the tenant endpoint.

http
POST https://app.boardherald.com/api/mcp
Authorization: Bearer bh_REPLACE_WITH_YOUR_KEY
Content-Type: application/json
Accept:       application/json, text/event-stream

# body: any JSON-RPC 2.0 MCP message
# protocol: 2025-11-25

Responses stream as Server-Sent Events when the tool supports it (e.g. long-running exports); otherwise they come back as plain JSON. Either way you send back a standard JSON-RPC reply.

Next