Flightdeck MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLIGHTDECK_BASE_URL | Yes | Base URL of your Flightdeck instance | |
| FLIGHTDECK_API_TOKEN | Yes | Personal access token from Flightdeck |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_meA | Return the user, workspace and token behind the configured Flightdeck API token. Useful as a connectivity/health check. |
| list_projectsA | List the projects in the token's workspace (paginated). |
| get_projectA | Retrieve a single project by its id. |
| list_work_itemsA | List work items in a project (summary shape), ordered by sequence number. Paginated. |
| get_work_itemA | Retrieve one work item by id (full shape: description + assignees, labels, parent, cycle). |
| create_work_itemA | Create a work item in a project. |
| update_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. |
| delete_work_itemB | Permanently delete a work item by id. |
| list_cyclesA | List the cycles (sprints) of a project. Paginated. |
| get_cycleA | Retrieve one cycle by id (includes progress_percent). |
| list_modulesA | List the modules (feature groups) of a project. Paginated. |
| get_moduleA | Retrieve one module by id (includes progress_percent). |
| list_commentsA | List the comments on a work item, oldest first. Paginated. |
| create_commentA | Add a comment to a work item. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
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.
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.
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.
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.