Connect Productboard to Meta Muse via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Productboard, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Productboard + Meta Muse

Productboard product management through the REST API v2: read and edit products, components, features, initiatives, objectives and key results, releases, companies and users as entities with custom fields and relationships, capture and search customer feedback notes and link them to features, and look up members and teams.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

PRODUCTBOARD_API_TOKEN

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Productboard workspace on the Pro plan or higher.

1. In Productboard open Settings > Integrations > Public APIs > Access Token and click + to create a token. Copy it right away: it is shown only once.
2. Paste it into PRODUCTBOARD_API_TOKEN, without a Bearer prefix. It is sent as Authorization: Bearer <token> and acts with the rights of the member who created it, so a token of a workspace admin or maker sees the most.
3. Install the connector and run productboard_list_entity_configurations: it confirms the token and lists the entity types of your workspace.

API v2 only: the connector uses the Productboard REST API v2 (https://api.productboard.com/v2). API v1 was deprecated in April 2026 and sunset on 8 July 2026.

Everything is an entity: products, components, features, subfeatures, initiatives, objectives, key results, releases, release groups, users and companies (and competitors and tasks where the workspace has them) are entities with a type. Customer feedback lives in notes.

Discover the workspace first: fields differ per workspace. productboard_list_entity_configurations and productboard_get_entity_configuration show every field of a type (standard ones such as name, description, status, owner, timeframe, teams, tags, and custom fields keyed by UUID), which are required and which patch operations each accepts. productboard_list_note_configurations does the same for notes, productboard_list_field_values lists the options of a select, tag or status field.

What it reads:

• The roadmap: productboard_list_entities with types (for example ["feature"], ["objective", "keyResult"] or ["company"]) and filters by name, owner, status, team, parent or archived state; productboard_search_entities for structured filters on several ids, dates, field values (also custom fields), parents and customers, with a choice of returned fields; productboard_get_entity for one item with its links.html URL.
• The hierarchy: productboard_list_entity_relationships shows parent, children, links and blockers, for example all features of a component.
• Feedback: productboard_list_notes by date, owner, creator, source system, processed or archived state; productboard_search_notes for full-text search combined with tags, customer and linked features; productboard_get_note and productboard_list_note_relationships for one note, its customer and its linked features.
• People: productboard_list_members and productboard_get_member for workspace members, productboard_list_teams and productboard_list_team_members for teams.

What it writes:

• productboard_create_entity creates a feature, component, initiative, objective, key result, release, company and more with type and fields; the parent is set through relationships, for example [{"type": "parent", "target": {"id": "<component id>"}}].
• productboard_update_entity overwrites values with fields or applies patch operations (set, addItems, removeItems, clear) on lists such as tags and teams.
• productboard_set_entity_parent moves an entity under another parent; productboard_create_entity_relationship adds a link, isBlockedBy or isBlocking relationship.
• productboard_create_note captures feedback in the Insights inbox with title, text, tags, owner, source record, customer and linked features; productboard_update_note changes it (for example marks it processed); productboard_link_note attaches a note to a feature or sets its customer.

Nothing to switch off, nothing to delete: no tool is switched off at install because the connector has no delete tools at all. Deleting an entity in API v2 also deletes all its children, so deleting stays in the Productboard app.

Data formats: references are objects: owners as {"email": "[email protected]"} or {"id": "<uuid>"}, a status as {"name": "In progress"}, tags as [{"name": "Q4"}]. timeframe looks like {"startDate": "2026-10-01", "endDate": "2026-12-31", "granularity": "month"}. Note content and rich text fields take simple HTML or plain text. Lists return data, each item with id, type, fields, links.html, createdAt and updatedAt. All ids are UUIDs and times ISO 8601 in UTC. Without the members:pii:read permission owner emails come back as [redacted].

Paging: when links.next is set, the AI takes the pageCursor value from that URL and passes it as page_cursor; it stops when links.next is null.

Limits and common errors: 50 requests per second per token; 429 comes with Retry-After. 401 means a wrong or revoked token, 403 a token whose member lacks the rights for that data, 400 or 422 an unknown field or type: the message names what the workspace accepts, and the AI checks the configuration.

The connector does not delete entities or notes, does not change workspace settings, fields or statuses and does not use the retired API v1.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the Productboard tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

Example prompts

• "List the features in the status In progress with owner and timeframe, grouped by component."
• "Which unprocessed feedback notes from the last two weeks mention onboarding? Summarise the main themes."
• "Create a feature named Dark mode for the mobile app under the Mobile component, owned by [email protected], status New idea."
• "Capture this support ticket as a note from [email protected] and link it to the CSV export feature."
• "Show our objectives and their key results for this quarter, with status and owner."

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Microsoft Copilot