Tools Reference

The remote server lists 31 tools. 17 only read. 14 write to your tracker. This page is generated from the server's tool manifest, so the names, titles and descriptions below are the ones your client sees (server flydocs, version 0.4.0).

• Start here
• Find what to name
• Read and work issues
• Milestones and projects
• Context and what shipped
• Delivery analytics

On every call

Every tool that works on a workspace takes two optional arguments, organization and workspace. The agent copies them from flydocs_whoami and passes them on every call. Leave them out and the call runs in your primary organization, and in your only workspace if you have one. If the choice is ambiguous the call is refused with the list to pick from. See Organizations and workspaces.

Reads, writes and confirmation

Every tool declares whether it reads or writes. 2 of the writes are also marked as able to cancel or archive an issue, because a status move can end an issue's life. A client can use those marks to ask you first.

Every write goes through the FlyDocs relay and is checked against the lifecycle. When the relay refuses, the answer says why. See Troubleshooting.

Start here

Call flydocs_whoami once at the start of a conversation. It lists the organizations and workspaces you can reach and gives the organization and workspace values to pass on every later call.

Tool	Access	What it does
flydocs_whoami Who Am I	Reads	Call this once, before anything else. It lists the organizations this account belongs to, the workspaces reachable in each, and which organization is primary. Copy one `useAsContext` pair into the `organization` and `workspace` arguments of every later call.
flydocs_server_info FlyDocs Server Info	Reads	Diagnostic: reports the path reached, the protocol revision, and the server name of this remote MCP endpoint.

Find what to name

Read-only lookups that return ids and names side by side, so the agent never has to guess an id and you can name a milestone, project or sprint the way you say it.

Tool	Access	What it does
flydocs_workspace_reference Workspace Reference	Reads	Call before filling in the arguments of a create or an update. Returns the workspace's labels, its statuses with their canonical FlyDocs mapping, the estimate values the tracker will accept, its teams, and the names of its issue templates.
flydocs_milestone_list Milestones	Reads	Call before naming a milestone anywhere, so an id is never guessed. Returns each milestone's id, name and target date, and the project it belongs to where the tracker records one.
flydocs_project_list Projects	Reads	Call before naming a project anywhere, so an id is never guessed. Returns each project's id, name and the state the tracker reports for it.
flydocs_sprint_list Sprints	Reads	Call before naming a sprint anywhere, so an id is never guessed. Returns each sprint's id, name, number, start and end dates, and whether it is running, planned or finished. A Linear cycle and a Jira sprint are the same thing here.

Read and work issues

The everyday tracker tools. Status changes need a comment, and checkboxes change only through the acceptance tool, by criterion id.

Tool	Access	What it does
flydocs_issue_get Get Issue	Reads	Read one issue from the tracker: status, description, acceptance criteria, comments, links.
flydocs_issue_list List Issues	Reads	Call to find issues in the workspace, filtered by status, assignee, project, milestone, sprint or board. Project, milestone and sprint take a name as well as an id, and the result says which one the word resolved to.
flydocs_issue_create Create Issue	Writes	Call to capture one new issue, validated against the workspace's conventions before anything is written. Name a `sprint` when the team works a board, or the issue lands outside every sprint that board shows.
flydocs_issue_update Update Issue	Writes	Call to edit an issue's fields: title, description, priority, estimate, labels, milestone, due date, project, sprint. Status changes go through flydocs_issue_transition and assignment through flydocs_issue_assign.
flydocs_issue_comment Comment on Issue	Writes	Append a markdown comment to an issue.
flydocs_issue_transition Transition Issue	Writes, can cancel or archive	Call to move an issue to a canonical status, with the audit comment every transition requires. The relay judges legality from the current state and returns a structured reason when it refuses.
flydocs_issue_assign Assign Issue	Writes	Call to assign an issue to a workspace member, or pass null to unassign. The assignee is validated against the workspace roster first.
flydocs_issue_activate Activate Issue	Writes, can cancel or archive	Call to start work on an issue: it assigns the issue and moves it to a status, with the audit comment the transition requires, in one call. The default status is IMPLEMENTING.
flydocs_issue_link Link Issues	Writes	Call to relate two issues as `blocks`, `related`, or `duplicate`.
flydocs_issue_acceptance_update Update Acceptance Criteria	Writes	Call to tick, untick, defer or annotate an issue's acceptance criteria, by criterion id. This is the only way to change a checkbox: the criteria live in the description, and rewriting the description to move one is never correct.
flydocs_issue_breakdown Break Issue Into Sub-Issues	Writes	Call to break one issue into sub-issues, rather than a run of create calls. One atomic call creates the whole validated batch or none of it, links each child as blocking the parent, and applies the dependsOn edges. Run it with dryRun first, fix the children it names, then run it for real.

Milestones and projects

Create and edit the containers issues live in. Deleting a milestone and archiving a project are not tools here; both are admin work in the portal or your tracker.

Tool	Access	What it does
flydocs_milestone_create Create Milestone	Writes	Call to create a milestone in a project. Returns the id, which is what flydocs_issue_update takes as milestoneId.
flydocs_milestone_update Update Milestone	Writes	Call to rename a milestone, move its target date, or edit its description. Name at least one field to change. Deleting a milestone is not on this surface: it is admin work in the portal or the tracker.
flydocs_project_create Create Project	Writes	Call to create a project in the workspace's tracker. This creates the container; flydocs_project_update posts a status update to an existing one. A new project starts active, and flydocs_project_edit changes its state.
flydocs_project_edit Edit Project	Writes	Call to edit a project itself: its name, its description, or its lifecycle state. It is not flydocs_project_update, which posts a status update to a project and changes nothing about it. Archiving is admin work in the portal.
flydocs_project_update Post Project Update	Writes	Call to post a status update, health plus a markdown body, to a project. It posts an update and does not edit the project itself; renaming one or changing its state is flydocs_project_edit.

Context and what shipped

Answers built from records, each claim cited to where it was read. None of them returns source code.

Tool	Access	What it does
flydocs_project_context Project Context	Reads	Call before drafting anything that describes the product or how the system fits together. Returns each repository's project.md and service descriptor in the team's own words, as the team last pushed them. Pass `repo` to narrow to one repository.
flydocs_what_shipped What Shipped	Reads	Call before describing what a team built, with an issue reference. Returns the issue's pull requests as GitHub records them, the related issues, and the decisions in its comments, each claim cited to where it was read. A pull request that cannot be reached is a gap, never a guess.
flydocs_release_digest Release Digest	Reads	Call before writing anything that says what a team released. Give it exactly one scope: a milestone, a project, a sprint, or a list of issue references. It returns the record and not the announcement, as one provenanced slice per done issue plus counts derived from those claims.
flydocs_week_digest Week Digest	Reads	Call for what a week came to, aggregated from the sessions the team recorded. The figures are exact as of `asOf`; `summary` can lag, so check `summary.source` (`model` or `template`) and `summary.generatedAt`. It does NOT report cost, tokens, or per-person productivity.
flydocs_session_updates Session Updates	Reads	Call to read the session records themselves, newest first, as written by the team at the end of each session; nothing here lags. `flydocs_week_digest` aggregates these same records and its claims point back to them. It does NOT report cost, tokens, or per-person efficiency.

Delivery analytics

What a window of work produced, what it cost, and what the next plan is likely to take. Aggregates only, with no per-person figure, and every answer carries a coverage note. These need the Team plan.

Tool	Access	What it does
flydocs_kpi_summary KPI Summary	Reads	Call to answer what shipped in a window and what it cost. Delivery-scoped: the set is the issues FlyDocs watched reach a finalized close in the window. Aggregates only, with no per-person figure, and every answer carries a coverage block; repeat it rather than presenting a total as complete.
flydocs_spend_breakdown Spend Breakdown	Reads	Call to answer where the spend went in a window, grouped by workflow_stage, repo, project, model, tool. Rows are ordered by cost and the total is the sum of the rows on screen. Aggregates only, and every answer carries the coverage block.
flydocs_forecast Forecast Inputs (beta)	Reads	Beta: call for the observed calibration facts a plan is built from, not a prediction. Returns tokens and cost per estimate point, their spread, completed points per week, the model mix and per-project history, with its own confidence. Read the figures out as history.
flydocs_estimate_plan Estimate Plan (beta)	Reads	Beta: call to size a plan before committing to it. Give exactly one of `children` or `ref`. Returns story points, calendar weeks at the team's pace, agent spend as a P10 to P90 range, precedents, and caveats to read out beside the numbers. Sizing an issue's sub-issues is not available yet.

Where this list comes from

The server publishes the same list, unauthenticated, at https://mcp.flydocs.ai/mcp/tools.json. It is built from the same code that answers tools/list, so it cannot list a tool the server does not offer. This page is built from a stored copy of that manifest.