Other MCP Clients

Use this path when your client is not covered by a client-specific guide, or when its native package is unavailable or unverified.

Prerequisites

You need a Stratifyre account and a client that supports remote Streamable HTTP MCP with browser-based OAuth authorization. The client must be able to discover the live server manifest. Its available scopes, mutation controls, and skill installation location are client-specific.

Release/evidence pin: @stratifyre/[email protected], bounded generic-streamable-http-oauth client profile with tool approval enabled, fallback path only; profile smoke evidence not recorded.

Connect and verify

Add a remote server with these values:

Setting	Value
Name	stratifyre
URL	https://app.stratifyre.com/mcp
Transport	Streamable HTTP
Authentication	OAuth through the client

Complete OAuth in the browser. Do not add API keys, access tokens, or secrets to configuration files.

Confirm the connection by asking the client to discover the live manifest, inspect available scopes and system status, and list your strategies. This is deliberately read-only; an empty strategy list can still be a successful connection. Resolve named instruments in Stratifyre or provide canonical IDs; the current MCP manifest has no direct market-data search tool.

Create and review a strategy

After connection, use the live manifest and schemas as authoritative. A safe strategy workflow is raw intent → AI conversion → asynchronous creation → status → inspection → backtest review:

1. Ask the client to call strategy_create with your raw intent, resolved instruments or baskets, and a new client-generated idempotency key. Do not ask it to generate or submit rule JSON.
2. Poll strategy_create_status using the returned operation ID until the result is terminal.
3. If completed, call strategy_get to inspect the persisted strategy and its generated rules before deciding whether to start and review a backtest.

A waiting result means keep polling. A failure has safe, sanitized errors and no follow-up action; do not infer internal causes or retry blindly. A completed operation remains an immutable terminal record. If its strategy is deleted later, the status identifies it as deleted and provides no strategy or backtest actions.

Keep the same idempotency key when recovering from a lost response: the same request replays the original operation without another allocation or billable create. Never reuse a key for a different request; the server returns IDEMPOTENCY_KEY_REUSED without changing anything.

You may create several approved ideas in parallel, but each accepted request is independently billable and governed by applicable usage and concurrency limits. Parallel creation is not a batch transaction: each request can independently complete or fail. Review each terminal result separately before backtesting.

Create, backtest, and limits

After verification, ask the client 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. Capabilities, scopes, entitlements, and concurrency limits are client- and server-dependent. Independent candidates may partially fail and are not atomic.

Approval is conversational guidance, not server enforcement. A bounded acceptance profile must record the client version, Streamable HTTP and OAuth support, and tool-approval behavior before this path can be labeled supported.

Update, remove, or use the portable fallback

To update, replace both copied skill directories from the next versioned bundle and use the client’s normal MCP configuration update flow. To remove, delete the stratifyre server entry, remove the copied skills, and revoke OAuth authorization in Stratifyre if desired. The portable bundle is the fallback when a client lacks native packaging.

Documentation basis: Model Context Protocol transport documentation, https://modelcontextprotocol.io/specification/2025-06-18/basic/transports, checked 2026-09-01; this generic profile is not yet smoke-tested.

If setup fails, verify remote Streamable HTTP and OAuth support, then consult the client’s own configuration documentation.

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.