FeatureOS
io.github.featureosPublished by GitHub account featureosv1.0.0Updated Nov 6, 2026
Manage FeatureOS feedback boards, roadmaps, changelogs and help-center articles from any MCP client.
Overview
Hosted FeatureOS MCP server that lets an assistant triage feedback boards, roadmaps, changelogs and help-center articles in your live workspace.
- What you can do
- List, search, create and update feature requests, assign owners, merge duplicates and manage tags and attachments
- Read, write and pin comments, and list upvoters or downvoters or cast a vote
- List, search, create and update changelogs and manage their labels
- List, search, create, update and delete help-center articles and inspect collections
- Inspect workspace boards, tags, statuses, organization and customers, and list, invite or update team members
- When to use it
- Useful when your team runs product feedback, roadmaps and changelogs on FeatureOS and you want an assistant to triage requests, merge duplicates, draft changelogs or edit help-center articles without switching to the dashboard.
- Requirements
- A hosted remote endpoint over Streamable HTTP; nothing to install. OAuth 2.0 browser sign-in on first connect, with no API key in the config. Access follows your FeatureOS role. For several workspaces, use an org-scoped URL so each workspace gets its own login.
Installation
In SourceWeft
- Open FeatureOS in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.featureos%2Ffeatureos-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"featureos": {
"type": "http",
"url": "https://mcp.featureos.app/mcp"
}
}
}README
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
Or add it to your MCP config file:
Claude Desktop
- Open Settings → Connectors and click Add custom connector.
- Name it
FeatureOSand pastehttps://mcp.featureos.app/mcp. - 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
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/<your-org-slug>/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 [email protected] 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.
Source: README.md at commit 60a8e95
Tools
0Version history
1- v1.0.0LatestNov 6, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts