# Use Cursor with Gaitro

> Connect Cursor's agent to Gaitro with a few lines of MCP settings. It gets typed tools through the gaitro MCP server and works in drafts that a person ships.

Source: https://gaitro.com/integrations/cursor

Cursor runs on your machine, on your own Cursor account. Gaitro doesn't run it or pay for it. It gives Cursor's agent a place to work: drafts, code reserved as it's edited, checks, and a person who decides what ships.

## 1. Install the CLI and log in

```sh
npm i -g --allow-remote=root https://app.gaitro.com/cli.tgz   # puts `gaitro` on your PATH
gaitro login                                  # approve in your browser; --device on a server
```

The login is named after the machine and can be revoked under the company's Settings › Agents. [Get started](/docs) shows how to check the download first.

## 2. Add the MCP server

Add the server to `~/.cursor/mcp.json` for every project, or to `.cursor/mcp.json` in one project:

```json
{
  "mcpServers": {
    "gaitro": { "command": "gaitro", "args": ["mcp"] }
  }
}
```

Check that it shows as connected in Cursor's MCP settings. One connection covers every project in the company you logged in to. Cursor's agent then has tools such as `gaitro_open_project`, `gaitro_intent`, `gaitro_sync` and `gaitro_ship`; the [MCP reference](/docs/mcp) lists them all.

Without the MCP server, Cursor's agent can still run the `gaitro` CLI in its terminal. Every command takes `--json`.

## 3. Point Cursor at the instructions

Every Gaitro project has a `GAITRO.md` that tells agents how to work there. Cursor reads its own rules in `.cursor/rules`, and can read an `AGENTS.md` in the project's root. If the project already had an `AGENTS.md` when it came to Gaitro, Gaitro added a line to it pointing at `GAITRO.md`. If not, add this line to an `AGENTS.md` or a project rule:

```md
This repo uses Gaitro. Read and follow GAITRO.md before making any change.
```

## 4. Ask for something

Open the project's working copy in Cursor (`gaitro open <company>/<project>` prints its folder), and ask the agent for a change in plain words. It opens a draft with `gaitro_intent` (or `gaitro start`), edits, and saves checkpoints. What it edits is reserved for its draft as it saves. When you're happy with what changed, tell it to ship, or press **Ship it** on the draft.

## Good to know

- An agent on a machine with no browser, such as a cloud machine, can log in with `gaitro login --device`, or with a token made in Settings › Agents: `gaitro login --token`.
- Run several agents at once with a working copy each: `gaitro clone <company>/<project> <folder>`. If two edit the same function, the second's draft waits its turn.
- Gaitro records which agent saved each checkpoint. It recognizes Cursor from its environment; set `GAITRO_AGENT` to name it yourself.
- Claude Code and Codex connect the same way: [Claude Code](/integrations/claude-code), [Codex](/integrations/codex).