Click Create token and give it a name you will recognise later, such as Claude Desktop or VS Code.

Copy it immediately. It is shown once and never again.

The list shows when each token was created and when it was last used, so you can spot ones nobody uses.

Revoke takes access away straight away — the connected AI tool stops working the moment you do.

Read tools — look up data in this account. They never change anything.

Write tools — create and change records. They act on live entities straight away, without a preview step.

AI content tools — hand a piece of work to Cora, who then edits the content herself and spends AI credits.

Guided workflows — multi-step recipes your AI tool can start on request. They only sequence the tools above and can do nothing those tools cannot.

Reference data — read-only background about your account that a client can attach once instead of fetching it again every turn.

Read person — one person record by ID, with tags, addresses and a donation summary.

List people — optionally narrowed by a search term or a target audience.

List content — landing pages, campaign mails, automated mails and pages.

List target audiences — the non-archived ones, with their people count.

List workflows — with their state and whether they have a published graph.

List tags, List custom fields, List trigger actions — the building blocks other tools expect, with their IDs and allowed values.

Get landing page, Get campaign mail, Get automated mail, Get target audience, Get workflow — one record in full.

Search media library — the images and files this account already has.

Get hosted page contract — the authoring rules for AI-hosted pages.

Search and Fetch — one text query across everything, and one record back by ID. These exist for clients such as ChatGPT that drive a server through a search/fetch pair rather than per-type tools.

Create and update landing page, campaign mail, automated mail, target audience and workflow — the record and its settings. Content is filled in separately, usually by Cora.

Set trigger action — bind an automated mail to the event that fires it.

Set workflow graph and Set workflow start condition — replace a workflow's nodes and edges and publish them as a new version, and replace the event that enrols people. See Workflows for what a graph is made of.

Add media library item — copy a file from a public URL into your media library so a page can reference it.

AI-hosted landing pages — create a page from raw HTML that CamBuildr hosts without the editor, add A/B variants to it, replace its HTML, and define a signup form on it. Useful when your AI tool wants to write the markup itself.

Instruct AI assistant — give Cora an instruction in plain language to write or rewrite the content of a landing page, mail, target audience or workflow. This is how an external tool gets real content built: it creates the shell, then asks Cora to fill it.

Build a landing page — create the page shell, then have Cora fill its content.

Build an automated mail — create the mail, bind it to a real firing event, fill its content, and only then activate it.

Build a target audience — create the group, have its rules written, then check how many people it matches.

Build a workflow automation — create the workflow, set its start condition and graph, and activate it last.

Audit this account — a read-only walkthrough of every landing page, mail and target audience, flagging what looks unfinished, unbound or inactive.

Account profile — who this connection belongs to: name, public base URL, content languages and which MCP features are in effect.

Tool catalogue — the exact names of every tool, prompt and resource your account exposes.

Trigger action catalogue — the internal events an automated mail can fire on, grouped by category.

Workflow building blocks — the node kinds, action shapes and real mail, tag and campaign IDs a workflow graph may reference.

Write tools act immediately. There is no preview and no approval step like Cora's Plan first mode. What the tool asks for is what happens.

There are no checkpoints here. Cora's Restore checkpoint is a feature of the chat inside CamBuildr, not of the MCP connection. Landing page and email history still works as usual.

Contact data is reachable. Read person and List people send real supporter records to whichever AI tool you connected. If that is not what you want, switch those two off in Enabled tools.

The AI content tools spend AI credits, because they run Cora. The read and write tools do not.

Things arrive as drafts. New landing pages are unpublished, new automated mails and workflows are inactive. Nothing goes live to your supporters without you publishing or activating it.

No MCP entry in the settings menu — MCP is not switched on for your account yet. Write to us in the chat.

Your AI tool only sees read tools — MCP write access is a separate switch. Ask us to enable it.

The AI content tools are missing or marked Unavailable — AI is not switched on. Enable it in Settings > AI first.

The browser never opens to sign in — your client probably cannot do it. Use the mcp-remote bridge, or create an access token.

VS Code does not pick the server up — check the key is servers and that "type": "http" is present. Cursor is the one client that does not need the type.

A tool your AI cannot find — check it is switched on under Enabled tools, then ask the tool to re-read the Tool catalogue.

What Cora can do — the full feature guide — everything the built-in assistant does inside CamBuildr

Setting up AI in CamBuildr — enabling AI, API keys, customer instructions, allowed domains

Using Cora, the AI assistant in CamBuildr — basics and prompt writing

Workflows: automating what happens after someone acts — what the workflow tools above build