You manage feedback via Claude Code by connecting FeatureOS as a remote MCP server, approving OAuth once, then asking Claude to list, create, update, assign, tag, and merge feature requests against live boards. No API key in git. Actions use your FeatureOS role.

Product managers and eng leads already live in Claude Code. Feedback still lives in another tab: boards, comments, votes, and status updates. That switch is where requests go stale. Connecting FeatureOS to Claude Code keeps triage next to the PR.

TL;DR: Add https://mcp.featureos.app/mcp to Claude Code MCP config, sign in with OAuth, then run prompts like "List Under Review posts on Product sorted by votes." You can create requests, assign owners, score RICE, merge duplicates, and draft changelogs without leaving the terminal.

This is part one of a three-post series:

  1. How to manage feedback via Claude Code (this post)
  2. How to manage changelog via Claude Code
  3. How to keep your knowledge base updated with Claude Code

What is MCP, and how does FeatureOS use it?#

MCP (Model Context Protocol) is a standard that lets AI assistants call tools on remote products. FeatureOS exposes your workspace as a remote MCP server at https://mcp.featureos.app/mcp. Claude Code discovers the tools, you approve OAuth in the browser, then Claude reads and writes FeatureOS data on your behalf.

Unlike pasting feedback into a chat, MCP is live. When Claude lists posts under review, it hits your real boards. When it updates a status, that change lands in FeatureOS.

Read tools fetch data. Write tools change it. Both respect your role (admin, member, CSM). If you cannot approve posts in the UI, Claude cannot either.

What feedback work can you do from Claude Code?#

From Claude Code you can run full feedback board hygiene: list and filter posts, open details and comments, create and update requests, assign owners, manage tags, merge duplicates, and pull votes. The same connection also reaches changelogs, knowledge base reads, boards, tags, team members, and custom statuses.

Feature requests (posts)#

  • List and filter by board, status, tags, submitter or interactor email, date range, and approval status (14 sort options)
  • Get full post details by ID
  • Create posts with title, board, HTML description, tags, custom status, optional Jira link
  • Update title, description, board, status, approval, or scoring (value/effort or RICE)
  • Assign or unassign by team member email
  • Add, remove, or list tags
  • Merge up to 30 duplicates into a parent (votes, comments, subscribers consolidated)
  • List merged children; unmerge a child back out

Comments and votes#

  • List comments on a post (date filters, up to 50 per page)
  • Get, create, or update a comment
  • List upvoters and downvoters

Changelog, knowledge base, and workspace#

  • Changelogs: list, get, create, update, tag, search, link feature requests
  • Knowledge base: list/get articles and collections
  • Workspace: boards, tags, team members by role, customers, organization, custom statuses

That surface is enough for triage, assignment, merge cleanup, and release notes without opening the dashboard for every step. Full tool list: FeatureOS MCP integration.

How do you connect FeatureOS to Claude Code?#

Connect FeatureOS to Claude Code by adding the remote MCP URL and completing browser OAuth. FeatureOS does not require an API key or JWT in your config file. You sign in once; Claude stores a session you can revoke later.

Server URL (same everywhere):

https://mcp.featureos.app/mcp

JSON config (Claude Code / Cursor)#

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

On first use, the browser opens FeatureOS. Log into the correct workspace and approve access. No secrets go in the file.

Settings UI clients#

If your client has an MCP or connectors screen, add a new remote server, paste the same URL, then complete OAuth when the browser opens.

How do you verify the connection?#

Ask something only live data can answer:

What are the top feature requests in my FeatureOS workspace?

Real posts from your boards mean you are connected. Empty results usually mean the wrong workspace or missing board access (see troubleshooting).

What does a daily feedback workflow look like in Claude Code?#

A practical loop is triage → deep-dive → capture → assign → merge → changelog. Each step is a natural-language prompt against live FeatureOS data, so you stay in the terminal with engineering context.

1. Morning triage: what needs attention?#

Ask for a filtered slice, not the whole backlog:

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.

2. Deep-dive one request#

Get the full details of feature request 1234, then show the latest 10 comments.

Who upvoted post 1234?

You get metadata, description, votes, and thread without clicking through the board UI.

3. Capture feedback as it comes up#

Create a feature request titled "Dark mode support" on the Product board.
Description: Users want a system-preference dark theme for the admin dashboard.
Tag it as "ux" and set status to Under Review.

The win is not losing the request between a standup and the board.

4. Assign and move status#

Assign post 1234 to alex@yourcompany.com and set status to Planned.

Update post 5678: set RICE score reach=80, impact=3, confidence=80%, effort=5.

Scoring and customer language stay in one system of record.

5. Merge duplicates#

Merge posts 4231 and 4232 into post 4230.

Votes, comments, and subscribers roll into the parent. Wrong merge:

Unmerge post 4231 from its parent.

6. Close the loop with a changelog#

Create a changelog for our v2.4 release and link it to feature requests 101 and 102.

For craft, see how to write a changelog and how to write SaaS release notes. Full release workflow: manage changelog via Claude Code.

Which Claude Code prompts work best for product feedback?#

The best prompts name the board, status, time range, or post ID. Vague asks like "clean up the board" are weaker than filtered lists and single explicit writes.

Discovery

  • List public boards sorted by latest activity.
  • What custom statuses are configured in this workspace?
  • List team members with the CSM role.
  • What tags are available for feature requests on the Feedback board?

Triage

  • List all feature requests with status "Under Review" on the Mobile board.
  • Show me posts submitted by user@customer.com in the last 30 days.
  • Find posts tagged "billing" that are still open.

Action

  • Create a feature request titled "…" on the Product board with description "…".
  • Add tag "enterprise" to post 1234.
  • Create a comment on post 5678: "We're prioritizing this for next quarter."

Release and docs

  • List all published changelogs.
  • Create a changelog titled "…" linked to posts 101 and 102.
  • List published articles in the Getting Started collection.

When a request is really a support question, check the help content first and answer from what is already documented instead of logging a new post. Pair with closing the feedback loop. For docs drift after ship, see keep your knowledge base updated with Claude Code.

Why use Claude Code for feedback management?#

Claude Code is a strong home for feedback because specs, PRs, and implementation notes already live there. Pulling FeatureOS into that environment cuts tab switching, ties customer language to the PR, speeds merge/tag/assign hygiene, and keeps writes permission-safe via OAuth on your user, not a god-mode service account.

In-app AI Chat for product teams still helps inside the FeatureOS dashboard. MCP is for when you refuse to leave the coding environment.

How secure is FeatureOS access from Claude Code?#

Access is as secure as your FeatureOS role and OAuth session. Claude can only do what you can do in FeatureOS. The config holds a URL, not a long-lived API key. Revoke any time under Dashboard → Organization Settings → Advanced. Wrong workspace on sign-in is the usual empty-results failure.

Do not treat Claude as an unsupervised bulk editor. Prefer small, explicit prompts. Review merges and mass status changes before you approve them.

How do you fix common Claude Code + FeatureOS errors?#

Symptom Fix
Sign-in page never opens Set a default browser, fully quit Claude Code, reopen, reconnect.
"Unauthorized" or re-prompted Session expired or revoked. Connect again.
No results Confirm workspace and board visibility for your user.
Need to cut access Revoke under Organization Settings → Advanced.

Official detail: FeatureOS MCP integration guide.

Getting started checklist#

  1. Open your Claude Code MCP config.
  2. Add the featureos HTTP server at https://mcp.featureos.app/mcp.
  3. Complete OAuth for the correct workspace.
  4. Run: What are the top feature requests in my FeatureOS workspace?
  5. Run one write action (assign, tag, or comment) and confirm it in FeatureOS.
  6. Save a short prompt pack for triage, merge, and changelog.

Feedback management fails when it is a separate chore from building. Put the board where the work happens.

Start a FeatureOS trial if you need a workspace, then connect and run the triage prompts above.