> For the complete documentation index, see [llms.txt](https://notara-1.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara-1.gitbook.io/notara-docs/mcp/cursor.md).

# Cursor

Cursor supports MCP servers through its settings panel. Once connected, your Notara tools and context are available to Cursor's AI agent while you code.

## Prerequisites

* Cursor installed (version 0.40 or later — MCP support requires a recent release)
* A Notara workspace with at least one connected tool connector
* An MCP endpoint and token from the Notara dashboard

## Step 1: Generate an MCP Token

1. In the Notara dashboard, go to **Connect → MCP Endpoints**.
2. Click **New Endpoint** and select the group whose tools you want Cursor to access.
3. Click **Generate Token**.
4. Copy the token — it's only shown once.

Your endpoint URL will be displayed next to the endpoint, for example:

```
https://app.notara.ai/mcp/g/acme/engineering
```

## Step 2: Add Notara to Cursor's MCP Settings

1. In Cursor, open **Settings** (Cmd+, on Mac, Ctrl+, on Windows/Linux).
2. Navigate to the **MCP** section (in the **Features** tab).
3. Click **Add MCP Server**.
4. Fill in the fields:

| Field                    | Value                              |
| ------------------------ | ---------------------------------- |
| **Name**                 | `Notara` (or any label you prefer) |
| **Type**                 | `SSE`                              |
| **URL**                  | Your Notara MCP endpoint URL       |
| **Authorization Header** | `Bearer ntr_your_token_here`       |

5. Click **Save**.

Alternatively, you can edit Cursor's MCP config file directly. Find it at `~/.cursor/mcp.json` (or `%APPDATA%\Cursor\mcp.json` on Windows) and add:

```json
{
  "mcpServers": {
    "notara": {
      "type": "sse",
      "url": "https://app.notara.ai/mcp/g/acme/engineering",
      "headers": {
        "Authorization": "Bearer ntr_your_token_here"
      }
    }
  }
}
```

## Step 3: Verify the Connection

1. Restart Cursor after saving the settings.
2. Open a new chat in Cursor (Cmd+L) and switch to **Agent** mode.
3. Type: `What tools do you have access to from Notara?`

Cursor should list the available tools, for example:

```
From Notara, I have access to:
- linear_search_issues, linear_create_issue, linear_list_projects
- github_list_repos, github_search_code
- read_context_document, search_context
```

## Transport: SSE vs stdio

Notara's MCP endpoint uses **SSE (Server-Sent Events)** transport, not stdio. This is the HTTP-based transport, meaning:

* No local process is spawned — the connection goes directly to Notara's servers
* Authentication is via the `Authorization` header
* Works behind corporate proxies (as long as HTTPS/SSE is allowed)

If Cursor's UI asks you to choose a transport, select **SSE** (not "Command" or "stdio").

## Using Notara in Cursor

Once connected, you can use Notara tools inline in Cursor's agent chat. Examples:

**Look up a Linear issue:**

```
@Notara What's the status of the auth timeout bug in Linear?
```

**Create a GitHub issue from a code review:**

```
I found a memory leak in src/workers/processor.ts line 142. 
Create a GitHub issue for this with a medium priority label.
```

**Search your docs:**

```
What does our runbook say about rolling back a database migration?
```

**Use a skill:**

```
Use the eng-error-digest skill to summarize the errors in our logs library.
```

## Tool Permissions in Cursor

Permissions apply the same way as in Slack. If a tool has `requires_approval` status, Cursor will receive a message like:

```
This action (linear_create_issue) requires admin approval. 
A request has been sent to your workspace admin. 
You'll be notified when it's approved or denied.
```

The admin will receive an approval request in their Slack DM. Once they approve, the tool executes and the result is available.

## Troubleshooting

**Tools not listed after connecting:** check the **MCP** section in Cursor settings to see if the server shows a connection error. Common causes: invalid token, network issues, or no active connectors in the group.

**SSE connection drops:** Cursor reconnects automatically. If tools keep disappearing, check if your token has been revoked in the Notara dashboard.

**Wrong tools showing up:** make sure the group slug in the endpoint URL matches the group you intend to use. Each group has its own tool and context configuration.