Give your AI agent the Bolder docs
Point a coding agent at the Bolder docs with llms.txt, Markdown pages and the docs skill, and connect a store to an agent through the MCP server.
Two jobs: a coding agent (Claude Code, Cursor, Codex) that builds on Bolder needs the docs as context; an assistant that runs a store needs access to the store’s data.
Docs for coding agents
Everything on this site is available in formats agents read well:
| What | Where |
|---|---|
| Index of every page | /llms.txt |
| All docs in one file | /llms-full.txt |
| Any page as Markdown | Add .md to its URL, for example /cli.md |
| A skill for these docs | /skill.md |
| API specs | /api/v2/openapi.yaml, /api/v1/openapi.yaml |
Every page also has Copy page and Open in chat actions.
For a project that builds on Bolder, add a line like this to your AGENTS.md or CLAUDE.md:
Bolder docs: https://developers.onbolder.com/llms.txt (append .md to any page URL for Markdown).Skills
Skills package instructions an agent loads when it needs them. Two sets are on the way: one for developers (themes, storefronts, integrations) and one for running a store (catalog, orders, customers). See Skills for their status.
npx skills add onbolder/skills --skill developer
npx skills add onbolder/skills --skill store-managementConnect a store to an AI assistant
Bolder runs an MCP server for stores at https://api.onbolder.com/v2/mcp. A merchant connects Claude, ChatGPT, Cursor or Gemini to it from Settings → AI agents in the admin. Each agent has its own identity, read and write permissions chosen by the merchant, and a log of every call; disabling or revoking an agent takes effect at once.
The MCP server only accepts agent tokens; to automate a store from your own code, use the REST API instead.
Next
- Skills
- Agentic checkout (UCP): let shopping agents buy from a shop.