Connect AI tools to Flying Donut with MCP

Use the hosted Flying Donut MCP endpoint to let coding assistants securely access your projects with your API token.

What you can do with MCP

Model Context Protocol (MCP) connects AI assistants to external tools and live data. With Flying Donut's MCP server, you can ask your assistant to explore projects, review sprint and backlog cards, inspect tasks, create and update cards, move work between a backlog bucket and a sprint, manage assignments, and mark cards as blocked or unblocked without leaving your coding tool.

For example, ask it to summarize cards in your current sprint or turn a feature idea into a backlog card. Access and changes follow the permissions of your Flying Donut API token.

Connection details

Use these values in any MCP-compatible client:

Transport type: HTTP
Endpoint URL: https://mcp.flyingdonut.io/mcp
Header: Authorization: Bearer <your-flying-donut-v2-api-token>

Visual Studio Code setup

Create or update your workspace-level .vscode/mcp.json file:

{
  "inputs": [
    {
      "id": "flyingDonutToken",
      "type": "promptString",
      "description": "Flying Donut V2 API token",
      "password": true
    }
  ],
  "servers": {
    "flying-donut": {
      "type": "http",
      "url": "https://mcp.flyingdonut.io/mcp",
      "headers": {
        "Authorization": "Bearer ${input:flyingDonutToken}"
      }
    }
  }
}

See the official Visual Studio Code MCP documentation.

Google Antigravity setup

In Antigravity IDE, open the agent panel's menu, select MCP Servers, then Manage MCP Servers and View raw config. Add the following entry to the existing mcpServers object in mcp_config.json:

{
  "mcpServers": {
    "flying-donut": {
      "serverUrl": "https://mcp.flyingdonut.io/mcp",
      "headers": {
        "Authorization": "Bearer <your-flying-donut-v2-api-token>"
      }
    }
  }
}

Replace the placeholder with your Flying Donut V2 API token, save the file, and refresh the server list. Unlike Visual Studio Code, Antigravity uses serverUrl rather than url.

Visual Studio Code-style inputsand password prompts are not available in Antigravity's documented MCP configuration. For this bearer-token setup, enter your token directly in the headers; it is stored as plain text. Keep the token-bearing configuration private and out of source control.

See the official Google Antigravity MCP documentation.

Other MCP clients

Use the same endpoint and bearer header in your preferred client. Configuration file names and schema differ per tool, so follow each client's official documentation:

Tool	Setup docs
Cursor	cursor.com/docs/mcp
Cline (Visual Studio Code extension)	docs.cline.bot/mcp/mcp-overview
Claude Desktop	docs.anthropic.com/en/docs/claude-code/mcp
Devin Desktop	docs.devin.ai/desktop/cascade/mcp

Security recommendations

Prefer dedicated tokens per tool to simplify rotation and revocation
Store tokens in each client's secure input or secret store, not plain-text files
Do not commit tokens to Git repositories or share them in issue trackers
Rotate tokens immediately if you suspect they were exposed

Ship faster with MCP-powered workflows

Connect Flying Donut to your coding assistant and keep planning and execution in sync.

Browse all docs