FeatureOS

FeatureOS MCP Server

The official Model Context Protocol server for FeatureOS, the product feedback, roadmap and changelog platform.

Connect it to Claude, Cursor, Gemini CLI or any MCP client, then triage feature requests, merge duplicates, assign owners, tag posts, publish changelogs and update help-center articles in plain language, against your live FeatureOS workspace.

This is a hosted remote server. There is nothing to install or run.

Connect

Claude Code

claude mcp add --transport http featureos https://mcp.featureos.app/mcp

Or add it to your MCP config file:

{

"mcpServers": { "featureos": { "type": "http", "url": "https://mcp.featureos.app/mcp" } } }

Claude Desktop

1. Open Settings → Connectors and click Add custom connector.
2. Name it FeatureOS and paste https://mcp.featureos.app/mcp.
3. Click Add, then Connect, and approve access in the browser.

Cursor

In Cursor's MCP settings, add a new server with the URL https://mcp.featureos.app/mcp, or add the same JSON block shown above to your MCP config file.

Gemini CLI

gemini extensions install https://github.com/featureos/featureos-mcp

This repo ships a gemini-extension.json that points Gemini CLI at the hosted server.

Other clients

Any client with remote MCP support: add a new remote server, paste https://mcp.featureos.app/mcp, and complete the sign-in when the browser opens.

Verify the connection

Ask: *"What are the top feature requests in my FeatureOS workspace?"* Real posts from your boards mean you are connected.

Authentication

On first connect your browser opens the FeatureOS sign-in page. Log in to the workspace you want and approve access. No API key or token goes in your config file.

Scopes requested: posts, comments, votes, tags, changelog, articles, collections, customers (read and write), roadmap:read, webhooks:manage.

Revoke access any time under Dashboard → Organization Settings → Advanced.

Several workspaces? MCP clients store one login per URL. Use an org-scoped URL to give each workspace its own connection: https://mcp.featureos.app/ /mcp.

Tools

IDs are opaque: the assistant gets them from a prior tool call (for example list_buckets before list_feature_requests). List tools return one page at a time.

Example prompts

• "List all feature requests with status Under Review on the Product board, sorted by votes."
• "Show me posts submitted in the last 7 days that are still unapproved."
• "Get the full details of feature request 1234, then show the latest 10 comments."
• "Find duplicates of 'dark mode' and merge them into the most-voted post."
• "Assign post 1234 to alice@example.com and tag it ux."
• "Draft a changelog for everything we shipped this week and label it Improvement."
• "Search the help center for SSO and update the setup article with the new steps."

Learn more

• How to manage feedback via Claude Code
• AI feedback triage workflows
• FeatureOS MCP integration guide
• FeatureOS Developer API
• Pricing: see featureos.com/pricing

License

Apache-2.0. See LICENSE.