Set up Volrix with your agent.

Add Volrix as a remote MCP server, sign in to your account, and check your connection before running a strategy.

volrix.ai/skill.md

Paste the copied skill link into your agent and ask it to set up Volrix. It will help connect Volrix and guide you through sign-in.

View setup skill ↗Download SKILL.md

The connection

Name:       volrix
URL:        https://mcp.volrix.ai/mcp
Transport:  Streamable HTTP
Auth:       OAuth (browser sign-in)

A Volrix account and a client that supports remote MCP with OAuth are required. Client features and workspace permissions vary. Reading a skill supplies instructions; adding the server and authorizing your account enables the tools.

Codex

codex mcp add volrix --url https://mcp.volrix.ai/mcp
codex mcp login volrix

Complete the browser sign-in, then return to Codex. If tools do not appear in the current conversation, restart or reload the client session. Reuse an existing Volrix connection if one is already configured.

Claude Code

claude mcp add --transport http --scope local volrix https://mcp.volrix.ai/mcp

Open Claude Code and run /mcp. Select Volrix, choose its authentication action, and complete browser sign-in. The command configures the current project's local scope. Use another scope only if you intend to share that configuration.

Claude and ChatGPT

Claude: in Settings → Connectors, add a custom connector named Volrix with the MCP URL above. Complete OAuth and enable it for your conversation where required.

ChatGPT: use the custom MCP app setup in Settings → Apps, where available. Developer mode or workspace administrator approval may be required. Enter the MCP URL, choose OAuth, connect, and add the app to your conversation.

Your AI client may require its own paid plan. A skill link cannot enable an unavailable connector feature or approve sign-in for you.

Other clients and skill installation

Use your client's remote MCP settings with the URL and OAuth details above. Editors and custom agents can also connect when their MCP implementation supports this transport and authentication flow.

Keep the connection skill in your agent

Download SKILL.md and place it in your client's skill directory. For a project skill, Codex uses .agents/skills/connect-volrix/SKILL.md; Claude Code uses .claude/skills/connect-volrix/SKILL.md. Preserve any existing file and reload skill discovery if needed.

Other clients use their own installation paths or import UI. You can also share the raw skill URL for one conversation without installing a persistent skill. MCP setup and OAuth are still required.

Verify, then research

Ask your connected agent: “Use Volrix to check my plan and available limits without running a backtest.” It should discover and call user_plan_info. A successful response verifies authenticated access.

For a strategy, first choose the market, date range, entry and exit rules, and position sizing. The agent can read Volrix's strategy guides with list_skills and get_skill, check available_duration, then validate and run your backtest using the appropriate engine.

If setup does not complete

  • Tools missing: enable the connector and reload the conversation.
  • Sign-in required or HTTP 401: use the client's authentication action.
  • Access denied or HTTP 403: check the returned account or workspace restriction.
  • Rate limit or HTTP 429: follow the retry guidance and check your plan limits.

Keep credentials in the client's sign-in flow. You do not need to paste tokens or passwords into a chat. For current client instructions, see Claude Code MCP and ChatGPT MCP apps.