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

# Connect Hyper Memory to the Cursor AI Editor

> Add Hyper's MCP server to Cursor in three steps and give your AI coding assistant persistent memory across every project and session.

Cursor supports the Model Context Protocol natively, which means connecting Hyper takes less than two minutes and requires no plugins or extensions. Once set up, Hyper gives Cursor's AI a persistent memory layer — decisions you've made, patterns you prefer, and context from past sessions all flow into every new conversation automatically.

## Add the MCP Server

<Steps>
  <Step title="Open Cursor Settings">
    Launch Cursor and navigate to **Settings** (gear icon, or `Cmd+,` on macOS / `Ctrl+,` on Windows and Linux).
  </Step>

  <Step title="Go to Features → MCP Servers">
    In the left sidebar, click **Features**, then scroll to the **MCP Servers** section.
  </Step>

  <Step title="Add a new server">
    Click **Add new MCP server** and fill in the following fields:

    | Field | Value                                  |
    | ----- | -------------------------------------- |
    | Name  | `hyper`                                |
    | URL   | `https://hyperlink.gethyper.space/mcp` |

    Click **Save** to apply the configuration.
  </Step>

  <Step title="Authenticate with Google">
    The first time Cursor calls a Hyper tool, an OAuth 2.0 flow launches in your browser. Sign in with Google to authorize access. Your token is saved to `~/.hyper/token` and reused for all future sessions — you won't be prompted again.
  </Step>
</Steps>

<Note>
  Cursor stores MCP server configurations in its internal settings database, so there's no JSON file to edit manually. The UI in Features → MCP Servers is the canonical way to manage servers.
</Note>

***

## Verify the Connection

Once the server is saved, confirm Hyper is live before you rely on it in a real project.

<Steps>
  <Step title="Open Cursor Chat">
    Press `Cmd+L` (macOS) or `Ctrl+L` (Windows/Linux) to open the AI chat panel.
  </Step>

  <Step title="Send a connect message">
    Type the following and press Enter:

    ```text theme={null}
    Connect to Hyper
    ```
  </Step>

  <Step title="Confirm the briefing">
    Cursor's AI will call the `connect` tool and return a workspace briefing similar to this:

    ```text theme={null}
    Connected to Hyper ✓
    Workspace: your-workspace-name
    Identity loaded: [your name / role]
    Pinned context: [any active memories]
    ```

    If you see a structured briefing like this, Hyper is fully operational.
  </Step>
</Steps>

<Tip>
  After a successful connection, try asking Cursor something that references past work — for example, "What decisions have we made about the auth system?" — to confirm that memory retrieval is working end-to-end.
</Tip>

***

## How Hyper Enhances Cursor's AI

With Hyper connected, Cursor's AI gains capabilities it doesn't have out of the box:

<CardGroup cols={2}>
  <Card title="Persistent Context" icon="brain" href="/guides/cursor-setup#verify-the-connection">
    Memories from past sessions are available in every new chat — no more re-explaining your stack or conventions.
  </Card>

  <Card title="Team Knowledge" icon="users" href="/guides/team-onboarding">
    Shared workspaces mean your teammates' discoveries and decisions are part of Cursor's context too.
  </Card>

  <Card title="Project Identity" icon="fingerprint" href="/guides/cursor-setup#add-the-mcp-server">
    Hyper knows which project you're in and loads the right workspace automatically when you connect.
  </Card>

  <Card title="Selective Memory" icon="shield" href="/guides/incognito-mode">
    Use [Incognito Mode](/guides/incognito-mode) to pause memory writes whenever you're working on something sensitive.
  </Card>
</CardGroup>

***

## Troubleshooting

<Warning>
  If the `hyper` server shows as **disconnected** in Cursor's MCP panel, check that the URL is entered exactly as shown — no trailing slash, and `https://` (not `http://`) for the production server.
</Warning>

| Symptom                        | Fix                                                                                              |
| ------------------------------ | ------------------------------------------------------------------------------------------------ |
| MCP server shows as offline    | Confirm the URL `https://hyperlink.gethyper.space/mcp` is reachable and re-save the server entry |
| OAuth window doesn't open      | Check your system's default browser and ensure popups aren't blocked                             |
| `connect` tool not found       | Remove and re-add the MCP server entry; restart Cursor                                           |
| Memories seem stale or missing | Ask Cursor to call `connect` explicitly to force a fresh context load                            |

***

## Local Development

If you're running a local Hyper instance for development or testing, use the local URL instead:

| Field | Value                       |
| ----- | --------------------------- |
| Name  | `hyper-local`               |
| URL   | `http://localhost:8000/mcp` |

Add this as a second server entry alongside the production one, and switch between them as needed directly in the MCP Servers panel.