API documentation for the agent era

Your agent writes the docs. Every agent can use them.

Paste one prompt into your coding agent. DocStar turns your code into API docs, an MCP server and a CLI, and keeps them in sync.

Claude Code · Cursor · Codex · VS Code · any MCP client

agent run00:41
  1. youDocument my API with DocStar.
  2. agentReading src/routes … 24 endpoints in 5 modules
  3. agentAuth: bearer token in Authorization header
  4. agentCreated “Acme API” · 5 modules · 24 endpoints
  5. agentPublished docs.acme.com✓
  6. agentMCP server live at mcp.acme.com✓
  7. agentCLI ready: npx docstar-cli init acme✓
  8. agentWatching main for changes to keep docs in sync✓

3 channels live · no OpenAPI file needed

Works with
  • Claude Code
  • Cursor
  • Codex
  • VS Code
  • Windsurf
  • Claude Desktop
  • ChatGPT
  • any MCP client

How it works

From code to every channel, in one prompt.

No spec to write, no editor to learn. Your agent already knows your code.

  1. 1

    Copy the prompt

    Paste it into Claude Code, Cursor or Codex, opened in your API's repo.

    Use the DocStar MCP to document
    this API in DocStar.
  2. 2

    Your agent reads your code

    It finds every route with its auth, params, bodies and responses, groups them into modules, and shows you the plan before writing anything.

    found 24 endpoints in 5 modules
    ? Create “Acme API” with these
      modules? (y/n)
  3. 3

    You approve, DocStar publishes

    Docs, llms.txt, markdown, MCP server and CLI go live together. Your agent proposes, you publish.

    docs.acme.com            ✓
    mcp.acme.com             ✓
    npx docstar-cli init acme ✓

One source, every format

Write it once. Every reader gets its format.

People, models, agents, terminals and tools each read an API differently. DocStar serves all of them from the same source.

  • for people

    Docs site

    Searchable API reference and guides on your domain, with try-it, code samples and your branding.

    docs.acme.com/messages/send
  • for models

    llms.txt + markdown

    Every page has a .md twin, and your site has llms.txt and llms-full.txt. Models read clean text, not HTML.

    GET docs.acme.com/llms.txt
  • for agents

    MCP server

    A hosted MCP server on your own domain. Agents search your docs and call your API as tools, with OAuth sign-in.

    claude mcp add acme https://mcp.acme.com
  • for terminals

    CLI

    Every endpoint becomes a command, generated from your docs and updated with them.

    npx docstar-cli acme messages send
  • for tools

    OpenAPI

    A current OpenAPI file for SDK generators, gateways and test tools.

    GET docs.acme.com/openapi.json

After launch

Docs that keep up with your API.

Publishing is the easy part. DocStar keeps the docs right as the API changes and shows you how they're used.

  • Never drifts

    DocStar watches your repo. When a route, param or response changes, it flags the drift and drafts the fix for you to approve.

    • GitHub app
    • Fixes linked to the PR that caused them
    • Review before publish
  • Agents report gaps

    When an agent using your MCP server hits missing or wrong docs, it files the issue for you, with the exact question it couldn't answer.

    • Built into every MCP server
    • Grouped and de-duplicated
    • Straight to your inbox
  • See how agents use your API

    Human and agent traffic, split by channel. Top questions, failed searches, popular endpoints and the clients calling them.

    • Docs, MCP, CLI and llms.txt
    • Agent and client names
    • Missing-answer reports
  • Your brand, every channel

    Your domain on the docs and the MCP server, your name on the CLI. DocStar stays in the background.

    • Custom domains
    • Branded MCP server
    • Branded CLI

For developers using APIs

Give any API to your agent.

Install the DocStar MCP once. Your agent can find, read and call every API documented on DocStar, always at the current version.

List your API
agent run
  1. youSend an order confirmation on WhatsApp.
  2. agentdocstar › search APIs: “whatsapp send message”
  3. agentFound MSG91 WhatsApp · docs.msg91.com/whatsapp/module.json
  4. agentAdded sendOrderConfirmation() with retries✓

Readable by agents

This page has a markdown twin.

Ask for markdown and you get clean text. Every page on docstar.io, and every docs site on DocStar, works the same way. Try it on MSG91's API docs, hosted on DocStar.

curl https://docstar.io -H "Accept: text/markdown"

# Your agent writes the docs. Every agent can use them.

Paste one prompt into your coding agent…

curl https://docs.msg91.com/llms.txt

# Msg91

## How to use this API (for AI agents)

- Module index (discover modules): https://docs.msg91.com/module.json

## Modules

- [Email](https://docs.msg91.com/email/module.json)
- [OTP](https://docs.msg91.com/otp/module.json)…

FAQ

Questions, answered.

What is DocStar?

DocStar is an API documentation platform for people and AI agents. Your coding agent creates the docs from your code. DocStar publishes them as a docs site, llms.txt and markdown, a hosted MCP server, a CLI and an OpenAPI file, and keeps them in sync.

Do I need an OpenAPI file?

No. Your agent reads your routes directly. If you already have an OpenAPI or Postman file, you can import it instead.

Which agents work with DocStar?

Any agent or client that supports MCP, including Claude Code, Cursor, Codex, VS Code, Windsurf and ChatGPT.

Will my agent publish without asking?

No. Agents create drafts and propose changes. You review and publish, unless you turn on auto-publish for a project.

Can I use my own domain and brand?

Yes. The docs site, the MCP server and the CLI can all carry your domain and your name.

How do my users hand my API to their agents?

Every docs page has a Copy prompt button and one-click MCP install for Cursor, VS Code and Claude, so your users can give your API to their agent in one step.

Take the first step. Let your agent write your API docs.

One prompt. Your docs, MCP server and CLI, live.

Start free