docchat-mcp 0.3.1

Turn your API docs into an intelligent MCP server with deterministic routing and layered knowledge injection.

DocChat MCP

Turn your API docs into an intelligent MCP server with deterministic routing and layered knowledge injection.

English | 中文

DocChat transforms your API documentation into a smart MCP server. Claude Code can query your API docs through natural language — with ~80% of queries resolved via deterministic routing (zero LLM cost).

Note: DocChat is currently optimized for Claude Code. Support for other AI coding tools is planned.

Use Case

You're building an app that calls a third-party API. You want Claude Code to understand that API — parameters, response fields, error codes, best practices — so it can write correct integration code.

Your API docs → DocChat → MCP server (runs locally) → Claude Code queries it while coding

DocChat is the bridge: it turns your docs into structured knowledge that AI assistants can search and retrieve on demand.

How It Works

                          Your machine
┌───────────────────────────────────────────────────┐
│                                                   │
│  Claude Code ◄── stdio ──► docchat mcp            │
│    (LLM)                    (local process)       │
│      │                         │                  │
│      │ "How do I call          │ reads from       │
│      │  the users API?"        ▼                  │
│      │                    ./my-api-docs/           │
│      │                    ├── META.yaml            │
│      │                    ├── GUIDE.md             │
│      ▼                    └── ...                  │
│  Generates answer                                 │
│  using retrieved docs                             │
│                                                   │
└───────────────────────────────────────────────────┘

The engine handles routing + knowledge retrieval. The AI client handles reasoning. No external services, no extra LLM calls.

Quick Start

1. Install

pip install docchat-mcp

2. Create your knowledge pack

Option A: Import from OpenAPI spec (recommended)

docchat import your-api-spec.json

This parses your OpenAPI spec (JSON/YAML, v2.0/3.x) and generates feed skeletons + an AUTHORING.md guide. Then let your AI assistant fill in the details:

# In Claude Code (skill is auto-installed as /docchat-author)
> Help me improve the docs based on the spec

# In other AI tools
> Read AUTHORING.md and help me improve the docs

Option B: Let AI do everything

If you have a documentation URL or just a description of your API, skip import entirely — just tell your AI assistant:

> I need a docchat knowledge pack for the Petstore API.
  Docs: https://petstore.swagger.io
  Read AUTHORING.md for the format.

Option C: Start from scratch (manual)

docchat init --name my-api

Then create each feed directory manually. See docs/writing-guide.md for the format.

3. Validate and build

docchat validate    # Check format
docchat build       # Verify index loads correctly

4. Connect to Claude Code

# In your knowledge pack directory:
docchat connect

# Or from another directory:
docchat connect --dir /path/to/my-api-docs/

That's it. Now when you ask Claude Code about your API, it queries DocChat's MCP server locally, retrieves the relevant docs, and generates accurate answers.

Manual registration (without docchat connect)

claude mcp add my-api -- docchat mcp --dir ./my-api-docs/

# Or via uvx (no prior install needed)
claude mcp add my-api -- uvx --from docchat-mcp docchat mcp --dir ./my-api-docs/

Team sharing (optional)

If you want multiple people to use the same knowledge pack:

# Start HTTP server on a shared machine
docchat serve --port 8710

# Team members connect remotely
claude mcp add my-api --transport http http://your-server:8710/mcp/

Features

• Deterministic routing — trigger keywords, field names, and feed codes match queries without LLM
• Layered knowledge injection — feed-level, overview, shared, and topic-matched knowledge
• AI-assisted authoring — built-in docchat-author skill guides AI to generate complete knowledge packs from any source (spec files, URLs, or descriptions)
• Custom dimensions — organize feeds by any hierarchy (product, version, region, etc.)
• MCP native — 4 tools, 3 resources, 2 prompts — works with any MCP client
• Zero LLM dependency — the engine only provides data; AI reasoning is done by the client
• OpenAPI import — docchat import spec.json generates feed skeletons from OpenAPI specs (v2.0/3.x)
• CLI tooling — init / import / build / validate / serve / mcp

Knowledge Pack Structure

my-api/
├── docchat.yaml          # Pack config (name, dimensions, assistant)
├── AUTHORING.md          # AI authoring guide (tool-agnostic)
├── .claude/skills/       # Claude Code auto-discovers this skill
│   └── docchat-author.md
├── _shared/              # Shared knowledge (error codes, auth, etc.)
│   ├── INDEX.yaml        # Topic keywords for matching
│   └── error_codes.md
├── _overview/            # API overview
│   └── INDEX.md
└── feeds/                # One directory per API endpoint
    ├── get-users/
    │   ├── META.yaml     # Triggers, fields, description
    │   ├── GUIDE.md      # Usage guide
    │   ├── FAQ.md        # Optional: troubleshooting
    │   └── fields/       # Optional: field reference
    └── get-posts/
        ├── META.yaml
        └── GUIDE.md

See docs/knowledge-pack-format.md for the full specification.

Custom Dimensions

Organize feeds by any hierarchy via docchat.yaml:

# Simple API (all feeds flat)
dimensions: []

# Two dimensions (product x sport)
dimensions:
  - key: product
    values: { rest: "REST API", ws: "WebSocket" }
  - key: sport
    values: { soccer: "Soccer", basketball: "Basketball" }

MCP Tools

Tool	Description
list_feeds	List all available feeds
search_by_field	Find feeds by field name
get_feed_info	Get feed details + documentation
route_question	Route a query and return matched feeds + knowledge

Updating

Knowledge files changed (META.yaml, GUIDE.md, etc.): Restart Claude Code. The MCP server reloads on startup.

Engine updated (new docchat-mcp version):

pip install --upgrade docchat-mcp
# Then restart Claude Code

# If using uvx, clear cache first:
uv cache clean docchat-mcp

Why Not RAG?

Approach	Limitation	DocChat
Swagger UI	Browse only, no Q&A	Natural language queries
ChatGPT + docs	Full context dump, token overflow	Layered injection
RAG (embeddings)	Embedding quality varies, routing opaque	Deterministic routing (~80% zero LLM)
No MCP	AI can't access docs	MCP native, Claude Code direct

Demo

See it in action at docchat.site

License

MIT