Using the BigCommerce Docs

Your most-used tool as a BigCommerce developer is the documentation itself. The modern BigCommerce docs are built for both humans and AI assistants - learn to navigate them fast and to wire them into your editor and Claude Code.

The AI tools menu (Copy page)

Every docs page has a Copy page button with a dropdown of AI-oriented actions. These turn any doc page into something an AI assistant can use directly:

  • Copy page as Markdown - copies the page as clean Markdown, ready to paste into Claude, ChatGPT, or a prompt.
  • Ask a question - opens the docs AI assistant scoped to the content.
  • View as Markdown - shows the page as raw Markdown in the browser.
  • Open in Claude / Open in ChatGPT - sends the page into a chat with that assistant so you can ask about it.
  • Connect to Cursor / Connect to Claude Code - one-click install of the docs MCP server into your editor / CLI, so the assistant can query BigCommerce docs live.

Markdown & llms.txt shortcuts

Two mechanisms power the above, and you can use them directly:

  • Append .md to any docs URL to get clean Markdown of that page - handy for feeding a single page to an AI without copy-paste.
  • llms.txt - a machine-readable index of the docs. The developer-scoped index lists every page, and appending /llms.txt to any section URL gives that section’s index.

The docs MCP server

BigCommerce hosts an MCP server at https://docs.bigcommerce.com/_mcp/server that lets AI tools search and read the docs on demand. Wire it into Claude Code once and the assistant can pull authoritative BigCommerce docs while you work:

claude mcp add --transport http bigcommerce-docs https://docs.bigcommerce.com/_mcp/server
# add --scope user to make it available in every project

Cursor, Codex, and Claude Desktop have their own one-step setups - the AI Agent Setup page documents each. The “Connect to” options in the Copy-page menu do this for you.

Using AI responsibly

AI assistants accelerate learning but can be confidently wrong, especially on version-specific details (v2 vs v3, token deprecations, exact scopes). Treat AI output as a fast first draft, then verify against the actual doc page or the API Reference before shipping. Never paste store tokens, secrets, or customer data into an external AI tool.

Read the BigCommerce docs