Back to MCP setup

Cursor Setup

Connect ContextDrop to Cursor

Connect Cursor to ContextDrop and give it access to your persistent project memory through MCP.

Cursor setup video coming soon

Before you start

What you need

  • A ContextDrop account
  • Cursor installed

Step 1

Create the MCP configuration

In the root of your Cursor project, create a .cursor/mcp.json file.

.cursor/mcp.json

{
  "mcpServers": {
    "contextdrop": {
      "url": "https://mcp.usecontextdrop.com/mcp"
    }
  }
}

Step 2

Open Cursor's MCP settings

After saving the configuration, open Cursor's MCP settings. ContextDrop will appear in your connected MCP servers.

ContextDrop

Your ContextDrop MCP server will appear in the MCP list.

Step 3

Authenticate with ContextDrop

On your first connection, Cursor will show that ContextDrop requires authentication.

Authentication required

Click the authentication option and complete the ContextDrop OAuth flow in your browser. Sign in to ContextDrop and authorize the connection when prompted.

Step 4

Confirm the connection

Once authentication is complete, Cursor reconnects to ContextDrop and the MCP server becomes available.

ContextDrop connected

Your ContextDrop MCP tools are now available in Cursor.

Verify

Verify the connection in ContextDrop

You can also confirm that Cursor has been authorized from your ContextDrop dashboard.

Settings → MCP & Integrations → Authorized Clients

Your Cursor connection will appear in the list of authorized MCP clients.

Step 5

Configure Cursor for autonomous memory

ContextDrop can automatically preserve durable project knowledge from your coding conversations. Add the following instruction to your Cursor project rules or instructions.

Recommended instruction

Use ContextDrop as the persistent memory layer for this project.

During normal coding conversations, recognize durable project-specific knowledge and proactively preserve it in ContextDrop without waiting for me to explicitly ask you to save it.

Use ContextDrop memory when you need existing project context, architectural decisions, requirements, constraints, conventions, preferences, workflows, or other durable project knowledge.

When new durable knowledge is established:
- Use save_memory when it should be added to project memory.
- Search existing memory first when related knowledge may already exist.
- If an existing memory has materially changed, use update_memory instead of creating a duplicate.
- Ignore information that is temporary, speculative, casual, generic programming knowledge, one-off questions, temporary debugging details, intermediate reasoning, or short-lived tasks.
- Never store secrets or credentials such as API keys, access tokens, refresh tokens, session cookies, database credentials, or signing/encryption keys.
- Avoid creating duplicate memories.
- Use the appropriate ContextDrop category and memory type.
- Continue working on my actual coding request normally after managing memory.
- Never claim that something was saved unless the ContextDrop tool call succeeds.

ContextDrop owns persistent memory. Do not create a separate memory document or maintain a separate memory system.

### Conversational Continuity

Memory operations should remain unobtrusive and must not interrupt the user's workflow.

When durable project knowledge is established:
- Search existing memories and save or update knowledge when appropriate.
- Continue the user's original task immediately after a successful operation.
- Do not announce routine memory searches or successful saves.
- Do not explain the memory-management process unless the user asks.
- Do not ask unrelated follow-up questions merely because a memory was saved.
- Never claim a save or update succeeded unless the tool confirms success.

Mention memory operations only when the user asks, when clarification is necessary, or when a meaningful conflict, failure, or important decision requires the user's attention.

Why this matters

Cursor recognizes durable project knowledge from your coding conversations, while ContextDrop handles persistent storage, duplicate detection, and updating existing project knowledge.

Secure OAuth authentication

ContextDrop uses OAuth to authorize Cursor. You authenticate through ContextDrop without sharing your ContextDrop password with Cursor.

← Back to MCP setup