Cursor

Cursor can use Memside as a remote MCP server. This allows Cursor agents to read selected Memories, checkpoints, Operating Rules, and other saved project context before planning, editing, or reviewing code.

The project configuration below is the simplest place to start. It keeps the connection limited to one project and can use OAuth when supported by the installed Cursor version.

Before starting

Install a current Cursor version with MCP support.
Sign in to Memside in the browser used for OAuth.
Open the project that needs the Memside connection.

Add Memside to the project

Open the project in Cursor.
Create the .cursor folder if it is not already present.
Create or open .cursor/mcp.json.
Add the following configuration.

{
  "mcpServers": {
    "memside": {
      "type": "streamable-http",
      "url": "https://api.memside.com/mcp/"
    }
  }
}

Save the file.
Open Cursor MCP settings and confirm that memside appears.
If Cursor opens OAuth, sign in to Memside and approve the connection.
Restart Cursor if the tools do not appear.

Make Memside available in every project

Use the same configuration in the global file:

~/.cursor/mcp.json

Use project configuration when Memside is needed only for one workspace. Use global configuration when the same connection should be available across Cursor projects.

API-key authentication

Some Cursor versions require a bearer header instead of OAuth. In that case:

Create a Memside API key under Settings > Developer & API.
Add it only through a secure header or secret setting supported by Cursor.
Do not place the real key in a shared repository file.

Confirm and test the connection

Open Cursor MCP settings and confirm that memside is enabled and its tools are listed. Then run:

Use Memside to find the latest project checkpoint before planning changes.

Troubleshooting

Restart Cursor after changing mcp.json.
Check that the JSON is valid and the file is in the correct folder.
Complete the Memside OAuth flow if a browser window opens.
Confirm that the installed Cursor version supports remote MCP servers.
Use API-key authentication only through a secure setting supported by Cursor.