Connect your AI assistant

The Itoflow plugin connects your assistant to Itoflow at https://mcp.itoflow.ai/mcp and adds two skills: the Itoflow skill for research and account tasks, and the worker skill for local analysis. Install it from the public itoflow/skills repository, then sign in with your Itoflow account.

Install the plugin → Sign in to Itoflow → Check the connection → Read and make changes

Install the plugin

claude plugin marketplace add itoflow/skills
claude plugin install itoflow@itoflow

Open Claude Code, enter /mcp, select the Itoflow server, choose Authenticate and sign in. Then use /itoflow:itoflow for the Itoflow skill or /itoflow:worker for local analysis.These are terminal commands; in JetBrains, run them in the IDE’s terminal. The Claude desktop app’s Code tab and the VS Code extension share the same settings, so the marketplace you add here shows up there too. In VS Code you can also type /plugins and add itoflow/skills on the Marketplaces tab.

This works for chat on claude.ai in a browser, chat in the Claude desktop app, and Cowork.

Open Customize → Plugins, select Add, then Add marketplace.
Enter itoflow/skills and install Itoflow.
Open the plugin’s Connectors tab, add the Itoflow connector, then connect it and sign in. Adding a plugin does not connect its server.

The plugin is then on your Claude account, so it also works in the Claude mobile app and syncs to Claude Code. On Team and Enterprise plans, an Owner decides whether members can add marketplaces and adds the connector for the organization.

codex plugin marketplace add itoflow/skills
codex plugin add itoflow@itoflow
codex mcp login itoflow

Start a new task, then pick the Itoflow skill or the worker skill. These are Codex CLI commands; Codex in the ChatGPT desktop app then installs Itoflow from its Plugins tab.The Codex IDE extension doesn’t install plugins, so add the two parts yourself. Open the gear menu, choose MCP servers → Add server, select Streamable HTTP, enter https://mcp.itoflow.ai/mcp and select Authenticate. Then add the skills with npx skills add itoflow/skills -a codex.

Download itoflow-openai.zip from the latest release.
On chatgpt.com, open Plugins, select Add, then Upload plugin archive, and choose the ZIP.
Find Itoflow in your personal plugins and install it. Connect it and sign in when ChatGPT asks.
In a chat, type @ and pick Itoflow.

The upload option appears only when your plan or workspace allows it. A workspace admin can instead import https://github.com/itoflow/skills under Admin Console → Plugins → Add → Import marketplace, which keeps the plugin up to date. ChatGPT can label a plugin that declares an MCP server Desktop only; if it labels Itoflow that way, use it in the ChatGPT desktop app. See Plugins in ChatGPT.

In Gemini CLI:

gemini extensions install https://github.com/itoflow/skills

Gemini CLI opens your browser to sign in the first time it uses an Itoflow tool.In the Gemini app, add the two parts yourself. On gemini.google.com, open Settings → Connected Apps, choose Add a custom app under Custom apps, enter https://mcp.itoflow.ai/mcp and sign in. Then upload itoflow-skill-itoflow.zip and itoflow-skill-worker.zip under Settings → Skills → Upload. Both also work in the Gemini mobile app. Custom apps need a personal Google account, age 18 or over, a location in the US, and Keep Activity turned on.

In the Copilot CLI:

copilot plugin marketplace add itoflow/skills
copilot plugin install itoflow@itoflow

In VS Code, with the chat.plugins.enabled setting on, run Chat: Install Plugin From Source from the Command Palette and enter https://github.com/itoflow/skills. Sign in when your browser opens.In Visual Studio and JetBrains, add the server URL from Copilot Chat’s MCP settings, then copy the skills/ folders to ~/.copilot/skills/. Skills need Visual Studio 18.5 or later; in JetBrains, turn them on under Settings → GitHub Copilot → Chat → Agent. On Business and Enterprise plans, an admin must turn on the MCP servers in Copilot policy.

Cursor loads plugins from ~/.cursor/plugins/local/. Clone the repository there, so git pull brings updates:

git clone https://github.com/itoflow/skills ~/.cursor/plugins/local/itoflow

Then restart Cursor, or run Developer: Reload Window, and sign in when Cursor asks. On Teams and Enterprise plans, an admin controls local plugins, or imports the repository under Dashboard → Plugins & MCPs → Add Marketplace → Import from Repo.

Add the two parts yourself.

Add the skills with npx skills add itoflow/skills, copy the skills/ folders into .agents/skills/, which many clients read, or upload both skill ZIPs from the latest release.
Add the server with these settings:
Setting Value
Server name itoflow
Server URL https://mcp.itoflow.ai/mcp
Transport Streamable HTTP (often labeled HTTP)
Authentication OAuth, through the client’s browser sign-in
Sign in when the client asks.

Setting	Value
Server name	`itoflow`
Server URL	`https://mcp.itoflow.ai/mcp`
Transport	Streamable HTTP (often labeled HTTP)
Authentication	OAuth, through the client’s browser sign-in

The skills need the server connection.

If you install the plugin and added the server by hand earlier, remove the older entry so you have one Itoflow connection. Your client stores the sign-in for you. Never paste a token or browser cookie into the conversation. If the sign-in expires, reconnect from the client’s MCP settings.

Make your first request

Check that your client lists three Itoflow tools: search, execute and workspace_list. Your first request only reads, so nothing changes while you test. Paste this into your assistant:

Use Itoflow to list my portfolios. Do not create or change anything.

Open in Claude

Start this in Claude with the Itoflow plugin.

Open in ChatGPT

Start this in ChatGPT with the Itoflow plugin.

Using another client? Copy the prompt with the button on the code block. Any list, even an empty one, means the connection works. A “connected” badge alone doesn’t prove that requests work. After that, your assistant can also make changes, such as creating monitors, editing strategies and importing portfolios. See what you can ask for. Next, try the usage examples. If something fails, see MCP troubleshooting.

Use Itoflow in Claude Code’s auto mode

In auto mode, Claude Code has a classifier review each tool call before it runs. It can block an execute call that sends holdings or weights to Itoflow and label it “Data Exfiltration”, because it doesn’t know you send that data to Itoflow on purpose. Tell it in your user settings, ~/.claude/settings.json:

{
  "autoMode": {
    "environment": [
      "$defaults",
      "Trusted external service: Itoflow (mcp.itoflow.ai), where I send portfolio holdings and weights for analysis"
    ]
  }
}

Keep "$defaults". Without it, your entry replaces Claude Code’s built-in list, including its own data rules.
Claude Code reads autoMode from your user settings or your organization’s managed settings, not from a project’s .claude/settings.json.
Run claude auto-mode config to check what it loaded.
The classifier still reviews every call. The entry tells it that sending portfolio data to Itoflow is expected.

You can also let the read-only search tool run without review. With the plugin, its name is mcp__plugin_itoflow_itoflow__search; with a server you added by hand as itoflow, it is mcp__itoflow__search. Enter /mcp and select the tool to see its full name.

{
  "permissions": {
    "allow": ["mcp__plugin_itoflow_itoflow__search"]
  }
}

Don’t pre-approve execute. It is the tool that sends your data, so keep auto mode reviewing it. If a call is still blocked as “Data Exfiltration”, run claude auto-mode config and check that your entry is there. Pressing r under Recently denied in /permissions doesn’t approve the call: it only lets your assistant try again, and the classifier reviews it again. Approving in chat doesn’t clear this rule either. If your entry is loaded and calls are still blocked, leave auto mode while you work with Itoflow and approve each execute call yourself. Your assistant should tell you when a call is blocked. It should never split, encode or rename data to get past the check. Your assistant’s program carries the data it sends, such as instrument names and weights. Itoflow keeps a risk run’s book only in your account’s risk sandbox, and doesn’t save it as a portfolio. The sandbox sleeps about two minutes after your last risk call, once none of your runs is going, and its files go with it. A finished run’s figures and full engine output stay available for 24 hours in owner-scoped storage. Use getRiskRunArtifact for the full output. The request itself stays in the sandbox. Stored outputs expire from storage within three days; cancellation and timeout retain their terminal outcomes. Resolving an identifier can add the instrument it finds to Itoflow’s shared symbol list, as any lookup does.

Releases and archives

Each new plugin version publishes a GitHub release. Installing from itoflow/skills gives you the latest one. To install without Git, download itoflow.zip, unzip it into a folder named itoflow and add that folder as a marketplace, for example claude plugin marketplace add ./itoflow. Keep the folder in place. The same ZIP works with Claude’s Upload plugin. Risk-run results include a top-level analytics reference. Copy the complete document through the owner-authorized artifact route, using gzip byte ranges for large files, and verify its compressed and raw sizes and hashes. Select needed records in your workspace; do not print or parse the entire document inside a chat worker. See risk runs.

Get started

Platform

Use cases

Features

HTTP API

Troubleshooting

Endpoints