Connect the MCP

Cursor and other clients

Any MCP client that supports remote servers over HTTP with OAuth can use Recallr.

Cursor#

Add Recallr to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "recallr": {
      "url": "https://mcp.recallr-ai.org/mcp"
    }
  }
}

Cursor shows Recallr in its MCP settings and opens Recallr's sign-in in your browser when it first connects.

VS Code#

Add a server to .vscode/mcp.json in your workspace, or run MCP: Add Server from the command palette and choose HTTP:

{
  "servers": {
    "recallr": {
      "type": "http",
      "url": "https://mcp.recallr-ai.org/mcp"
    }
  }
}

Windsurf#

Add Recallr to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "recallr": {
      "serverUrl": "https://mcp.recallr-ai.org/mcp"
    }
  }
}

Any other client#

• Transport: Streamable HTTP, POST https://mcp.recallr-ai.org/mcp.
• Auth: OAuth 2.1 with PKCE (S256). The client learns everything from the 401 answer's WWW-Authenticate header and https://mcp.recallr-ai.org/.well-known/oauth-protected-resource, then registers itself at /register.
• Redirects: https callbacks, or http://localhost and http://127.0.0.1 on any port for desktop clients.

Clients without OAuth#

A client that only runs local (stdio) servers can reach Recallr through the open-source mcp-remote bridge, which handles the sign-in in your browser:

{
  "mcpServers": {
    "recallr": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.recallr-ai.org/mcp"
      ]
    }
  }
}

Something missing or wrong? Ask in the forum or write to support@recallr-ai.org.