> ## Documentation Index
> Fetch the complete documentation index at: https://docs.auditynow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Cursor

> Use Audity inside Cursor via MCP (auto-configured by npx @auditynow/connect) or manual setup.

## Fastest way: one command

```bash theme={null}
npx @auditynow/connect
```

This auto-configures Cursor's MCP server. Skip to [Verify it works](#verify-it-works) below.

For details on connect and other tools, see [Connect with one command](/guides/connect-cli).

## Manual setup (if you prefer)

If you want to configure Cursor manually:

### 1. Get a Personal Access Token

Go to **Settings → API Tokens** in your Audity workspace and create a token with **Read + Write** scopes. It starts with `aky_` and is shown only once.

### 2. Open Cursor's MCP settings

Cursor Settings → **MCP** → **Add Server**.

### 3. Configure the server

* **Name**: `Audity`
* **URL**: `https://app.auditynow.com/api/mcp`
* **Headers**: `Authorization: Bearer aky_<your-token>`

The full Bearer string goes in the headers field, including the `Bearer ` prefix.

### 4. Save and reload

Cursor will discover the available tools automatically. You should see `audity_list_projects`, `audity_create_intake`, `audity_enqueue_audit_analysis`, `audity_list_memories`, and 95+ more in the tool palette.

## Verify it works

In a Cursor chat, type:

```text theme={null}
@audity list my projects
```

The first time you invoke an Audity tool, Cursor may prompt for permission. Approve to enable. If Cursor returns your real projects, you're connected.

## What you get

100+ `audity_*` tools covering projects, documents, interviews, analysis, opportunities, ROI, deliverables, leads, and persistent memory (Nucleus).

Full tool list in [Connect Claude → What you get](/guides/claude#what-you-get).

## Common prompts

```text theme={null}
@audity list my projects
```

```text theme={null}
@audity start an audit for {client}, {industry}, {size}
```

```text theme={null}
@audity search nucleus for everything related to {topic}
```

```text theme={null}
@audity convert lead {id} into a project and trigger the analysis
```

## Cursor-specific tips

* **Use `@audity` to scope the tool call.** Without an explicit reference, Cursor may pick a different MCP server's tool.
* **Composer mode works great.** Multi-step workflows ("convert all leads above 70 from this week, then trigger analysis on each") run cleanly because Cursor stages the tool calls before executing.
* **Per-project tokens.** If you want different tokens for different projects (testing vs production), use Cursor's per-workspace MCP settings.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Cursor doesn't see Audity tools after configuring">
    Reload Cursor (Cmd+Shift+P → "Reload Window"). MCP servers are discovered at startup; config changes need a reload.
  </Accordion>

  <Accordion title="Every call returns 401 PAT_MALFORMED">
    Check the headers field. It should be exactly `Authorization: Bearer aky_<token>`. If you have an extra `Bearer ` (double prefix), remove one.
  </Accordion>

  <Accordion title="Every call returns 403 PAT_SCOPE_INSUFFICIENT">
    Token lacks `write` scope. Generate a new token in Settings → API Tokens with both `read` and `write` checked, then update Cursor's MCP headers.
  </Accordion>

  <Accordion title="`@audity` doesn't autocomplete">
    The MCP server isn't connected. Check Cursor Settings → MCP; Audity should show a green dot. Red means a connection error; verify the URL and headers.
  </Accordion>

  <Accordion title="429 rate limited">
    See [Authentication → Rate limits](/authentication#rate-limits). Cursor's composer can fan out calls fast; for batch operations consider serializing or adding delays.
  </Accordion>
</AccordionGroup>

## What's next

* [Run a full audit workflow →](/guides/running-an-audit)
* [Working with Nucleus →](/guides/working-with-nucleus)
* [API Quickstart (curl) →](/api-quickstart) for non-MCP integrations