---
title: Connect to Cursor
slug: connect-to-cursor
docTags: 
createdAt: 2026-02-03T14:27:07.456Z
---

In this guide, learn how to connect your MCP toolbox to Cursor.

**Prerequisites**

- Cursor account 
- [MCP toolbox URL and key](docId\:JqY6i5aCFIm-kOm9ERv7A) 

To connect your MCP toolbox to Cursor:

:::::WorkflowBlock
:::WorkflowBlockItem
Open the desktop version of Cursor.
:::

:::WorkflowBlockItem
On the upper right-hand side, click the settings icon to open the **Cursor Settings **dialog.
:::

:::WorkflowBlockItem
In the left sidebar, click **Tools & Integrations** (or **Tools**, if you're on the Free Plan).
:::

:::WorkflowBlockItem
Under **MCP Tools**, click **Add Custom MCP** to open the editor for the `mcp.json` file.
:::

::::WorkflowBlockItem
In the editor, add the configuration below:

```json
{
  "mcpServers": {
    "make": {
      "url": "<MCP TOOLBOX URL>",
      "headers": {
        "Authorization": "Bearer <TOOLBOX_KEY>"
    }
  }
}
```

:::hint{type="info"}
Optionally, use an env variable when adding the toolbox key for additional security. To learn more, see [Cursor's MCP documentation](https://cursor.com/docs/context/mcp).&#x20;
:::
::::

:::WorkflowBlockItem
To complete the configuration, replace the placeholders with your actual values:

- `MCP TOOLBOX URL`: The URL generated when you created the MCP toolbox.&#x20;
- `TOOLBOX KEY`: The key generated for the MCP toolbox.&#x20;

Configuration example:

```json
{
  "mcpServers": {
    "make": {
      "url": "https://eu2.make.com/mcp/server/•••••••••••••",
      "headers": {
        "Authorization": "Bearer •••••••••••••"
    }
  }
}
```
:::
:::::

You've now connected your MCP toolbox to Cursor.

:::hint{type="warning"}
**Troubleshooting:** If an OAuth consent screen appears when you're trying to connect, your MCP toolbox URL or key is likely incorrect. For guidance, see [Configure your URL](docId\:JqY6i5aCFIm-kOm9ERv7A).
:::

:::hint{type="info"}
**MCP toolbox timeout:** Your MCP toolbox scenarios must finish running within 40 seconds. If a scenario runs longer, the connection times out and no outputs return to the client.
:::