Featurebase MCP server

What the model can do

Featurebase feedback, support inbox and changelog: boards and statuses, feedback requests by board, status, tag or search with votes, comments and ETA, a request's comments, support conversations with their messages, the team's admins, and changelog updates; when you ask, can create, edit or delete a request, add a vote for a named person, comment or delete a comment, close, snooze, reopen, assign or tag a conversation, reply or add a note to it or leave a draft for an admin, and create and publish changelog updates.

Reads

• featurebase_list_boardsList Featurebase feedback boards and the post statuses (with their workflow stage), with ids.
• featurebase_list_postsList Featurebase feedback requests (posts): title, board, status, tags, upvotes, comment count, ETA, assignee…
• featurebase_get_postRead one Featurebase request by id with its full content (up to 4,000 characters).
• featurebase_list_commentsRead the comments on a Featurebase request or changelog update, threaded by reply_to, with author names and whether each is private.
• featurebase_list_conversationsList Featurebase support conversations: title, state (open, closed, snoozed), priority, assignee, tags and when they last moved.
• featurebase_get_conversationRead one Featurebase support conversation with its messages and notes (the most recent 100 shown, each cut at 1,500 characters)…
• featurebase_list_adminsList the Featurebase workspace's admins (teammates) with their ids and names.
• featurebase_list_changelogsList Featurebase changelog updates (release notes): title, state (live or draft), date, categories, whether subscribers were emailed, and the link.

Acts, when you ask

These change something in Featurebase. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• featurebase_create_postCreates a feedback request in Featurebase, as a finished request (no AI processing), pushed to no integration and without emailing admins.
• featurebase_update_postEdits a Featurebase request: title, content, board, status, tags (replacing them), ETA (null clears), assignee (null unassigns)…
• featurebase_delete_postPermanently deletes a Featurebase request with all its comments and votes; it cannot be undone.
• featurebase_add_voteAdds an upvote to a Featurebase request on behalf of the person named by email, external user id or Featurebase id…
• featurebase_add_commentPosts a comment on a Featurebase request or changelog update as the API key's user, or a reply to a comment.
• featurebase_delete_commentDeletes a Featurebase comment.
• featurebase_update_conversationChanges a Featurebase support conversation: closes, reopens or snoozes it (until a time), assigns or unassigns (null) an admin or team…
• featurebase_reply_to_conversationPosts in a Featurebase support conversation as the admin you name: a reply (message_type reply) is sent to the customer, outside the company…
• featurebase_draft_conversation_replyPuts a draft reply or note into the named admin's composer for a Featurebase conversation.
• featurebase_tag_conversationAttaches a workspace tag to a Featurebase support conversation, recorded as the named admin.
• featurebase_create_changelogCreates a draft changelog update in Featurebase.
• featurebase_publish_changelogPublishes a Featurebase changelog update on the public changelog now, or schedules it for a future time.

Connect it

First connect Featurebase on Dashboard → Connections, then add Memtro to your client once. The Featurebase tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Featurebase connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which Featurebase requests have the most votes?
• › What are customers saying on the dark mode request?
• › Which support conversations are open and unassigned?
• › What did we publish in the changelog last month?
• › Draft a reply to the open conversation about invoices for Sarah to review.

Questions

Is this an official Featurebase MCP server?

No. It is Memtro's MCP server with Memtro's Featurebase connector behind it: the connector reads Featurebase through its API with the credentials you connect on Dashboard → Connections, and Featurebase publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Featurebase?

Only when you ask, and only what it has been granted: create a feedback request on a board; edit a request: title, content, board, status, tags, ETA, assignee or visibility; delete a request with its comments and votes; add an upvote to a request for a named person; comment on a request or update, publicly or privately; delete a comment; close, snooze, reopen, assign or rename a support conversation; reply to a customer in a conversation, or add an internal note; leave a reply or note draft in an admin's composer; tag a conversation; create a draft changelog update; publish or schedule a changelog update, optionally emailing subscribers. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

• Help Scout MCP server
• Zendesk MCP server
• Intercom MCP server
• Freshdesk MCP server
• Front MCP server
• Zoho Desk MCP server