DocStar

DocStar is an API documentation platform for people and AI agents. It turns your code into API docs, llms.txt, a hosted MCP server and a CLI, and keeps them in sync.

View on docstar.io

Documentation

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

API documentation for people and AI agents

DocStar is API documentation for people and AI agents. Paste one prompt into your coding agent: it documents your API from your code, and DocStar publishes the docs, llms.txt, an MCP server and a CLI, and keeps them in sync.

Copy prompt: paste this into your agent:

Use DocStar to let my users use my app from their AI assistants.
Follow https://docstar.io/mcp/quickstart.md, document my app's user-facing APIs from my latest code, and set up MCP.

See how it works

Works with: Claude Code, Cursor, Codex, VS Code, any MCP client

What the agent does:

  • you: Document my API with DocStar.
  • agent: Reading src/routes … 24 endpoints in 5 modules
  • agent: Auth: bearer token in Authorization header
  • agent: Created “Acme API” · 5 modules · 24 endpoints
  • agent: Published docs.acme.com
  • agent: MCP server live at mcp.acme.com
  • agent: CLI ready: npx docstar-cli init acme
  • agent: Watching main for changes to keep docs in sync

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

From code to every channel, in one prompt.

How it works

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

  1. Copy the prompt. Paste it into Claude Code, Cursor or Codex, opened in your API's repo.
  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.
  3. You approve, DocStar publishes. Docs, llms.txt, markdown, MCP server and CLI go live together. Your agent proposes, you publish.

Write it once. Every reader gets its format.

One source, every format

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

  • Docs site (for people): Searchable API reference and guides on your domain, with try-it, code samples and your branding. Example: docs.acme.com/messages/send
  • llms.txt + markdown (for models): Every page has a .md twin, and your site has llms.txt. Models read clean text, not HTML. Example: GET docs.acme.com/llms.txt
  • MCP server (for agents): A hosted MCP server on your own domain. Agents search your docs and call your API as tools, with OAuth sign-in. Example: claude mcp add acme https://mcp.acme.com
  • CLI (for terminals): Every endpoint becomes a command, generated from your docs and updated with them. Example: npx docstar-cli acme messages send
  • OpenAPI export (for tools): Export your docs to OpenAPI 3 for SDK generators, gateways and test tools. Example: Export to OpenAPI 3 any time

Docs that keep up with your API.

After launch

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

Every part of DocStar, in detail.

Related

Hosted MCP server

Every API you document gets an MCP server that agents use to search your docs and call your API.

How the MCP server works

docstar-cli

Every published endpoint becomes a terminal command, and the CLI runs as a local MCP server.

Generate a CLI from your docs

API docs

A public API reference with a try-it playground, guides, llms.txt and markdown for every page.

See the API docs platform

Agent analytics

See which people and agents read your docs, what they ask and what they couldn't find.

Explore agent analytics

White-label

Your domain on the docs and the MCP server, your name on the CLI, your look everywhere.

Brand every channel

For developers using APIs

Install the DocStar MCP once and your agent can find, read and call any API on DocStar.

Give any API to your agent

Using someone else's API? Hand it to your agent.

For developers using APIs

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

Copy MCP install command:

claude mcp add --transport http docstar https://mcp.docstar.io/mcp

List your API on DocStar

This page has a markdown twin.

Readable by agents

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"

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

Questions, answered.

FAQ

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, with OpenAPI 3 export, 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.

Copy prompt: paste this into your agent:

Use DocStar to let my users use my app from their AI assistants.
Follow https://docstar.io/mcp/quickstart.md, document my app's user-facing APIs from my latest code, and set up MCP.

Start free