Connect Cursor

← Agents

OAuth limitation: The endpoint format below is valid for Cursor, but Monomer login has not been verified. If Cursor asks for a Client ID or reports unsupported registration, stop and contact Monomer. Use only the client registration details supplied by Monomer.

Add the server

Open ~/.cursor/mcp.json for your user configuration, or .cursor/mcp.json for a single project. Add monomer under mcpServers, preserving existing entries:

{
  "mcpServers": {
    "monomer": {
      "url": "https://api.monomer.cc/mcp"
    }
  }
}

Open Cursor’s MCP settings, enable Monomer, and start its OAuth connection action if offered. Complete the Monomer sign-in flow, then make Monomer’s tools available to Agent. Cursor documents these files and remote OAuth in its MCP guide.

Monomer’s Settings → Agents → Cursor also provides Copy configuration for your environment and Add to Cursor. The latter uses Cursor’s MCP install-link format to open the installation prompt. Review the configuration before installing it; adding the server does not verify Monomer sign-in.

Monomer requires a compatible client registration method. Cursor’s documentation does not establish CIMD support for this connection; a valid URL configuration is only the first step.

Verify

Only after OAuth completes, run the Workspace access check in Agent. Follow troubleshooting for other connection problems.

No successful Monomer OAuth test is claimed for Cursor.

After connecting, follow Direct your agent to read resources, follow availableOperations, and fetch input schemas with monomer_describe.