AI agents, MCP & API access

Comet is built to be operated by AI agents, not just clicked through by hand. The primary way to automate Comet today is its MCP (Model Context Protocol) server.

MCP server

Comet ships an MCP server so an AI agent — Claude Code, Cursor, or a custom workflow — can operate Comet directly. Through it an agent can:

• List, get, create, update, and publish stores
• Add and remove store sections, and update the theme
• Configure product detail pages and the cart
• Look up your connected brand apps and find products

That makes bulk operations a single prompt:

"Spin up 20 creator stores from this CSV, themed to each creator's palette, and publish them."

Getting set up

Agent and programmatic access is rolling out and is geared toward the Developer role on your team. If you want to drive Comet from an agent or your own tooling, contact us and we'll get you connected with the right credentials for your setup.

Developer & API reference

For the full API surface — authentication, catalog, checkout, pagination, and platform integration guides — see Comet's developer docs. This help center covers the operator-facing basics; the developer docs are the source of truth for building against the API.

Good to know

• Agent access today runs through the MCP server; self-serve API-key management in the dashboard isn't shipped yet, so contact us to get keys provisioned.
• Customer-facing webhooks aren't available yet — if your integration needs events, tell us about your use case so we can prioritise it.