Skip to content
Read-only on Free, read & write on Pro

your agent fixed itnow let it tell your users

Connect Claude Code, Cursor or any MCP client to FeedFast. Your assistant reads what users asked for, closes the request and publishes the changelog, without you leaving the editor.

  • Works with
  • Claude Code
  • Claude Desktop
  • Cursor
  • Windsurf
  • Zed
  • VS Code
  • Codex

your agent sees the codewe show it the users

Your assistant can read the repo, write the fix and deploy it. It can’t see what users asked for, or tell them it’s done. That’s the half this adds.

one conversationfrom request to release

  1. 1

    Ask what people want

    Your agent calls list_feedback and gets the real requests back, with votes and comments, from your real users.

  2. 2

    Fix it in your editor

    This part is all yours. FeedFast never sees your code, your repo or your deploys. Your agent just knows which fix forty people voted for.

  3. 3

    Close the loop in one call

    resolve_feedback marks it Done, replies with an Owner badge and publishes the changelog entry the reply links to.

  4. 4

    Announce downtime before it happens

    schedule_maintenance puts it on your status page in blue, not red. No incidents, no false alerts, and uptime % skips the window.

  5. 5

    Check that it actually worked

    get_uptime returns status, latency and open incidents. Worth asking right after a deploy.

connect itin about a minute

Point your client at the hosted server, or run it locally through npx. Either way all it needs is an API key from Settings, Account.

Nothing to install and nothing to update: the server runs on ours. Works in Claude Code, Claude Desktop, Cursor, Windsurf and VS Code.

Claude Code

One command, then restart the session.

claude mcp add --transport http feedfast https://feedfa.st/api/mcp --header "Authorization: Bearer ff_your_key_here"

Claude DesktopCursorWindsurfVS Code

The same object everywhere: only the config file's location differs.

{
"mcpServers": {
"feedfast": {
"type": "http",
"url": "https://feedfa.st/api/mcp",
"headers": {
"Authorization": "Bearer ff_your_key_here"
}
}
}
}

The key comes from Settings → Account → API keys, and both transports take the same one. A read-only key lets an agent answer questions but never change anything. Give it a read-write key only when you want it to publish. The local form runs feedfast-mcp, fetched from npm on each run.

twelve toolsone API key

Feedback

  • list_feedback
  • get_feedback
  • update_feedback
  • resolve_feedback

Read the board with votes and comments, move requests along, and resolve them with a public reply.

Changelog

  • list_changelog
  • publish_changelog
  • update_changelog

Write markdown release notes and publish them to your page, RSS feed and widgets at once.

Maintenance

  • list_maintenance
  • schedule_maintenance
  • transition_maintenance

Announce downtime ahead of time, then start, complete or cancel it.

Uptime

  • get_uptime
  • list_projects

Status, latency and uptime per monitor, plus any open incident and its cause.

what it can reachand what it can’t

The MCP server has no database connection. It calls the same public API you could call with curl, holding your key, so an agent can never do more than that key allows.

  • Read-only keysLet it answer questions about your board and uptime without changing anything.
  • Nothing publishes silentlyWriting tools ask you first, every time something would go public.
  • Hashed, revocable keysStored hashed, and revoked from the dashboard the moment you want.
  • Scoped to your accountA key reaches your projects and nobody else's. No database behind the server.

Give your agent the other half

Reading works on every plan. Publishing, resolving and scheduling come with Pro, alongside five projects and three monitors in each. Three days free. The docs have every tool’s exact schema.