ChatGPT
Availability and prerequisites
Section titled “Availability and prerequisites”You need ChatGPT on the web with Developer mode and custom MCP app support. Full MCP write support is rolling out for Business and Enterprise/Edu; a workspace admin/owner must enable Developer mode, and only an admin/owner can publish the app. Enterprise/Edu workspaces can grant developer access through RBAC. You also need a Stratifyre account. The source metadata is tools/agent-skills/adapters/chatgpt/app.json; it is not a local skill installer.
Release/evidence pin: @stratifyre/[email protected], ChatGPT web Business or Enterprise/Edu workspace fixture with Developer mode enabled by an admin/owner, fallback path only; workspace smoke evidence not recorded.
Connect and verify
Section titled “Connect and verify”In the supported ChatGPT workspace surface, ask an administrator or permitted developer to add a remote MCP connector. Enter the exact production endpoint:
https://app.stratifyre.com/mcpComplete OAuth in the browser, wait for tool scanning to finish, and follow the workspace’s action controls. Enterprise/Edu admins can refresh and approve changed actions; Business apps may need to be recreated and republished for changes. Do not paste API keys, OAuth tokens, or credentials into a chat or app configuration.
Ask ChatGPT to begin read-only:
Discover the live Stratifyre MCP manifest, inspect available status and scopes, and read my existing strategies. Do not query market data or resolve instruments through MCP. Do not change anything or start a backtest.
The connector’s live tools, granted scopes, and policy controls are authoritative. If the workspace does not expose a tool or write action, it is unavailable; do not attempt to bypass the restriction.
Create, backtest, and limits
Section titled “Create, backtest, and limits”After the read-only check, ask ChatGPT 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 are limited by the live manifest, OAuth scopes, account entitlements, workspace action controls, and the ChatGPT surface; agent mode does not use custom apps and mobile does not support these apps.
ChatGPT may request confirmation for write actions, but Stratifyre conversational approval remains agent guidance and is not server enforcement. Independent candidate calls are not atomic.
Update, remove, or use the portable fallback
Section titled “Update, remove, or use the portable fallback”For Enterprise/Edu, refresh app actions and review the diff. For Business, recreate and republish the app when metadata or tools change. Remove or disable the app in ChatGPT workspace settings and revoke OAuth in Stratifyre if desired. Use the copyable workflow instructions in tools/agent-skills/adapters/chatgpt/README.md or the generic MCP page if the workspace cannot create custom apps.
Documentation basis: OpenAI Help Center, https://help.openai.com/en/articles/12584461-developer-mode-and-full-mcp-connectors-in-chatgpt, checked 2026-09-01; the named workspace OAuth/action fixture is not yet smoke-tested.
Next steps
Section titled “Next steps”ChatGPT uses its remote connector and importable workflow instructions rather than local skill directories.
Continue with Work with Stratifyre for strategy and backtest workflows. See Troubleshooting and Security for permission limits, interrupted jobs, updates, and removal.