Private previewWorkspaces are by invitation

HeedPost

01Collect

Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.

02Understand

Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.

03Ship and tell

Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.

04Run it

Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.

05Connect

Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.
AIDocsHelpPricingBlog

Collect

Understand

Ship and tell

Run it

Connect

Request an inviteSign in

Chapter 5 · Connect · MCP server

Your AI agent can run your feedback. Claude Code, Cursor, VS Code, or one you built.

HeedPost speaks the Model Context Protocol, the standard way AI assistants use other software. Connect your agent with one command, and every operation in the API becomes a tool it can call, as the person who holds the key.

Plan Plus and Pro, with an MCP key. 1,000 calls an hour per person.
> which ideas have the most votes?248  Export the roadmap to CSV196  Dark mode for the mobile app141  Slack alert for big accountsMove the top one?Ask in plain words
27 toolsone for every API operation
1 commandto connect Claude Code
1 dooran MCP key opens MCP and nothing else
As youwhat it files carries your name

Try it

Watch an agent work.

Pick a job on the left. Every call is a real tool name with real arguments.

claude codeheedpost · 27 tools
27 tools. One for every operation in the API.They are generated from the API's own schema, so every new endpoint arrives as a tool too. Point at one to read it.

list_posts Posts on this workspace's boards, with filters for board, status, kind and free text, and a sort.

Connected in a minute

1
Make an MCP keySettings · Developers, then New key, then MCP. That key opens the MCP endpoint and nothing else.
2
Paste one commandThe page hands you the whole thing with your key already in it.
3
AskBefore it calls anything, the agent is told it acts on one workspace as you, and that what it files carries your name.

        
Run it once in your project. Claude Code remembers the server.
27tools, read off the same schema as the REST API, so the two cannot drift apart
1 personper key: what the agent files carries their name, and it can do only what their role allows
1 dooran MCP key is refused on REST and a REST key is refused here, so a leaked key opens one surface
1,000calls an hour per person, one MCP message counting as one, on Plus and Pro

Step by step

How it fits into your week.

  1. Make an MCP key

    In Settings, under Developers, make a new key and choose MCP.

  2. Run one command

    Or add the server to your client's settings.

  3. Ask

    Ask in plain words, in the assistant you already use.

  4. Check what it did

    Every call is shown, and every change appears in the activity log under your name.

Who it's for

Three people, an ordinary week.

For PMs

Ask in plain words

“Which ideas under review have the most votes?” One question to the assistant you already use, a ranked answer, and an offer to move the top one.

For founders

Set up a workspace by asking

“Make a private Bugs board and invite our two support leads.” Your team's agents file, vote and triage without anyone copying links between tools.

For engineers

Ship from the terminal

After merging a release, ask Claude Code to mark the post Shipped with a note, and its followers are emailed. Its tools are the REST API's own operations, so the two never drift apart.

The details

Everything it does, explained.

What MCP is

A common language AI assistants use to work with other software. Once HeedPost is connected, your assistant can read your boards and take actions on them when you ask, the way a teammate would.

What you can ask

Questions ("which requests from this month have the most votes?") and jobs ("log this request unless we have it", "move these three to Planned", "invite our support leads"). The assistant chooses the calls and shows you what it did.

Safe by default

It acts as the person whose key it holds, so it can only do what that person may, and everything it files carries their name. An MCP key opens the MCP endpoint and nothing else. Revoke it on the page where you made it.

For developers.

The API, the events, and what you can rely on when you build on it.

Transport

There's one endpoint, POST https://api.heedpost.com/v1/mcp, using Streamable HTTP and answering in JSON. Each request stands alone: the key names the workspace and the person, so there's no session to keep. Send one message per request. A GET returns 405, and a batch gets a clear error.

Protocol versions

Supported versions are 2024-11-05, 2025-03-26, 2025-06-18, 2025-11-25 and 2026-07-28. From 2025-06-18, each result carries a sentence for people and the data for programs, and 2026-07-28 adds server/discover. The version is read from the MCP-Protocol-Version header on every request.

The same rules as the API

Each tool is one API operation with the same name, and its inputs come from the same OpenAPI document. Keys, checks, plan limits, events and rate limits work exactly as they do over REST. The tool list isn't cached, so a client always works from the current version.

Errors an assistant can fix

Asking for a tool that doesn't exist, or sending arguments it doesn't accept, is a protocol error. When a tool runs but can't do what was asked, the result explains why in a sentence, so the assistant can correct the board name or status and try again.

REST API and MCP tools

Each of these is a REST endpoint and, with the same name, an MCP tool.

  • POST/v1/posts/{post_id}/commentsadd_comment Reply on a post, as the person the key belongs to.
  • POST/v1/webhooksadd_webhook Add an endpoint. The events you choose are sent to its URL, signed with a secret.
  • POST/v1/boardscreate_board Make a board. The slug is its address, and every link to the board is built from it.
  • POST/v1/postscreate_post File a post, as the person the key belongs to.
  • DELETE/v1/boards/{slug}delete_board Deleting a board hides it and its posts. Nothing is destroyed, and you can bring it back from Settings, under Deleted.
  • PATCH/v1/boards/{slug}edit_board Change a board's name, description, visibility and switches. Its address has an endpoint of its own.
  • PUT/v1/webhooks/{endpoint_id}edit_webhook Change an endpoint's URL or the events it wants. Send the whole set each time: a field you leave out is cleared, not kept.
  • GET/v1/posts/{post_id}get_post One post in full, with its board, status, author, tags and demand.
  • POST/v1/membersinvite_member Invite someone by email. The answer is the pending invitation, without its link, which goes only to their inbox.
  • GET/v1/boardslist_boards Every board this key can see, in the workspace's own order.
  • GET/v1/posts/{post_id}/commentslist_comments Oldest first, in one flat list. A comment written while you page through is added at the end, so the pages you haven't read yet don't shift.
  • GET/v1/memberslist_members Everyone in this workspace, newest first.
  • GET/v1/postslist_posts Posts on this workspace's boards, newest first unless you choose another sort. Filter by board, status, kind or free text.
  • GET/v1/statuseslist_statuses Every current status, and the stage each belongs to. Read this first, so your client only sends ?status= names that exist.
  • GET/v1/tagslist_tags Every current tag in the workspace, in alphabetical order.
  • GET/v1/user-segmentslist_user_segments Every user segment, largest first. Team keys only.
  • GET/v1/webhookslist_webhooks Every endpoint this workspace sends events to, and how its recent deliveries went.
  • DELETE/v1/members/{user_id}remove_member Take someone off this workspace. Their posts, votes and comments stay, because those belong to them, not to their place on the team.
  • DELETE/v1/webhooks/{endpoint_id}remove_webhook Unlike everything else on this API, removing an endpoint is permanent.
  • POST/v1/webhooks/{endpoint_id}/rotaterotate_webhook Get a new signing secret. It's shown in this answer only, and the old one stops working at once.
  • PUT/v1/boards/{slug}/addressset_board_address Give a board a new address. Every address it has had keeps working, so a link someone sent last year still opens the board.
  • PATCH/v1/members/{user_id}set_member_role Make someone an admin, or make an admin a member again. The last admin can't step down, and gets a 409. Promote someone else first.
  • POST/v1/posts/{post_id}/statusset_post_status Give a post one of the workspace's statuses, by name. Only admins can do this. A move to a new stage emails everyone who follows the post.
  • DELETE/v1/posts/{post_id}/comments/{comment_id}/voteunvote_comment Take a comment vote back. It's safe to repeat. Voting on a comment doesn't follow anything, so there's nothing to unfollow.
  • DELETE/v1/posts/{post_id}/voteunvote_post Take a vote back. It's safe to repeat.
  • POST/v1/posts/{post_id}/comments/{comment_id}/votevote_comment Add a vote to a comment, as the person the key belongs to. Voting twice still counts as one vote.
  • POST/v1/posts/{post_id}/votevote_post Safe to repeat: voting twice still counts as one vote and sends one event.

Plans

What each plan includes.

Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line

FeatureFreePlusPro
MCP serverNot includedIncludedIncluded
API keys, including MCP keys0UnlimitedUnlimited
Calls
1,000 an hour per person, and each MCP message counts as one
What it can do
Only what the key's person can do, and it can't make keys

What people ask us.

Something else? Write to us, and a person answers.

Which assistants work?

Claude Code, Cursor, VS Code, and any client that speaks Streamable HTTP and can send a bearer token.

Can an agent do anything I can't?

No. It can only do what your role allows, and it can't make keys.

Does it count against my limits?

Yes. Each MCP message counts as one API call, toward 1,000 an hour per person.

Can it delete things?

It can do what your role allows, like deleting a board if you're an admin. If that worries you, use a member's key or a test workspace.

Where do I see what it changed?

In the activity log, under the name of the person whose key it used.

Start hearing everyone.

Free for your first two boards, with no card.