Skip to content

Troubleshooting and Security

Use the client’s connection controls and the live Stratifyre MCP manifest to diagnose problems. Do not work around missing capabilities by guessing requests, adding credentials to prompts, or repeatedly submitting writes.

A client must support remote Streamable HTTP MCP and browser-based OAuth. Connect it to:

https://app.stratifyre.com/mcp

Common outcomes have distinct meanings:

  • Empty strategy list: the connection can be healthy; the account may not have strategies yet.
  • Missing tool: the live manifest or client does not expose that capability.
  • Authorization error: the granted scopes, account policy, or workspace policy does not permit the operation.
  • OAuth unavailable: the installed client version, workspace plan, or administrator policy may not support the required flow.

Use the relevant client setup guide to verify current prerequisites. Never guess an alternative endpoint or request schema.

Complete OAuth in the browser opened by the client. Never put an API key, access token, OAuth token, or client secret in:

  • prompts or chat messages
  • project or workspace configuration
  • source control
  • portable workflow skills

The client should store and refresh its own OAuth authorization. Revoke access in Stratifyre if credentials or client access may be compromised.

A disconnect or polling timeout does not prove a write or job failed. Reconnect, then re-read persisted strategy and job state before taking another action. Follow returned nextActions or polling instructions until the job reaches a terminal state.

Never blindly resubmit a create, update, delete, or backtest request. Keep completed work, validation failures, unavailable capabilities, timeouts, and still-running jobs separate.

The portable Stratifyre Agent Skills package contains MCP and strategy-iteration workflow guidance for clients that support local skills. Copy both parent directories containing their SKILL.md files into the client’s supported skill location and keep each directory intact.

ChatGPT uses its remote connector and importable workflow instructions instead of a local skill-directory installation. Native client packaging is available only where published compatibility information records support; remote MCP plus portable skills remains the baseline elsewhere.

Skills guide client behavior only. Authentication, authorization, validation, billing, persistence, and execution remain with Stratifyre and the MCP client.

To update a connection:

  1. Use the client’s current MCP configuration flow.
  2. Replace both portable skill directories together where applicable.
  3. Reconnect and repeat the read-only verification request from the client guide.

To remove access:

  1. Remove the stratifyre MCP server from the client.
  2. Delete copied portable skill directories where applicable.
  3. Revoke the client’s OAuth authorization in your Stratifyre account.