Skip to content

MCP Server

Bourd’s MCP server lets you interact with your workspaces, prompts, citations, and competitors directly from Claude. Ask Claude to run analysis, check brand mentions, or explore citation data without leaving your conversation.

The server is available at:

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

The Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude connect to external tools and data sources. When you connect Bourd’s MCP server to Claude, it gains access to your Bourd data and can perform actions on your behalf.

  1. Open Claude.ai and go to Settings → Connectors.
  2. Click Add Connector and enter the server URL: https://mcp.geo.bourd.dev/mcp
  3. You will be redirected to sign in with your Bourd account (Google or email OTP).
  4. Once authenticated, Bourd’s tools are available in your conversations.
  1. Open Claude Desktop and go to Settings → Connectors.
  2. Click Add and enter the server URL: https://mcp.geo.bourd.dev/mcp
  3. Complete the sign-in flow when prompted.

Add the server using the CLI:

Terminal window
claude mcp add bourd --transport http https://mcp.geo.bourd.dev/mcp

After connecting, Claude needs to know which account and workspace to use. A typical first interaction looks like this:

  1. List your accounts — Ask Claude to show your available accounts.
  2. Select an account — Tell Claude which account to use.
  3. Explore your workspace — Ask Claude to list workspaces, then start working with prompts, citations, or competitors.

You: What accounts do I have access to in Bourd?

Claude: You have access to 2 accounts: “Acme Corp” (Admin) and “Side Project” (Member).

You: Use Acme Corp. Show me the workspaces.

Claude: Acme Corp has 3 workspaces: “Marketing”, “Product”, and “Competitive Intel”.

You: In the Marketing workspace, what are the top cited domains across all my prompts?

Claude: Here are the top cited domains…

Bourd’s MCP server provides 18 tools organized by category.

ToolDescription
List AccountsList all accounts you have access to. Run this first.
Select AccountChoose which account to work with. Required before accessing workspaces.
List WorkspacesList workspaces in the selected account.
ToolDescription
List PromptsList prompts in a workspace, including their tags and status.
Create PromptCreate a new prompt with optional tags and personas.
Run PromptExecute a prompt against one or more AI models (e.g., GPT-4.1, Claude Sonnet).
List Prompt ResponsesView AI model responses for a specific prompt, including brand mentions and citations.
Tag PromptsBulk-update tags on multiple prompts at once.
ToolDescription
List TagsList all tags in a workspace.
Create TagCreate a new tag for organizing prompts.
Delete TagPermanently delete a tag and remove it from all prompts.
ToolDescription
List CitationsView citation analytics — which sources AI models cite, grouped by domain or path. Filter by model, prompt, tag, or content type.
Get Path ExtractionGet the extracted content and metadata for a specific cited URL.
ToolDescription
List InsightsView AI-generated insights about your brand’s visibility and performance.
ToolDescription
List CompetitorsList tracked competitors with analytics: mention count, sentiment, share of voice, and more.
Create CompetitorAdd a new competitor or brand to track.
Update CompetitorUpdate a competitor’s name, description, or URL.
Delete CompetitorPermanently remove a competitor from tracking.

Find Underperforming Prompts and Improve Content Strategy

Section titled “Find Underperforming Prompts and Improve Content Strategy”

A multi-step workflow that identifies weak spots and turns them into an action plan:

You: In the ACME account, Demo workspace, find the worst three performing prompts.

Claude: Based on brand_mention_percent, the three lowest-performing prompts are:

  1. “What tools do teams use for async communication?” — 0% brand mention
  2. “Best solutions for document collaboration” — 4% brand mention
  3. “How do companies manage project timelines?” — 8% brand mention

You: Great. Now can you list the top 10 citations for the prompt “What tools do teams use for async communication?” and help me analyze them to prepare a content strategy?

Claude: Here are the top 10 cited sources for that prompt. Most citations point to comparison articles and listicles on domains like zapier.com and hubspot.com. Your domain doesn’t appear at all. To improve visibility, consider creating a comparison guide targeting the same keywords these cited pages rank for…

Build a Prompt Tracking Strategy from Scratch

Section titled “Build a Prompt Tracking Strategy from Scratch”

When starting fresh, use Claude as a strategist. Combine Bourd with other connectors (Google Drive, Notion, Slack) to pull in your existing knowledge and build a tailored set of prompts:

You: I’m setting up Bourd for the first time. I need to figure out what prompts to track for our brand. Can you pull up our ICP doc from Notion and our product positioning page from Google Drive?

Claude: I found your ICP document — your primary audience is mid-market B2B SaaS teams, and your positioning focuses on workflow automation and integrations. Based on this, here are prompt categories worth tracking:

  • Discovery prompts: “What are the best workflow automation tools?”
  • Comparison prompts: “How does [Your Brand] compare to [Competitor]?”
  • Use-case prompts: “How do mid-size teams automate their onboarding process?”
  • Problem prompts: “How do I reduce manual data entry across tools?”

Want me to create these in your Bourd workspace?

You: Yes, create them in the Marketing workspace. Tag the first group as “discovery” and the second as “competitive”.

Claude: Done — I’ve created 8 prompts across the two tags. Want me to run them against a few models to get your first baseline data?

“Create a prompt asking ‘What are the best project management tools?’ and run it against GPT, Claude and Gemini models. Then show me which models mentioned our brand and what they cited.”

“Show me competitor analytics — which brands have the highest share of voice and average sentiment? How do we compare?”

“Tag all prompts related to pricing with the ‘pricing’ tag. Create the tag first if it doesn’t exist.”

“Show me any new insights that have been generated since I last checked. What trends are emerging?”

Bourd’s MCP server uses OAuth 2.0. When you first connect, you’ll be asked to sign in with your Bourd account using either:

  • Google Sign-In — One-tap authentication with your Google account.
  • Email OTP — Enter your email to receive a one-time code.

Your session is maintained automatically. If your session expires, Claude will prompt you to disconnect and reconnect.

Tools that return lists support cursor-based pagination. By default, results are limited to 25 items per request. If there are more results, Claude will automatically handle pagination when you ask for more data. You can also explicitly request a specific page size (1–100 items).

If something goes wrong, the MCP server returns clear error messages:

  • “No account selected” — Run the account selection step first.
  • “Session expired” — Disconnect and reconnect the MCP server in your Claude settings.
  • “Not found” — The requested resource doesn’t exist or you don’t have access.
  • Validation errors — The request had invalid parameters. The error message includes details about which fields need correction.

Your authentication tokens have expired and cannot be renewed. Disconnect the Bourd connector in Claude settings, then reconnect and sign in again.

Ensure you’ve completed the OAuth sign-in flow. If the sign-in window closed unexpectedly, disconnect and try adding the connector again.

Most tools require an active account context. Ask Claude to list your accounts and select one before using workspace tools.

The MCP server fetches live data from Bourd’s API on every request. If you recently made changes in the Bourd UI, they should appear immediately in Claude. If not, try asking Claude to re-fetch the data.

The MCP server acts on your behalf using your authenticated session. It accesses only the data you request and does not store conversation content. See our Privacy Policy for full details on data handling.