Skip to main content

MCP for Featurebase

General

I hate updating a new release note.

It’d be great, from Cursor, I just ask, “Can you add this to the next release note?”

When launch, I can just ask, “Can you publish the release note"? It’ll publish whatever draft is available.

I wish to drag and drop a screenshot to Cursor and it’ll automatically upload it in the release note when asked. “Can you use this screenshot in the next release note?”

Post type
💡 New feature
Posted by Phat Pham ·
Status: Completed15 comments

Log in to comment and vote

Comments15

  • Robi Rohumaa

    Team•

    Apr 29

    Pinned

    Hey — quick update: an official Featurebase MCP server is now live. It connects to your entire org and exposes admin actions across Posts, Changelogs, Help Center, Inbox, Users, and more — so tools like Cursor, Claude, and Copilot can read and edit your Featurebase data directly.

    You can set it up in Dashboard → Developers → MCP. Documentation: https://feedback.featurebase.app/en/help/articles/6144007-featurebase-mcp-server

    Would love to hear what you build with it.

  • Robi Rohumaa changed status to Completed
    Team•

    Jan 5

    Pinned

    Hey everyone,

    Great news! With the recent API documentation changes we’ve made, we now have the capabilities to support MCP.

    You can directly install it into your code editor like Cursor from the Copy dropdown menu on our docs page:

    Or by adding this MCP URL to any tool you might be using:
    https://docs.featurebase.app/mcp

    This lets your agent browse and navigate the Featurebase API Documentation and create/modify things on your behalf.

    • Nic Acton

      •

      Feb 8

      Has MCP support been removed? I’m not seeing the ability to Connect to Cursor or VS Code?

    • Dmitrii Beliakov

      •

      Feb 20

      https://docs.featurebase.app/mcp leads to a message

      ```json

      {"jsonrpc":"2.0","error":{"code":-32000,"message":"Not Acceptable: Client must accept text/event-stream"},"id":null}

      ```

      • Dmitrii Beliakov

        •

        Feb 26

        @Robi Rohumaa is the MCP removed? I’d be pleased to hear

        • Robi Rohumaa

          Team•

          Feb 26

          Hey!
          The MCP is not removed. We had a small issue with the documentation billing provider downgrading us to a lower plan without the MCP at some point, but that issue should’ve been resolved ~1-2 weeks ago.

          • Dmitrii Beliakov

            •

            Feb 26

            @Robi Rohumaa can you point at the documentation on MCP? Or at least the MCP endpoint? Current docs don’t say anything about the MCP.

            • Robi Rohumaa

              Team•

              Feb 26

              This comment goes over how to use it:

              https://feedback.featurebase.app/p/mcp-for-featurebase-2/comment/695bac31e5bd778ebd6ad7a5

              We have not yet documented this in the help center.

              • Danielle Murphy

                •

                Mar 11

                Hey Robi, Your initial comment says the MCP URL can be added to “any tool.” I’m trying it in Claude Code, and the server adds successfully, but authentication fails with Forbidden: Invalid idpId. Is Claude Code officially supported on this endpoint, or has only Cursor been configured/tested so far?

  • Jack Finnegan

    •

    Jul 28, 2025

    Featurebase team, please also add the ability for Featurebase information to be available for the MCP.

    The current ask flows as follows:

    1 Developer asks Cursor to write a Featurebase release note, based on recent commit

    Information flow:

    Cursor > Featurebase MCP

    A flow I’d like to see is:

    1 Developer asks Cursor to write a feature, based on a Featurebase Feedback ticket

    Information flow:

    Featurebase MCP > Cursor

    This will enable this ‘full circle’ flow:

    1 Developer asks Cursor to write a feature, based on a Featurebase Feedback ticket

    2 Developer asks Cursor to write a Featurebase release note, based on this recent commit

    Information flow:

    Featurebase MCP > Cursor > Featurebase MCP

  • Phat Pham

    •

    Jun 16, 2025

    I hate writing documentations for a new feature as well. It’s better to list bullet points on Cursor and ask, “can you write documentation for this”?

    Cursor already have the proper context in the code files so why won’t it write the best, easy-to-read documentation that even non-techies would understand?

  • coreties

    •

    Nov 5, 2025

    Also interested in this. Since the API is already there, it’s simply wrapping the API around some tools calls and hosting the MCP server somewhere, right? This would simplify creating and updating articles so much, as it would enable updating help desk articles based on pull requests. Any plans?

  • SGM Ninja01

    •

    Nov 10, 2025

    It would be great to access the knowledge base and resources through MCP. Currently, our AI Agents access Notion, and citation links direct users to Notion. However, we would love to redirect users to our Featurebase KB instead.

  • Linked to Unified knowledge management for Help Center and Fibi AI Agent