Document Cursor MCP setup using mcp-remote

[ricpruss]

Summary

Cursor can reach the OutSystems MCP endpoint, but its native remote MCP OAuth flow currently registers this redirect URI:

cursor://anysphere.cursor-mcp/oauth/callback

The OutSystems MCP server rejects that during client registration with:

redirect_uri \"cursor://anysphere.cursor-mcp/oauth/callback\" rejected: redirect_uri must use scheme http for loopback

A working Cursor setup is to configure the MCP as a project-local stdio server through mcp-remote, so OAuth uses an HTTP loopback callback instead.

Proposed README change

I pushed a small docs branch here:

https://github.com/ricpruss/outsystems-mcp/tree/docs/cursor-mcp-install

Compare URL:

https://github.com/OutSystems/outsystems-mcp/compare/main...ricpruss:docs/cursor-mcp-install?expand=1

The change adds a Cursor-specific install section with this project-scoped .cursor/mcp.json shape:

{
  "mcpServers": {
    "outsystems": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://<my-tenant>/mcp",
        "7890",
        "--transport",
        "http-only"
      ]
    }
  }
}

It also suggests adding the OutSystems MCP skill content to a project Cursor rule and reloading the Cursor window.

Validation

This path worked locally in Cursor against an OutSystems tenant. The native url-based Cursor MCP config failed with the redirect URI error above; the mcp-remote bridge completed the OAuth flow using http://localhost:7890/callback.