Cursor

Prerequisites and availability

You need a Cursor version and workspace policy that allow remote HTTP MCP and browser OAuth, plus a Stratifyre account. The supported v1 route is the remote server plus portable skills. Native Cursor skills or rules packaging is optional and must not be assumed unless Stratifyre’s published compatibility information records a passing pinned smoke test.

Connect and verify

Add the production server in Cursor’s current MCP settings flow. Where Cursor accepts JSON configuration, use the client’s documented schema with this endpoint:

https://app.stratifyre.com/mcp

For example, supported Cursor versions may use a configuration shaped like:

{
  "mcpServers": {
    "stratifyre": {
      "url": "https://app.stratifyre.com/mcp"
    }
  }
}

Complete OAuth in the browser launched by Cursor. Confirm the server is enabled, then ask Cursor to discover the live manifest, check available status and scopes, resolve an instrument with marketdata_search, and read existing strategies. Do not create, update, delete, or launch a backtest in this first read-only task. Do not store credentials in mcp.json.

Next steps

Continue with Work with Stratifyre for strategy and backtest workflows. See Troubleshooting and Security for portable skills, permission limits, interrupted jobs, updates, and removal.