auth object in mcp.json.
Before you start, ask Novaplan Support to confirm the approved OAuth app, Client ID, and Client Secret for your workspace.
Configuration
Open Cursor Settings > Tools and Integrations > New MCP Server, or edit your project’s.cursor/mcp.json:
If
scopes is omitted, Cursor’s current documentation says it reads scopes_supported from /.well-known/oauth-authorization-server. To limit access, list only the scopes approved for the tools you need. Ask Novaplan Support to confirm the server-side defaults for your workspace.Using Environment Variables
Use Cursor’s${env:VAR} interpolation to keep secrets out of config files:
Redirect URIs
Register the callback URI for each Cursor surface your team uses in the Novaplan OAuth app:
Cursor’s current MCP documentation lists the localhost callback for the desktop app and the HTTPS callback for web/agents. Some older desktop installations still use the
cursor:// callback. The accessible Novaplan OAuth source accepts that legacy URI as well as localhost and HTTPS redirects, but the deployed Enterprise app still needs a sign-in test. A redirect mismatch means the exact URI sent by Cursor is not registered; check the authorization request before changing the OAuth app.