Frostbyte
dev.getfrostbytePublished by getfrostbyte.devOfficial publisherv1.6.0Updated Nov 6, 2026
Product planning workspace for AI coding agents: tasks, releases, feedback and decisions over MCP.
Overview
Remote MCP workspace that lets an AI coding agent work with product planning data such as tasks, releases, feedback and decisions.
- What you can do
- Work with product planning items: tasks, releases, feedback and decisions, exposed to the assistant over MCP.
- No tool list is published, so the exact operations available are not documented in the supplied material.
- Access is through a hosted endpoint at getfrostbyte.dev rather than a local package.
- When to use it
- Useful when an AI coding agent should stay aligned with a product planning workspace, for example to look up tasks, releases, feedback or decisions while working on code, instead of switching to a separate planning tool.
- Requirements
- A remote MCP connection to the getfrostbyte.dev endpoint over streamable HTTP. OAuth authentication is required; the connection sends an Authorization header carrying a bearer token obtained from the service's Settings > Connections > Connect your agent page. No local runtime or environment variables are declared.
Installation
In SourceWeft
- Open Frostbyte in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.getfrostbyte%2Ffrostbyte/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"frostbyte": {
"type": "http",
"url": "https://getfrostbyte.dev/mcp"
}
}
}Tools
0Version history
4- v1.6.0LatestNov 6, 2026
- v1.5.6Nov 4, 2026
- v1.5.5Nov 3, 2026
- v1.3.0Sep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.