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, no daemon to manage, no port to expose. Your client connects directly to our server over HTTPS.

For most users, the easiest path is the Plugin, which handles install and token entry. If you're integrating from custom code, see the example below.

What the tools do

The server exposes 33 tools across the major Frostbyte concepts. Categorised:

Discovery

  • list_projects, projects you have access to.
  • list_areas, list_releases, list_tasks, within a project. list_tasks defaults to active (todo + in-progress) tasks and takes status, releaseId, areaId, and search filters so agents fetch only what they need.
  • 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, recent activity entries.
  • dashboard_snapshot, one-call summary (task counts, in-progress task titles, active release with progress, blocked count, 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.
  • task_complete, task_start, task_log_decision, task_spawn_subtasks, task_add_blocker.
  • task_edit_subtask (check / uncheck / set-text), task_delete_subtask.
  • delete_task.

User signals

  • signals_capture, signals_list_new, signals_get, signals_link_task, signals_dismiss.
  • signals_link_task accepts a signal and links it 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, disabling, or reconfiguring the feedback hub is done in the web app, not over MCP.

Sessions

  • session_end, emit a wrap-up summary.

The exact list and shape can be enumerated by your client via MCP's standard tools/list request.

Auth

Authentication uses a Bearer token in the Authorization header. The token is hashed (SHA-256) at rest in our DB; the plain token is shown to you once at generation time and never stored. Revoking the token from settings is immediate, no propagation delay.

See API tokens for generation, rotation, and revocation.

What MCP doesn't do

  • It doesn't transmit your codebase. MCP only sees Frostbyte data (tasks, areas, releases, projects, activity, feedback).
  • 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. MCP is plain database access, no LLM is invoked on Frostbyte's side. 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

  • Generate the token: API tokens.
  • For the easy install path on supported clients: Plugin.
Last updated