How do I install FlyDocs?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does FlyDocs need an API key?

No required environment variable is listed on this record.

What transport does FlyDocs use?

FlyDocs runs locally over stdio.

FlyDocs

Q: When was FlyDocs last checked?

Last checked 2026-10-16. Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

by ai.flydocs

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

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

npx -y @flydocs/[email protected]

Provider

Claude Code

claude mcp add ai.flydocs-flydocs -- npx -y @flydocs/[email protected]

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "ai.flydocs-flydocs": {
      "command": "npx",
      "args": [
        "-y",
        "@flydocs/[email protected]"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
N
NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all

reaReverse engineer anything with agents, from app behavior down to native binaries.
rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

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