Claude Code
Prerequisites and availability
Section titled “Prerequisites and availability”You need Claude Code with remote HTTP MCP and browser OAuth available in your installed version, plus a Stratifyre account. The v1 native plugin is not published: the pinned native smoke test has not run. Download the versioned fallback bundle from the release assets or copy tools/agent-skills/skills/ from this repository, then connect the remote MCP server below.
Release/evidence pin: @stratifyre/[email protected], Claude Code 2.1.207 fixture, fallback path only; client smoke evidence not recorded.
Connect and verify
Section titled “Connect and verify”Run:
claude mcp add --transport http stratifyre https://app.stratifyre.com/mcpUse Claude Code’s MCP controls (such as /mcp) to complete OAuth in your browser and inspect the connection. Choose a user or project scope using Claude Code’s current configuration controls. Never place Stratifyre credentials in a repository.
Start with a read-only request:
Discover the live Stratifyre MCP manifest, check my available status and scopes, and list my strategies. Do not mutate anything.
If a tool or scope is unavailable, treat that as a client, policy, or authorization limit rather than guessing an alternative request.
Create, backtest, and limits
Section titled “Create, backtest, and limits”After the read-only check, ask Claude to draft a strategy_create payload, show it for approval, create it, poll strategy_create_status, and call strategy_get. For a backtest, show and approve the complete backtest_start payload, poll backtest_status, and inspect the result. Use canonical instrument IDs supplied by the user or resolved in Stratifyre; the current MCP manifest has no direct market-data search tool. Capabilities and limits are determined by the live server, OAuth scopes, account entitlements, and Claude workspace policy; each write and job remains subject to those limits.
Conversational approval is workflow guidance, not server enforcement. If a tool is unavailable, do not substitute an invented tool or field.
Update, remove, or use the portable fallback
Section titled “Update, remove, or use the portable fallback”Update by downloading the next versioned fallback bundle and replacing both skill directories together. Remove the stratifyre MCP entry with Claude Code’s normal MCP controls, delete copied skills, and clear authorization with /mcp or claude mcp logout stratifyre.
Documentation basis: Claude Code MCP documentation, https://code.claude.com/docs/en/mcp, checked 2026-09-01; native support remains unverified in the pinned fixture.
Next steps
Section titled “Next steps”Portable skills plus remote MCP are the supported v1 fallback. The native plugin becomes a supported artifact only after its pinned smoke test and publication evidence are recorded in the compatibility matrix.
Continue with Work with Stratifyre for strategy and backtest workflows. See Troubleshooting and Security for portable skills, permission limits, updates, and removal.