Bourd
Integrations

MCP server

Connect Bourd to any MCP-compatible AI assistant. Run prompts, explore citations, and manage workspaces directly from ChatGPT, Claude, or your tool of choice.

Bourd now ships a Model Context Protocol (MCP) server, letting you work with your accounts, workspaces, prompts, citations, and competitors directly from any MCP-compatible AI assistant (ChatGPT, Claude, Cursor, and more) without leaving your conversation.

What’s new

  • Hosted MCP server: Connect any MCP-compatible client to https://mcp.geo.bourd.dev/mcp.
  • OAuth sign-in: Authenticate with your existing Bourd account via Google or email OTP. No API keys to copy around.
  • Multi-account support: Switch between accounts and workspaces mid-conversation; the server maintains your selected context.
  • Tool coverage: List accounts and workspaces, create and run prompts, manage tags and competitors, and explore citations and insights, all from your assistant.

Why this matters

Brand monitoring rarely happens in isolation. You’re usually mid-conversation with an AI assistant about positioning, a competitor, or a content gap, and pulling data out of Bourd means breaking flow to open another tab.

With the MCP server connected, your assistant can query your workspace directly:

  • “What are the top cited domains across my prompts this month?”
  • “Run my competitor comparison prompt against GPT-5.2 and Claude Opus 4.6.”
  • “Which competitors are being mentioned alongside us most often?”

The assistant handles the tool calls; you stay in the conversation.

How to use

Most MCP-compatible clients support remote servers over HTTP. Add a connector pointing to:

https://mcp.geo.bourd.dev/mcp

Then sign in with your Bourd account when prompted. The exact steps vary by client. For example, Settings → Connectors in ChatGPT and Claude, or claude mcp add bourd --transport http https://mcp.geo.bourd.dev/mcp on the Claude Code CLI.

See the MCP Server guide for the full tool list, example workflows, and per-client setup instructions.