# GuideMark for coding agents

Let Claude Code, Cursor or any MCP client build tours and tooltips from your code, as drafts you approve.

Your coding agent already knows your app: its pages, components, ids and data attributes. Connected to GuideMark, it can turn that into onboarding: create a tour for a page you just shipped, add a tooltip to a new setting, or update steps after a redesign.

## What an agent can do

* Read the project: its domain, tours, tooltips and what the agent is allowed to do.
* Create a tour with all its steps in one call, or a beacon tooltip.
* Edit and delete drafts.
* Ask you to review a finished draft (you get an email with a link).
* Publish, but only if you allow it (see below).

## You stay in control

* **Drafts by default.** Everything an agent makes is a draft that visitors don't see, until you switch it on.
* **Publishing is opt-in, twice.** An agent can only put something live if the project allows agent publishing *and* you gave that agent publish access when connecting.
* **Live content is protected.** Without publish rights an agent can't edit or delete anything that's live.
* **One project per connection,** and you can disconnect it any time in **Settings → Agents**.

## Two ways in

|                                               | Best for                                      | How it signs in                                                                 |
| --------------------------------------------- | --------------------------------------------- | ------------------------------------------------------------------------------- |
| **MCP server** `https://guidemark.co/api/mcp` | Claude Code, Cursor, VS Code and other agents | Sign in with GuideMark in the browser, no key ([Connect](/docs/agents/connect)) |
| **REST API** `https://guidemark.co/api/v1`    | Scripts, CI, your own tools                   | An API key from Settings → Agents ([API keys](/docs/agents/api-keys))           |

Both do the same things with the same rules; see the [REST](/docs/reference/rest-api) and [MCP](/docs/reference/mcp-tools) references.