Connect with Cursor

From a Mapled project to a site that reads its content from Mapled, in one Cursor agent chat.

1. Open the site in Cursor

Open the site's repository folder in Cursor and start a new chat with the agent — it has to be able to edit files and run commands in the terminal.

2. Paste the prompt

In Mapled, open the project → Connect with AI → Copy prompt, and paste it into the chat. When the agent asks to run npx -y @mapled/cli connect --project <id> in the terminal, allow it.

3. Authorize

Your browser opens Mapled on the project. Press Authorize. The command writes mapled.json (the project id and the framework — no secrets) and prints Mapled's guide for agents, which the agent follows from here.

4. Approve the plan

The agent reads the code and proposes a plan. You get an email and Mapled shows the plan: the collections and singles with their fields, the records it will import, the files it will change. Press Approve plan.

You don't need to tell the agent you approved: it waits for the decision with npx -y @mapled/cli tool get_setup_run '{"runId":"…"}' --wait and carries on by itself. Cursor may ask you to allow each command it runs; allow the Mapled ones (npx -y @mapled/cli …) and your build.

5. Let it finish

The agent applies the plan, wires the site as Mapled tells it for your framework, builds it, runs npx -y @mapled/cli doctor, ships the change to the branch the site deploys from, writes MAPLED.md and reports back. Mapled then checks the deployed site; the result is on the run's page in Integrations.

If the site's host needs the delivery key and the agent can't set it there itself, it names the variable and the one place to paste it — the key is on the project's Integrations → Your site.

6. Publish

Open Review & publish in Mapled and press Publish now. From now on, editors change the content in Mapled and publish; the site follows.

Keep Mapled in Cursor

Every Mapled tool is available from the terminal without any setup: npx -y @mapled/cli tools lists them and npx -y @mapled/cli tool <name> calls one, through the connection connect made.

To make Mapled known to Cursor in every project, install the mapled skill:

npx skills add mapledhq/agent-kit -g

To add Mapled as an MCP server instead, use the hosted endpoint — OAuth in the browser, no token to copy. Add it to .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project):

{
  "mcpServers": {
    "mapled": {
      "url": "https://api.mapled.io/mcp"
    }
  }
}

The first time Cursor connects, it asks you to sign in and Mapled opens in the browser: pick the project and press Authorize. Every tool is listed in the @mapled/mcp README.