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

DocsReference

MCP server

Ask about and work your feedback from Claude Code, Cursor or any agent that speaks MCP. Every API operation is a tool.

Plan Plus and ProTransport Streamable HTTP

One endpoint

URL
https://api.heedpost.com/v1/mcp

An AI agent can use this workspace through the Model Context Protocol, at one endpoint, with the same kind of key as the API. Every tool is one of the API's operations, generated from the same document, so there is nothing here the REST API does not have and nothing to keep in step.

Connecting

Make a key of kind MCP on Settings · API, webhooks and MCP. The page gives you the whole command. Then add the server to your client:

claude mcp add --transport http heedpost https://api.heedpost.com/v1/mcp \
  --header "Authorization: Bearer hp_live_..."

Claude Code remembers the server once it's added. Cursor reads .cursor/mcp.json for one project, or ~/.cursor/mcp.json for all of them. VS Code reads .vscode/mcp.json. Any client that speaks Streamable HTTP works the same way: POST JSON-RPC to that URL with the key as a bearer token. Each request stands alone, so there's no session to keep, and answers come back as application/json instead of a stream.

What an agent can do

Whatever the person whose key it is can do, which is the same rule the REST API follows. It files posts under their name, and it can move a status, which emails followers. Point it at a test workspace first if that matters to you, and remember that a key is revoked from the same page it was made on.

An MCP key doesn't work on the REST API, and a REST key doesn't work here. Both get a 403 that names the kind of key to make instead. That way, a key someone finds in a repository opens only one door.

Calls

1,000 an hour per person, shared with the REST API. Each MCP message counts as one.

History

Every change an agent makes is in the activity log, under the key's person.

Never

Make keys. No key, of any kind, can.

The tools

27 tools, one per API operation.

list_posts

Posts on this workspace's boards, newest first unless you choose another sort. Filter by board, status, kind or free text.

create_post

File a post, as the person the key belongs to.

get_post

One post in full, with its board, status, author, tags and demand.

set_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.

vote_post

Safe to repeat: voting twice still counts as one vote and sends one event.

unvote_post

Take a vote back. It's safe to repeat.

list_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.

add_comment

Reply on a post, as the person the key belongs to.

vote_comment

Add a vote to a comment, as the person the key belongs to. Voting twice still counts as one vote.

unvote_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.

list_boards

Every board this key can see, in the workspace's own order.

create_board

Make a board. The slug is its address, and every link to the board is built from it.

edit_board

Change a board's name, description, visibility and switches. Its address has an endpoint of its own.

delete_board

Deleting a board hides it and its posts. Nothing is destroyed, and you can bring it back from Settings, under Deleted.

set_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.

list_statuses

Every current status, and the stage each belongs to. Read this first, so your client only sends ?status= names that exist.

list_tags

Every current tag in the workspace, in alphabetical order.

list_members

Everyone in this workspace, newest first.

invite_member

Invite someone by email. The answer is the pending invitation, without its link, which goes only to their inbox.

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.

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.

list_user_segments

Every user segment, largest first. Team keys only.

list_webhooks

Every endpoint this workspace sends events to, and how its recent deliveries went.

add_webhook

Add an endpoint. The events you choose are sent to its URL, signed with a secret.

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.

remove_webhook

Unlike everything else on this API, removing an endpoint is permanent.

rotate_webhook

Get a new signing secret. It's shown in this answer only, and the old one stops working at once.