VS Code and GitHub Copilot

Prerequisites and availability

You need a VS Code and GitHub Copilot configuration that exposes remote MCP and browser OAuth under your workspace policy, and a Stratifyre account. Remote MCP plus portable skills is the supported v1 path. Native VS Code or Copilot skill packaging is conditional on a published passing pinned smoke test and is not implied by this guide.

Connect and verify

Use VS Code’s current MCP: Add Server command or its documented workspace configuration. Where the installed version supports .vscode/mcp.json, configure the remote HTTP endpoint using its current schema, for example:

{
  "servers": {
    "stratifyre": {
      "type": "http",
      "url": "https://app.stratifyre.com/mcp"
    }
  }
}

Start the server through VS Code’s MCP controls and complete OAuth in the browser. Do not commit credentials or OAuth tokens.

Verify with a read-only task: ask Copilot to discover the live manifest, inspect available status and scopes, resolve an instrument with marketdata_search, and read your strategies. An unavailable tool or authorization error indicates the live manifest, granted scopes, or workspace policy does not permit it.

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.