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.

Release/evidence pin: @stratifyre/[email protected], Cursor workspace fixture using the JSON shape shown below, fallback path only; client smoke evidence not recorded.

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, 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.

Create, backtest, and limits

After verification, ask Cursor to prepare a complete strategy_create payload, show it for approval, create it once, poll strategy_create_status, and call strategy_get. For a backtest, review and approve the complete backtest_start payload, poll backtest_status, and inspect the result. Resolve named instruments in Stratifyre or provide canonical IDs; the current MCP manifest has no direct market-data search tool. The live server, granted OAuth scopes, account entitlements, and workspace policy determine capabilities and limits.

Approval is conversational guidance, not a server-enforced confirmation. Independent calls may partially fail and are not atomic.

Update, remove, or use the portable fallback

Update by replacing both copied skill directories from the next versioned fallback bundle. Remove the stratifyre server entry from Cursor’s MCP settings, delete the copied skills, and revoke OAuth in Stratifyre if desired. Native Cursor skills/rules are not published because their pinned smoke test is not run.

Documentation basis: Cursor MCP documentation, https://cursor.com/docs, checked 2026-09-01; use the installed client’s current MCP schema and the named fixture is not yet smoke-tested.

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.