FlyDocs
NPM · @FLYDOCS/CLI
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Available components
Last scanned (56 minutes ago)
Scores higher than 43% of npm servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 29 of 60 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 9 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1461 tokens (~132/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
- 15 Oct 26 0
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 −2
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/@flydocs/cli@1.3.23
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 60 packages
| Packages resolved | 60 |
|---|---|
| Stale | 29 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
change_context Change Context ~133
See what an issue shipped: its pull requests, linked issues and decisions, each claim citing its source.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Per-section cap: pull requests, related issues, decisions |
| mode | string | – | shipped: what the issue records. impact: blast radius (not yet) |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| target | string | yes | Issue reference, e.g. FLY-123. A module or topic string is accepted by the schema and answered with NOT_AVAILABLE until the graph lands |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
issue_acceptance_update Update Acceptance Criteria ~89
Check, uncheck, defer or annotate acceptance criteria by id. Never rewrite the description to do this. See stages/implement.md.
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | yes | – |
| ref | string | yes | Issue reference, e.g. FLY-123 |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
issue_activate Activate Issue ~121
Assign, transition and record session state in one call. Not transactional; re-running is safe. Procedure: stages/activate.md.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | yes | Provider id, or 'me' |
| comment | string | yes | Why the work is starting — the transition requires it |
| ref | string | yes | Issue reference, e.g. FLY-123 |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| status | string | – | Defaults to IMPLEMENTING |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
issue_comment Comment on Issue ~80
Post a comment — one per milestone, not per step. Templates: reference/comment-templates.md.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| ref | string | yes | Issue reference, e.g. FLY-123 |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
issue_create Create Issue ~171
Capture a new issue. Procedure: stages/capture.md.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | Provider id, or 'me' |
| description | string | – | Required unless triage is true |
| estimate | integer | – | Estimate points on the provider scale — `flydocs run workspace.get-estimate-scale` reports it. See reference/priority-estimates.md |
| milestone | string | – | – |
| priority | integer | – | 0 none, 1 urgent, 2 high, 3 medium, 4 low |
| project | string | – | – |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| title | string | yes | – |
| triage | boolean | – | – |
| type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
issue_get Get Issue ~78
Read one issue with its status, description, and acceptance criteria. Read before you write.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | – |
| ref | string | yes | Issue reference, e.g. FLY-123 |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
issue_list List Issues ~149
List issues in the current focus — active sprint, board, or your assigned work.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | – |
| all | boolean | – | Bypass the product scope cascade |
| assignee | string | – | – |
| board | string | – | Board id, or 'active' |
| focused | boolean | – | – |
| limit | integer | – | – |
| milestone | string | – | – |
| mine | boolean | – | – |
| project | string | – | – |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| sprint | string | – | Sprint id, or 'active' |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
issue_transition Transition Issue ~157
Move an issue to a canonical status. The comment is required: a short pointer, not a summary — reference/comment-templates.md, reference/status-workflow.md.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | Never optional — no status moves silently |
| force | string | – | Provider-native override for STATUS_NOT_REACHABLE |
| ref | string | yes | Issue reference, e.g. FLY-123 |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| status | string | yes | Canonical FlyDocs status: BACKLOG, READY, IMPLEMENTING, BLOCKED, REVIEW, TESTING, COMPLETE, ARCHIVED, CANCELED, DUPLICATE |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
project_update Post Project Update ~78
Post a mid-session project health update; end-of-session updates belong to session_wrap. See session.md.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| health | string | yes | – |
| project | string | – | – |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
session_start Start Session ~61
Load continuity: the active issue with AC progress, last session's summary, pending work and blockers. Procedure: session.md.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
session_wrap Wrap Session ~210
End the session: write the handoff summary and post the project update, with a `title` and `summary` for your teammates. Procedure: session.md.
| Name | Type | Req | Description |
|---|---|---|---|
| blockers | array | – | – |
| body | string | – | Filled session-wrap template; sections are enforced |
| health | string | – | Omit to wrap without posting a project update |
| issues | array | – | – |
| notes | string | – | Legacy spelling of `summary`; `summary` wins when both are sent |
| pending | array | – | – |
| project | string | – | – |
| repo | string | – | Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root. |
| summary | string | – | 2-3 plain sentences for a teammate: what changed and what it means. Prose, not a log |
| title | string | – | One line for a teammate: what this session did. E.g. "Landed the Activity week view over live data" |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
How do I install the FlyDocs MCP server?
FlyDocs runs locally as an npm package, launched with npx -y @flydocs/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @flydocs/cli
claude mcp add ai-flydocs-flydocs -- npx -y @flydocs/cli
What is the FlyDocs MCP server?
FlyDocs is an MCP server listed in the public MCP registry as ai.flydocs/flydocs. Spec-driven development workflow: your agent works issues, sessions and the status lifecycle. This page covers its npm package (@flydocs/cli).
Is the FlyDocs MCP server safe to use?
FlyDocs scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FlyDocs MCP server expose?
FlyDocs exposes 11 tools: issue_get, issue_list, issue_create, issue_activate, issue_transition, and 6 more. Their descriptions and schemas cost roughly 1,327 tokens of context every time the server is loaded.
Is the FlyDocs MCP server still maintained?
FlyDocs is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.