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.

Release/evidence pin: @stratifyre/[email protected], VS Code workspace fixture using .vscode/mcp.json with the server entry shown below, fallback path only; client smoke evidence not recorded.

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, and read your strategies. An unavailable tool or authorization error indicates the live manifest, granted scopes, or workspace policy does not permit it.

Create, backtest, and limits

After verification, ask Copilot 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. Capabilities and limits come from the live server, OAuth scopes, account entitlements, and VS Code/Copilot workspace policy.

Approval is conversational guidance, not server enforcement. Independent candidate calls can fail separately; do not claim atomicity.

Update, remove, or use the portable fallback

Update by replacing both copied skill directories from the next versioned fallback bundle. Remove the stratifyre entry from .vscode/mcp.json or the user MCP configuration, delete the copied skills, and revoke OAuth in Stratifyre if desired. Native VS Code/Copilot packaging is not published because its pinned smoke test is not run.

Documentation basis: VS Code MCP server and configuration documentation, https://code.visualstudio.com/docs/agent-customization/mcp-servers and https://code.visualstudio.com/docs/agents/reference/mcp-configuration, checked 2026-09-01; the named workspace 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.