MCP server

Connect any MCP-aware client to https://getfrostbyte.dev/mcp. Hosted, Indie-tier, no local process.

Frostbyte runs a hosted MCP (Model Context Protocol) server at https://getfrostbyte.dev/mcp. Any MCP-aware client (Claude Code, Codex, Cursor, your own tooling) connects with an Indie-or-higher bearer token and starts reading or writing project data straight away.

MCP access is included on Indie, Studio, and Enterprise. Free accounts need to upgrade before generating an agent token or calling the MCP endpoint.

Connecting

The endpoint is POST https://getfrostbyte.dev/mcp with Authorization: Bearer <your-api-token>. There's no local process to run and no port to expose; your client connects directly over HTTPS.

For Claude Code and Codex, the easiest path is the Plugin. For anything else, open Settings → AI agents, click Connect your agent, and pick Cursor or Other to get the address and a token.

Cursor reads servers from ~/.cursor/mcp.json:

{
  "mcpServers": {
    "frostbyte": {
      "url": "https://getfrostbyte.dev/mcp",
      "headers": {
        "Authorization": "Bearer <your-token>",
        "X-Frostbyte-Client": "cursor"
      }
    }
  }
}

If you're integrating from custom code, see the example below.

What the tools do

The server exposes 38 tools across the major Frostbyte concepts:

Discovery

  • list_projects: projects you have access to.
  • list_areas, list_releases, list_tasks: within a project. list_tasks defaults to active tasks and takes status, release, area, and search filters.
  • release_read_active: the current active release with progress.
  • tasks_list_blocked: tasks with an active blocker.

Reading

  • get_project, get_task, get_release, get_activity.
  • get_task_attachment: reads a file attached to a task. get_task lists attachments with their IDs. Images come back as images your agent can see, text and CSV come back as text, and PDFs and other types return a note instead. Files over the size limit return a note too.
  • dashboard_snapshot: a one-call summary of task counts, in-progress work, the active release, blocked count, and pending feedback. The intended first read for an agent session.

Writing

  • create_project, create_task, create_area, create_release.
  • update_project, update_task, update_area, update_release.
  • update_task takes null for releaseId to send a task back to the Backlog, or for areaId to clear its area. An ID from another project is rejected.
  • create_release and update_release take launchDate (ISO 8601) to backdate when a release really shipped. It only applies to a completed release, so create it as completed or set it once complete. Pass null to clear. Setting it sends no emails and publishes nothing. Completing a release without a date stamps it as launching now, and moving it out of completed clears it. list_releases shows the launch date of completed releases.
  • task_complete, task_start, task_log_decision, task_spawn_subtasks, task_add_blocker.
  • task_edit_subtask, task_delete_subtask.
  • delete_task, delete_area and delete_release need confirm: true, and your agent should only send it after you've said yes in chat. Deleting an area or release keeps its tasks: they're left without an area, or back in the Backlog.

User signals

  • signals_capture, signals_list_new, signals_get, signals_get_attachment, signals_link_task, signals_dismiss.
  • signals_get lists a signal's attachments, and signals_get_attachment reads one the same way as get_task_attachment.
  • signals_link_task links a signal to an existing task, carrying its public votes across. To turn a signal into new work, call create_task first, then link.
  • feedback_hub_get reads the public portal's settings. Enabling or reconfiguring the hub happens in the web app, not over MCP.

Sessions

  • session_end: emit a wrap-up summary.

Your client can enumerate the exact list and shape via MCP's standard tools/list request.

Turned-off modules

  • If the project owner turns off User Signals (from the project ⋯ menu), the signals tools and feedback_hub_get return an error saying so, and get_project and dashboard_snapshot note that it's off. Nothing is deleted. Turning it back on restores the tools.

GitHub sync

If the project has GitHub sync on, task changes your agent makes over MCP update the linked issue the same way the app does: new tasks open an issue, edits and status changes update it, completing closes it, and deleting a task closes it. With milestone sync enabled, creating or editing a release also creates or updates its GitHub milestone, including its name, description, target date and open or closed state.

Auth

Authentication uses a bearer token in the Authorization header. Revoking the token from settings takes effect immediately. See API tokens for generation, rotation, and revocation.

What MCP doesn't do

  • It doesn't transmit your codebase. MCP only sees Frostbyte data. See Plugin.
  • It doesn't bypass plan limits. Creating tasks via MCP counts against the same active-task cap as the UI.
  • It doesn't consume AI credits. No LLM runs on Frostbyte's side; MCP is plain database access. It still requires an Indie-or-higher plan. See AI overview.

Example client request

Most users won't write raw MCP requests; your client handles it. For reference, a tools/call looks like:

POST /mcp HTTP/1.1
Host: getfrostbyte.dev
Authorization: Bearer <your-token>
Content-Type: application/json

{
  "method": "tools/call",
  "params": { "name": "list_tasks", "arguments": { "projectId": "..." } }
}

What's next

  • Manage and revoke tokens: API tokens.
  • For the easy install path on supported clients: Plugin.
Last updated