Skip to content
MCP server

FlyDocs

Spec-driven workflow that has your coding agent work issues and sync to Linear or Jira

Runs locallyStatus and history
Pricing
Freemium
Platforms
CLI, macOS, Windows
Runs
Locally
Version
1.3.47
Listing updated
2 days ago

About FlyDocs

FlyDocs is a freemium MCP server for developer tools. It runs locally on your machine and is started by your AI client.

FlyDocs is a workflow layer for AI coding sessions rather than an editor or tracker. Skills, hooks and slash commands carry a team's standards into every session, and some rules are described as gates the AI cannot bypass: code formats on each edit, status changes need documentation, and incomplete work cannot be marked done.

Issues, transitions and comments flow from the IDE to Linear or Jira, so leads see accurate status without developers leaving their editor. Session memory carries forward from one AI session to the next, and project context is distributed to every developer. The site names Cursor, Claude Code, Windsurf, Warp and Codex as supported tools. Usage and cost dashboards are marked as coming soon.

The free tier runs entirely on your machine with local issue tracking for one repository. Paid tiers add cloud issue tracking, cloud-managed configuration, a web dashboard and the project-management integration. Every seat includes the remote MCP endpoints, which the pricing FAQ says lets a product manager use the same workflow from Claude Desktop. The package is @flydocs/cli on npm.

Install

Run in a terminal

claude mcp add flydocs -- npx -y @flydocs/cli

Add to claude_desktop_config.json

{
  "mcpServers": {
    "flydocs": {
      "command": "npx",
      "args": [
        "-y",
        "@flydocs/cli"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "flydocs": {
      "command": "npx",
      "args": [
        "-y",
        "@flydocs/cli"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "flydocs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@flydocs/cli"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "flydocs": {
      "command": "npx",
      "args": [
        "-y",
        "@flydocs/cli"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "flydocs": {
      "command": "npx",
      "args": [
        "-y",
        "@flydocs/cli"
      ]
    }
  }
}

What it does

Enforced standards
Hooks and gates keep every AI session to team rules.
Tracker sync
Issues and comments reach Linear or Jira from the editor.
Session memory
Context carries from one AI session to the next.
Local-first free tier
Full workflow in one repository with no account.
Workflow lifecycle
Issues move from capture to close with required documentation.
Team onboarding
A new developer gets project context with one command.

Good for

  • Keep issue status in Linear current without manual updates
  • Apply one set of standards across Cursor and Claude Code users
  • Onboard a new developer to a repository quickly
  • Run several client projects with consistent ticket conventions

Pricing

Freemium, from $12 a month

Free local tier; Solo $12/mo, Team $20/user/mo, billed yearly; 7-day trial; Enterprise by contact.

Prices change. Check flydocs.ai before you buy.

FlyDocs FAQ

Is there a free plan?

Yes. A local-only plan covers one repository with no account.

What do paid plans cost?

Solo is $12 per month and Team is $20 per user per month, billed yearly, with a 7-day trial.

Which trackers does it support?

Linear and Jira.

Does the trial need a card?

Yes. Stripe Checkout requires a card, and nothing is charged before day 8.

Is FlyDocs free?

FlyDocs has a free plan, with paid plans for more usage or features. Paid plans start at $12 a month.

How do I add FlyDocs to Claude Code?

Run this command in your terminal: claude mcp add flydocs -- npx -y @flydocs/cli

What are the best alternatives to FlyDocs?

The closest alternatives to FlyDocs are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to FlyDocs

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ha MCP

    MCP server

    MCP server for managing and automating Home Assistant from AI assistants

    Runs locally
    • 8 tools
    • Open source
    • 7.9K GitHub stars
    • Productivity