Skip to content
FeedFast
Get started

Model Context Protocol

Your coding agent already fixed it. Let it tell your users.

FeedFast ships an MCP server, so the assistant you already code with can read feedback, publish the changelog and check uptime without leaving the editor.
Start freeRead the docs

The loop

FeedFast is the half your agent can't see

Your assistant can read your repo, write the fix and deploy it. It can't see what users asked for, or tell them it's done. That's the gap this closes.
  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.

Setup

Connect it in a minute

Use the hosted server with a URL, or run it locally through npx. Either way you only need an API key. Works with Claude Code, Claude Desktop, Cursor, Windsurf, Zed and VS Code (Copilot agent mode).

Hosted: a URL and your key

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 Desktop, Cursor, Windsurf, VS 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"
      }
    }
  }
}

Local: run it through npx

For clients without HTTP transport, and for when the key should stay on your machine. Fetched from npm on each run.

Claude Code

Add --scope project to commit it to the repo for your team.

claude mcp add feedfast --env FEEDFAST_API_KEY=ff_your_key_here -- npx -y feedfast-mcp

Claude Desktop, Cursor, Windsurf, Zed, VS Code, Gemini CLI

Same file as above.

{
  "mcpServers": {
    "feedfast": {
      "command": "npx",
      "args": [
        "-y",
        "feedfast-mcp"
      ],
      "env": {
        "FEEDFAST_API_KEY": "ff_your_key_here"
      }
    }
  }
}

Codex

TOML, in ~/.codex/config.toml.

[mcp_servers.feedfast]
command = "npx"
args = ["-y", "feedfast-mcp"]
env = { FEEDFAST_API_KEY = "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.

Tools

Twelve tools, one 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.

Trust

What an agent can reach, and 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 keys let it answer questions without changing anything.
  • Nothing publishes silently. Writing tools ask you before anything goes public.
  • Keys are hashed and can be revoked instantly from the dashboard.
  • Scoped to your account. A key reaches your projects and no one else’s.

Stop context-switching to write a changelog

Free forever for one project, with the full API and MCP server included: no trial, no card. See the docs for the exact tool schemas.

Start freeSee pricing