Read posts, comments, reactions, feature requests, votes and NPS responses in Beamer. For product teams that share updates and collect feedback with Beamer. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"beamer": {
"url": "https://beamer.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"beamer": {
"type": "http",
"url": "https://beamer.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Read a post with its reactions and comments.
beamer_get_post beamer_list_post_reactions beamer_list_post_comments
List the feature requests, open one and read its comments and votes.
beamer_list_feature_requests beamer_get_feature_request beamer_list_feature_request_comments beamer_list_feature_request_votes
List the NPS responses and count them for a period.
beamer_list_nps_responses beamer_count_nps_responses
Count posts, comments and unread posts to see how active users are.
beamer_count_posts beamer_count_post_comments beamer_get_unread_count
The login page asks for your Beamer API key.
Create it in Beamer under Settings → API. A read-only key is enough. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone. Your plan sets a monthly API request limit.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Beamer API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Beamer connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
beamer_list_posts | read | List posts List changelog posts (announcements) with their translations, category, publish date, and stats (views, unique views, clicks, feedbacks, reactions). Does not record views. Beamer API: GET /posts. |
beamer_count_posts | read | Count posts Count changelog posts that match the filters. Beamer API: GET /posts/count. |
beamer_get_post | read | Get post Get one changelog post by id: translations, category, dates, audience filter, and stats. Does not record a view. Beamer API: GET /posts/{postId}. |
beamer_list_post_comments | read | List post comments List the comments that users left on one changelog post, with the author and text. Beamer API: GET /posts/{postId}/comments. |
beamer_count_post_comments | read | Count post comments Count the comments on one changelog post. Beamer API: GET /posts/{postId}/comments/count. |
beamer_list_post_reactions | read | List post reactions List the reactions (positive, neutral, negative) that users gave one changelog post. Beamer API: GET /posts/{postId}/reactions. |
beamer_count_post_reactions | read | Count post reactions Count the reactions on one changelog post. Beamer API: GET /posts/{postId}/reactions/count. |
beamer_list_feature_requests | read | List feature requests List feature requests (ideas) from the Beamer Feedback board with status, category, vote and comment counts, and the author. Beamer API: GET /requests (beta). |
beamer_count_feature_requests | read | Count feature requests Count feature requests that match the filters. Beamer API: GET /requests/count. |
beamer_get_feature_request | read | Get feature request Get one feature request by id. Beamer API: GET /requests/{featureRequestId}. |
beamer_list_feature_request_comments | read | List feature request comments List the comments on one feature request, with the author and whether a team member wrote it. Beamer API: GET /requests/{featureRequestId}/comments. |
beamer_list_feature_request_votes | read | List feature request votes List the votes on one feature request, with the user who voted and the date. Beamer API: GET /requests/{featureRequestId}/votes. |
beamer_list_nps_responses | read | List NPS responses List Net Promoter Score responses with score (0-10), written feedback, user, and date. Beamer API: GET /nps. |
beamer_count_nps_responses | read | Count NPS responses Count NPS responses that match the filters. Beamer API: GET /nps/count. |
beamer_list_users | read | List users List the end users that Beamer tracked in Analytics (first seen, last seen, language, custom attributes). Beamer API: GET /users. |
beamer_get_unread_count | read | Get unread post count Get how many changelog posts are unread in the feed, plus the feed URL and the popup URL. Beamer API: GET /unread/count. |
beamer_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
beamer_request_feature | Request a missing feature Tell usefulapi that the user needs something the Beamer tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
beamer_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Beamer (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
beamer_cancel_subscription | Cancel the Pro subscription Cancel the caller's Beamer Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run beamer_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Beamer server only. Subscribe with beamer_upgrade (it returns a Stripe Checkout link). Cancel any time with beamer_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running beamer_upgrade before then undoes the cancel. Or write to [email protected].
See how an announcement landed. Review feature requests. Read the NPS responses. Count activity. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Beamer. The server calls the Beamer API with your own Beamer access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Beamer API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Beamer API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Beamer API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Beamer.
All 16 Beamer tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Beamer server only. Cancel any time: Pro then runs to the end of the paid period. Run beamer_usage_status to see how many calls you used.
Ask the AI to run beamer_upgrade: it returns a Stripe Checkout link. To cancel, run beamer_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with beamer_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.