Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hc.starbridge.ai/llms.txt

Use this file to discover all available pages before exploring further.

The Starbridge MCP is currently in beta. It leverages your existing bridges and cannot create or edit bridges directly — see Not yet supported for details.

​
Overview

The Starbridge MCP brings your bridges, feed, signals, and buyer research directly into any AI environment that supports the Model Context Protocol. Plug Starbridge into your existing agents, skills, and workflows in minutes — every draft, digest, and prep doc grounded in live Starbridge data. Use the Starbridge MCP to:
  • Ground pre-meeting and outbound prep agents in live Starbridge signals and contacts
  • Pull bridge data into your favorite tool to build vendor-presence maps, attribute breakdowns, or other buyer insight visualizations
  • Surface Starbridge data in places like Slack or wherever your team works today — on a scheduled cadence that fits your workflow

​
Install the MCP

The Starbridge MCP installs as a custom connector in any client that supports MCP with OAuth.
Connector URL: https://dashboard.starbridge.ai/mcp/oauth
1

Open the connector settings

In Claude, go to Customize → Connectors.
2

Add a custom connector

Click + Add custom connector and paste the connector URL:
https://dashboard.starbridge.ai/mcp/oauth
3

Complete OAuth

Authorize Starbridge when prompted. You’ll sign in with the same credentials you use for the Starbridge web app.

​
What’s supported

Everything you need to bring Starbridge into your agents:
  • Bridges — pull rows and data from every bridge in your workspace.
  • Feed — pull your Starbridge feed, automatically tailored to your territory if one is set.
  • Buyer signals & summary — pull recent signals for any buyer alongside their summary. Ideal for pre-call research.
  • Buyer contacts — pull verified contacts at a buyer directly from Starbridge.
  • Deep buyer research — run one-off research across meetings, purchases, and RFPs that Starbridge has — even outside your existing bridges.

​
Not yet supported

The following are on the roadmap but not available in the current beta:
  • Creating or editing bridges. The MCP is read-only today — bridges should be created and edited inside the Starbridge app.
  • Territory- or TAM-wide analysis without a bridge. MCP analysis is scoped to a single buyer or small set. For full territory or TAM breadth, build a bridge in Starbridge first, then consume it via the MCP.

​
Where to start

Augment your prep skills

Add MCP calls to your pre-meeting or outbound email prep agents — every draft grounded in live Starbridge signals and contacts.

Visualize your bridges

Pull bridge data into your favorite tool to build vendor-presence maps, attribute breakdowns, or other buyer insight visualizations.

Consume Starbridge where you live

Build custom digests to surface Starbridge data in places like Slack or wherever else your team works today — use a scheduled task to pull fresh data through the MCP on a cadence that fits your workflow.

​
FAQ

Any Starbridge user with an active seat can connect the MCP using their existing credentials. Data access through the MCP respects the same territory and permission scopes as the Starbridge web app.
Yes — during the beta, the Starbridge MCP is read-only. Creating or editing bridges, as well as bulk actions like contact enrichment must be done inside the Starbridge app.
Any MCP-compatible client that supports OAuth, including Claude (desktop & web), ChatGPT, Cursor, Cline, and Goose.
Reach out to the Starbridge team at support@starbridge.ai with any questions or feedback during the beta.