---
title: Connect Cursor
description: Add Phasoric as a remote MCP server in Cursor and use permitted project knowledge in Agent.
slug: mcp-cursor
path: /mcp-cursor
section: MCP setup
availability: supported
nav_order: 6.5
canonical_url: https://developers.phasoric.com/mcp-cursor
markdown_url: https://developers.phasoric.com/mcp-cursor.md
mirror_url: https://phasoric.com/developers/mcp-cursor
---
# Connect Cursor to Phasoric

Complete [Prepare your Phasoric vault](https://developers.phasoric.com/mcp-client-setup), then use a Cursor version and workspace policy that allow remote MCP.

## Configure the server

1. Open `.cursor/mcp.json` in your project, or use `~/.cursor/mcp.json` for your user-wide configuration.
2. Add the following entry under the existing `mcpServers` object. Preserve any other servers:

```json
{
  "mcpServers": {
    "phasoric": {
      "url": "https://phasoric.com/api/mcp"
    }
  }
}
```

3. Open Cursor's MCP controls and enable/connect Phasoric. Follow its OAuth prompt to sign in to Phasoric and review consent. No static client secret or provider token is needed.
4. In Agent, enable the Phasoric tools and ask it to list your vaults. Read a named project note before using it to guide implementation.

Configuration locations and remote OAuth support follow [Cursor's official MCP documentation](https://cursor.com/docs/mcp). Team policy may limit which servers and tools can run. These steps target the local editor; a cloud agent's team MCP setup is a separate configuration.

## Make the context explicit

Try **“Read the architecture decision for this change from Phasoric. Explain the constraint before editing code.”** Review any tool approvals Cursor presents. For a note update, use the [Phasoric write-preview workflow](https://developers.phasoric.com/mcp-client-setup); automatic execution settings do not replace Phasoric's approval requirement.