Documentation

mcp2cli turns any MCP server into a native command-line application. Server tools become verbs, resources become nouns, prompts become workflows — no MCP protocol knowledge required at the command line.

# One binary. Any server. Real CLI commands.
work echo --message hello
work email send --to user@example.com --body "Meeting at 3"
work get file:///project/README.md
staging deploy --version 2.1.0 --background

Why mcp2cli?

Architecture at a Glance

graph TB
    subgraph "User Interface"
        CLI["CLI Input<br/>work echo --message hello"]
        JSON["--json output"]
    end

    subgraph "mcp2cli Runtime"
        DISPATCH["Dispatch Router"]
        MANIFEST["Command Manifest<br/>auto-generated from discovery"]
        BRIDGE["Bridge Engine"]
        PROFILE["Profile Overlay<br/>aliases, groups, flags"]
        CACHE["Discovery Cache<br/>offline fallback"]
        DAEMON["Daemon (optional)<br/>warm connections"]
    end

    subgraph "MCP Transport"
        HTTP["Streamable HTTP"]
        STDIO["Stdio subprocess"]
        DEMO["Demo backend"]
    end

    subgraph "MCP Server"
        SERVER["Any MCP Server<br/>tools · resources · prompts"]
    end

    CLI --> DISPATCH
    DISPATCH --> MANIFEST
    MANIFEST --> BRIDGE
    PROFILE -.-> MANIFEST
    CACHE -.-> MANIFEST
    BRIDGE --> HTTP
    BRIDGE --> STDIO
    BRIDGE --> DEMO
    BRIDGE -.-> DAEMON
    HTTP --> SERVER
    STDIO --> SERVER
    BRIDGE --> JSON

Documentation Map

Getting Started

Feature Guides

Each major feature has its own deep-dive page with examples, diagrams, and best practices.

Articles & Guides

In-depth walkthroughs for specific use cases and audiences.

Quick Links

• Install: See Getting Started
• Config example: config.example.yaml
• Source: repository root
• Tests: cargo test -p mcp2cli