Frostbyte

npx add-mcp 'https://getfrostbyte.dev/mcp'

Browse documentation

Home

Start

• What is Frostbyte?
• Quickstart
• Connect your agent

Setup guides

• Solo developers
• Small teams
• Startups & scaling teams
• Agencies & freelancers
• Game developers

Planning

• Projects
• Dashboard
• Product
• Tasks
• Views & filters
• Areas
• Releases
• Release notes & changelog

Signals & feedback

• Signals
• Turn a signal into a task
• Feedback Portal
• Widget
• Custom domain
• Public roadmap

AI & agents

• AI overview
• Frostbyte Agent
• Working with your agent
• Auto-tracking
• MCP reference

Team & account

• Team & invites
• Plans & limits
• Billing & credits

Integrations & data

• GitHub
• Import & export

Reference

• FAQ

Docs / AI & agents / MCP reference

MCP reference

Connect any MCP client by hand, manage tokens, and look up every tool.

Copy page

Copy pageCopy page as Markdown for LLMs View as Markdown ↗View this page as plain text

Frostbyte runs a hosted MCP server that any agent can connect to. The plugin and the in-app setup steps use it too; this page is for connecting by hand, managing access, and looking up a tool. Most people should start with Connect your agent.

Server

Setting

Value

Server URL

https://getfrostbyte.dev/mcp

Transport

Streamable HTTP. Nothing to install locally

Authentication

OAuth sign-in (Claude chat, ChatGPT, Codex) or Authorization: Bearer <token>

Requires

A verified email, on any plan

Your client can list every tool and its arguments with the standard tools/list request.

Every connection also gets a few short instructions, so apps without the plugin follow the same core rules: look things up before changing them, set the real releaseId or areaId for a named release or area, keep a release's description current as its tasks change, delete only after the user says yes, stop at a plan limit instead of retrying, and treat whats_next as suggestions only.

Claude chat and ChatGPT

These apps sign in to Frostbyte, so there's no token to copy.

1. In Claude, open Settings → Connectors and add a custom connector. In ChatGPT, open Plugins, choose +, then Add custom MCP server, and pick OAuth authentication. Custom servers depend on your ChatGPT plan and workspace settings.
2. Name it Frostbyte and enter https://getfrostbyte.dev/mcp.
3. Connect, sign in to Frostbyte, and approve access.

The connection appears in Settings → Connections with the app's name. Claude chat covers the web, desktop and mobile apps.

Sign-in uses OAuth with PKCE (S256). Access lasts an hour and refreshes itself while in use; after 60 days unused, reconnect from the app. Only Claude's, ChatGPT's and Codex's own sign-in addresses are accepted, so other apps use a token. Codex signs in through the plugin.

Cursor

Add Frostbyte to ~/.cursor/mcp.json, creating the file if it isn't there:

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

Then check Frostbyte is switched on in Cursor's settings. X-Frostbyte-Client names the app in Frostbyte's activity; any short name works for another client.

Other clients

Add a remote MCP server with the URL above, and send your token in the Authorization header as Bearer <your-token>. For Claude Code, Claude Desktop's Code tab and Codex, use the plugin instead: it connects to the same server and adds guidance on when to use it.

To give Codex the tools by token, with your token in FROSTBYTE_API_TOKEN. With the plugin installed, this replaces its sign-in and keeps its guidance:

codex mcp add frostbyte --url https://getfrostbyte.dev/mcp --bearer-token-env-var FROSTBYTE_API_TOKEN

API tokens

Tokens are how Claude Code, Cursor and other clients sign in, and Codex when you'd rather not sign in through the browser. Create one from Settings → Connections → Connect your agent: pick your app (Another tool for Codex) and the token is created and filled into its steps.

• It's shown once. Frostbyte stores only a fingerprint of it. If you lose it, connect again and revoke the old one.
• Use one per app. Each shows as its own row, so you can see which app is active and revoke one without the others.
• It reaches every project you can open. A repository's .frostbyte.json picks where the agent starts; it doesn't narrow the token. See Auto-tracking.
• It lasts until you revoke it. Treat it like a password: never commit it or share it.

Check and manage connections

Each row in Settings → Connections shows the app, when it was added, and its status:

Status

Means

Ready for setup

A token exists, but no request has used it yet

Authorised

Claude, ChatGPT or Codex signed in, but hasn't made a request yet

Authenticated

Frostbyte has received a request, with the time of the last one

Expired

An OAuth connection went 60 days unused. Reconnect in the app

Revoked

It no longer works

Use the row's ⋯ menu to Rename it (Add label if it has none) or Revoke it. Revoking takes effect on the next request. To rotate a token, connect again, check the new one works, then revoke the old row.

Tools

Every tool acts as the signed-in user, on projects they can open. Each one is marked as read-only or not, and whether it can delete, so apps that ask before changes can tell them apart.

Group

Tools

Projects

list_projects · get_project · create_project · update_project (name, pitch, product brief, stage and Current Focus; owner only)

Session context

dashboard_snapshot (one-call overview) · release_read_active · whats_next · whats_next_dismiss · whats_next_restore · tasks_list_blocked · get_activity

Tasks

list_tasks · get_task · get_task_attachment · create_task · update_task · delete_task · task_link_github

Work log

task_start · task_spawn_subtasks · task_edit_subtask · task_delete_subtask · task_log_decision · task_add_blocker · task_complete · session_end

Releases

list_releases · get_release · create_release · update_release · delete_release

Areas

list_areas · create_area · update_area · delete_area

Signals

signals_list · signals_get · signals_get_attachment · signals_capture · signals_update · signals_link_task · signals_unlink_task · signals_mark_reviewed · signals_dismiss · signals_delete · feedback_hub_get

For what these do in plain terms, see Working with your agent.

Rules worth knowing

• Task numbers. Any taskId also takes the task's number within that project: FB-7, #7 or 7.
• Backlog and no area. Set releaseId: null to move a task to the Backlog, or areaId: null to clear its area. A task created without releaseId joins the active release.
• Assignees. assignedTo is a list of project member IDs and replaces the current list; [] clears it. get_project returns your own member ID, for "assign it to me".
• Open subtasks. Marking a task Done with unchecked subtasks needs completionPolicy: complete-subtasks or override.
• Deletes. delete_task, delete_area, delete_release and signals_delete need confirm: true. Deleting an area or release keeps its tasks.
• Errors. A failed call, such as a missing task, an invalid value or a plan limit, comes back with isError: true, so your client can tell it from a result.
• Completing a release. update_release with status: "completed" stamps today's launch date unless you pass launchDate, and can email the people who asked for its work. Setting launchDate on its own sends nothing. See Releases.
• New release names. Leave out name in create_release to follow the project's pattern, such as 1.2.0 → 1.2.1.
• What's next. whats_next returns your Current Focus, up to five tasks with a reason for each, up to three new signals and one release suggestion. It never changes anything; whats_next_dismiss and whats_next_restore only change your own recommendations. task_start also returns your Current Focus.
• Signals. signals_list shows new signals unless you pass status (saved, reviewed, dismissed or all). Portal signals keep their wording and reporter: signals_update can only change their type, area and portal visibility.
• Attachments. get_task_attachment and signals_get_attachment return images, and text or CSV (cut to the first 100 KB). Other files return a note instead.
• User Signals off. Signal tools and feedback_hub_get explain that the module is off. Turn it back on in the web app.
• GitHub. Changes made over MCP follow the project's GitHub sync settings, the same as changes in the app. get_task lists the task's linked pull requests, issues and latest commits, and task_link_github links a pull request, issue or commit from the connected repository by URL.

Things to note

• No Frostbyte AI credits. MCP requests are free. The AI runs on your plan with the app you connected. See AI overview.
• Plan limits still apply. A project follows its owner's plan, so a Free project's task limit counts even when a teammate's agent adds the task. See Plans & limits.
• Changes are labelled with the app's name in the project's activity. Reading doesn't add activity.

Related

• Connect your agent: guided setup for every app.
• Working with your agent: the tools in plain terms.
• Auto-tracking: link a repository to a project.

Was this page helpful?

Yes No

What were you trying to do, or what was missing? Email, if you'd like a reply (optional) Send feedback

Previous Auto-tracking Next Team & invites

Last updated November 5th, 2026

On this page

• Server
• Claude chat and ChatGPT
• Cursor
• Other clients
• API tokens
• Check and manage connections
• Tools
• Rules worth knowing
• Things to note
• Related