---
title: Cursor
description: Install the AdCrunch MCP server in Cursor and authorize your organization.
---

:::tip

AdCrunch is a **remote MCP server** — there's nothing to install locally. You add the AdCrunch URL to an MCP file and complete an OAuth flow.

:::

## Install

1. **Add the server to your MCP file**

    Add the AdCrunch entry to one of the two MCP files. When both files name
    the same server, the project file wins.

    **Global (all projects)**

    Edit `~/.cursor/mcp.json`:

    ```json
    {
      "mcpServers": {
        "adcrunch": {
          "url": "https://mcp.adcrunch.dev/mcp"
        }
      }
    }
    ```

    **Per project**

    Create `.cursor/mcp.json` in the project root:

    ```json
    {
      "mcpServers": {
        "adcrunch": {
          "url": "https://mcp.adcrunch.dev/mcp"
        }
      }
    }
    ```

2. **Restart Cursor**

    Save the file, and restart Cursor.

3. **Authorize**

    Open **Customize → MCPs** in the sidebar. The `adcrunch` server is there.
    Sign in when Cursor asks: your browser opens the AdCrunch sign-in. Sign in
    and approve the access.

The consent screen does not ask for an organization. Cursor acts for the organization that is active in your most recent AdCrunch session. [Auth & scopes](/mcp/auth#which-organization-your-client-acts-for) explains how to choose it.

## Try it

In the chat, ask: _"List my advertisers."_ Cursor calls `list_advertisers` and reads back the result.

:::warning[Approve each change yourself]

By default, Cursor asks before it runs an MCP tool. Do not add a tool that changes your ad account, such as `meta_update_budget`, to the tools that Cursor runs without asking.

:::

If that works, go to the [Quickstart](/quickstart#ten-minutes-start-to-finish) for a first question and a first change.

## Troubleshooting

:::warning[Server shows an error / no tools]

Confirm the JSON is valid and the URL is exactly `https://mcp.adcrunch.dev/mcp`. Then turn the server off and on in **Customize → MCPs** to connect again. Cursor writes its MCP logs to the **Output** panel, under **MCP Logs**.

:::