FlyDocs

ai.flydocsPublished by flydocs.aiv1.3.46Updated Nov 11, 2026

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

FlyDocs is a local MCP server that gives an assistant a spec-driven development workflow for working issues, sessions and their status lifecycle.

What you can do
  • Work development issues through a spec-driven workflow
  • Manage sessions in which the agent carries out that work
  • Track and advance items through a status lifecycle
  • No individual tools are documented, so the exact operations are not described in the available material.
When to use it
Worth considering if you want an assistant to take part in a spec-driven development process and move issues and sessions through defined statuses, rather than only editing code.
Requirements
Runs as a local process on the user's machine via npx from the npm package @flydocs/cli, so Node.js and network access for package retrieval are needed. Desktop only; no authentication, environment variables or headers are declared.
Before you install
The server can change issue and session state as part of its status lifecycle, so expect it to write data rather than only read it. No credentials are declared, but the available material does not describe what data is stored or sent anywhere.

Installation

In SourceWeft

  1. Open FlyDocs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

13
  1. v1.3.45Nov 7, 2026
  2. v1.3.43Nov 6, 2026
  3. v1.3.42Nov 5, 2026
  4. v1.3.40Nov 4, 2026
  5. v1.3.39Nov 3, 2026
  6. v1.3.38Nov 3, 2026
  7. v1.3.37Nov 3, 2026
  8. v1.3.34Oct 30, 2026
  9. v1.3.33Oct 30, 2026
  10. v1.3.32Oct 29, 2026
  11. v1.3.28Oct 26, 2026
  12. v1.3.23Sep 25, 2026
  13. v1.3.16Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.