Skip to main content
Glama
Flightdeck MCP Server

Flightdeck MCP Server

by CruGlobal

Flightdeck MCP Server

A Model Context Protocol server that gives AI clients (Claude Code/Desktop, Cursor, …) first-class access to a Flightdeck instance — listing and creating projects, work items, cycles, modules and comments.

It's a thin client over Flightdeck's public REST API (/api/v1): it speaks MCP over stdio to the AI client and HTTPS to your Flightdeck install, using a personal access token. It never touches the app internals — the public API is its entire surface.

Prerequisites

  • Node.js ≥ 18

  • A Flightdeck install with the public API enabled (FD-21+)

  • A personal access token: in Flightdeck, go to Settings → API tokens, create one, and copy the fd_pat_… value (shown only once). The token is scoped to a single workspace and acts as you.

Related MCP server: TestRail MCP Server

Configuration

Two environment variables:

Variable

Required

Example

FLIGHTDECK_BASE_URL

yes

https://flightdeck.example.com

FLIGHTDECK_API_TOKEN

yes

fd_pat_xxxxxxxx…

Use with Claude Code

claude mcp add flightdeck \
  --env FLIGHTDECK_BASE_URL=https://flightdeck.example.com \
  --env FLIGHTDECK_API_TOKEN=fd_pat_xxxxxxxx \
  -- npx -y @cruglobal/flightdeck-mcp-server

Use with Claude Desktop / Cursor

Add to your MCP config (claude_desktop_config.json or .cursor/mcp.json):

{
  "mcpServers": {
    "flightdeck": {
      "command": "npx",
      "args": ["-y", "@cruglobal/flightdeck-mcp-server"],
      "env": {
        "FLIGHTDECK_BASE_URL": "https://flightdeck.example.com",
        "FLIGHTDECK_API_TOKEN": "fd_pat_xxxxxxxx"
      }
    }
  }
}

Tools

Tool

Description

get_me

Who/what the token maps to (user, workspace, token). Health check.

list_projects

List projects in the workspace.

get_project

Retrieve a project by id.

list_work_items

List a project's work items (summary shape).

get_work_item

Retrieve a work item by id (full shape).

create_work_item

Create a work item in a project (title required).

update_work_item

Update a work item; only supplied fields change.

delete_work_item

Delete a work item by id.

list_cycles

List a project's cycles.

get_cycle

Retrieve a cycle by id.

list_modules

List a project's modules.

get_module

Retrieve a module by id.

list_comments

List a work item's comments.

create_comment

Add a comment to a work item.

List tools accept page and per_page (max 100).

Writes are tenant-safe on the server: any referenced state, cycle, parent or label must belong to the work item's own project, and assignees must be members of the workspace — otherwise the API rejects the request.

Development

npm install
npm run build      # compile TypeScript to dist/
npm run watch      # recompile on change
FLIGHTDECK_BASE_URL=… FLIGHTDECK_API_TOKEN=… npm start

License

MIT

Available Tools

14 tools
create_commentCreate a commentA

Add a comment to a work item.

Inputs: work_item_id (required), body (required).

create_work_itemCreate a work itemA

Create a work item in a project. title is required; all other fields optional. Related ids (state/cycle/parent/label) must belong to the same project; assignees must be workspace members.

Inputs: project_id (required), title (required), description, priority, +9 more.

delete_work_itemDelete a work itemB

Permanently delete a work item by id.

Inputs: work_item_id (required).

get_cycleGet a cycleA

Retrieve one cycle by id (includes progress_percent).

Inputs: cycle_id (required).

get_meGet current identityA

Return the user, workspace and token behind the configured Flightdeck API token. Useful as a connectivity/health check.

Inputs: no named parameters.

get_moduleGet a moduleA

Retrieve one module by id (includes progress_percent).

Inputs: module_id (required).

get_projectGet a projectA

Retrieve a single project by its id.

Inputs: project_id (required).

get_work_itemGet a work itemA

Retrieve one work item by id (full shape: description + assignees, labels, parent, cycle).

Inputs: work_item_id (required).

list_commentsList commentsA

List the comments on a work item, oldest first. Paginated.

Inputs: work_item_id (required), page, per_page.

list_cyclesList cyclesA

List the cycles (sprints) of a project. Paginated.

Inputs: project_id (required), page, per_page.

list_modulesList modulesA

List the modules (feature groups) of a project. Paginated.

Inputs: project_id (required), page, per_page.

list_projectsList projectsA

List the projects in the token's workspace (paginated).

Inputs: page, per_page.

list_work_itemsList work itemsA

List work items in a project (summary shape), ordered by sequence number. Paginated.

Inputs: project_id (required), page, per_page.

update_work_itemUpdate a work itemA

Update a work item by id. Only the fields you pass are changed. Pass cycle_id: null to remove it from its cycle.

Inputs: work_item_id (required), title, description, priority, +9 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: CRUD operations for different entities (work items, cycles, modules, projects, comments) are separated, with no overlapping functionality. The 'get_me' tool serves a unique health check role.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., create_work_item, list_comments, get_cycle), making it predictable and easy for an agent to understand the action and resource.

    Tool Count5/5

    With 14 tools covering core project management entities (projects, work items, cycles, modules, comments), the count is well-scoped. Each tool earns its place, and the number is manageable without being excessive or insufficient.

    Completeness4/5

    The tool surface provides full CRUD for work items and listing/getting for other entities, but lacks update and delete operations for comments, and there is no search or filtering across work items. These minor gaps do not severely hinder common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers