MCP Server
Connect Claude — or any MCP-compatible AI assistant — to ProductBridge with a bearer token, capability URL, or OAuth 2.1. Let Claude read your feedback, search semantically, create posts, and update the roadmap from any conversation.
What Is the MCP Server?
ProductBridge ships an MCP (Model Context Protocol) Server that exposes your workspace to AI assistants. Once connected, Claude can:
- Search and read feedback, roadmap items, and changelog entries
- Find semantically similar feedback ("anything else that sounds like this?")
- Create new feedback posts, roadmap items, and changelog entries
- Look up boards, statuses, tags, categories, and user segments
- Filter feedback by user segment ("what are Enterprise customers asking for?")
- Upvote feedback on behalf of a user
The connection is scoped to your organization — Claude only ever sees your workspace's data. Authenticate with a bearer token, a capability URL (for clients that can't set headers), or OAuth 2.1.
MCP is an open protocol from Anthropic. While these docs focus on Claude Desktop and Claude.ai, the same connection works with any MCP-compatible client.
How It Works
Claude calls a tool, the MCP server verifies your bearer token, scopes the call to your organization, runs it against your data, and streams the result back. No data leaves your workspace's boundary.
Connect Claude in Three Steps
Generate your connection config
In the ProductBridge admin, go to Settings → Connect → MCP Server and click Generate MCP Config.
ProductBridge generates:
- A Server URL to connect to (
https://mcp.productbridge.io/mcp, Streamable HTTP transport) - A Bearer token (shown with a reveal/hide toggle — copy it from the field)
- A Capability URL — a secret-embedded URL for clients that can't set headers, like Claude.ai
- A Key prefix — a short identifier for the token used in audit displays
- Ready-to-paste config snippets for Claude Desktop and Claude Code
Treat the bearer token and capability URL as production secrets. If you suspect either is exposed, click Regenerate to issue fresh ones — the old credential becomes invalid immediately.
Paste into your Claude client
Open your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Paste the config snippet ProductBridge generated:
{
"mcpServers": {
"productbridge": {
"type": "http",
"url": "https://mcp.productbridge.io/mcp",
"headers": {
"Authorization": "Bearer pb_your_token_here"
}
}
}
}
Restart Claude Desktop for the change to take effect.
Claude.ai can't set custom headers, so it uses the Capability URL instead of the bearer token.
- Copy the Capability URL from the MCP Server settings page (
https://mcp.productbridge.io/c/{secret}/mcp) - In Claude.ai, go to Settings → Connectors → Add custom connector
- Paste the Capability URL as the server URL
Claude.ai picks up the connection immediately — no restart needed.
The capability URL embeds your credential. Treat it like a password — anyone with the URL can access your workspace's tools.
Any client that speaks MCP can connect:
- Transport: Streamable HTTP (stateless)
- URL:
https://mcp.productbridge.io/mcp - Auth: pick whichever method your client supports:
- Bearer token —
Authorization: Bearer pb_...header - Capability URL — use
https://mcp.productbridge.io/c/{secret}/mcpas the server URL when headers aren't configurable - OAuth 2.1 — for clients with built-in MCP OAuth support; the server advertises itself via
/.well-known/oauth-protected-resourceand issues tokens with themcp:toolsscope
- Bearer token —
Point your client at the URL with one of these credentials and the tools become available.
Try it out
In Claude, try a prompt like:
"Use ProductBridge to list the top 10 feedback posts from Enterprise customers."
Claude will call the appropriate MCP tools — you'll see the tool calls appear inline — and respond grounded in your real data.
What Claude Can Do
The MCP Server exposes 22 tools across four areas. Claude picks the right ones automatically based on your prompt.
Feedback
| Tool | What It Does |
|---|---|
get_feedback_list | List feedback posts with filters (status, category, search, pagination) |
search_similar_feedback | Semantic vector search — "find anything that sounds like this" |
get_feedback_by_segment | List feedback posts from users in a specific segment |
create_feedback | Create a new feedback post |
update_feedback | Update title, description, board, status, category, or tags |
upvote_feedback | Toggle an upvote on a post |
Roadmap
| Tool | What It Does |
|---|---|
get_roadmap | List roadmap items grouped by status |
create_roadmap_item | Create a new roadmap item with title, description, ETA, effort, impact |
Changelog
| Tool | What It Does |
|---|---|
get_changelog | List changelog posts with status, type, and label filters |
create_changelog | Create a new changelog entry (draft or published) |
Configuration & Lookups
| Tool | What It Does |
|---|---|
list_feedback_boards | List all feedback boards in your workspace |
list_roadmap_boards | List all roadmap boards |
list_feedback_statuses / list_roadmap_statuses | List available statuses |
list_feedback_categories / list_roadmap_categories | List available categories |
list_feedback_tags / list_roadmap_tags | List available tags |
list_changelog_status_codes / list_changelog_types / list_changelog_labels | List changelog metadata |
list_user_segments | List user segments — use these IDs with get_feedback_by_segment |
Claude reads the tool descriptions, decides which ones it needs, and composes them. You don't need to memorize the names — just ask in plain English.
Example Conversations
Connection Management
Regenerate Your Token
If your token is exposed or you want to refresh it:
- Go to Settings → Connect → MCP Server
- Click Regenerate
The old token — and the capability URL derived from it — is invalidated immediately. You'll need to update your Claude config with the new credential.
Credential Name & Key Prefix
Each connection carries a read-only Credential name (mcp by default) and a Key prefix — a short identifier shown in the UI so you can recognize the token without revealing it. Use the show/hide toggle next to the bearer token field when you need to copy it.
One Active Credential per User
Each user has one active MCP credential per organization. You can't create multiple parallel keys — clicking Regenerate rotates the credential, invalidating the old token and issuing a new one. If several machines share your credential, update all of them after a rotation.
Scope & Security
| Detail | |
|---|---|
| Organization scope | Every tool call is scoped to the organization the credential belongs to. Claude can never see another workspace's data. |
| Auth methods | Bearer token (Authorization: Bearer pb_... header), capability URL (/c/{secret}/mcp for header-less clients), or OAuth 2.1 (mcp:tools scope, discovery via /.well-known/oauth-protected-resource) |
| Token storage | Tokens are SHA-256 hashed and encrypted at rest. We never log raw tokens. |
| Read + write | MCP tools can create and update content. Regenerate the credential immediately if exposed. |
| Audit trail | Errors and key activity are logged on the server side for support investigation. |
Treat your MCP bearer token like a production API key — never paste it into chats, screenshots, or commits. Rotate it immediately if it ends up somewhere it shouldn't.