Point your AI at CIOport

Updated 2026-07-06

CIOport ships a local, read-only MCP connector: attach Claude Desktop (or any MCP-capable agent) to the same live intelligence the terminal renders — world events, composite risk scores, macro series, market signals, the economic calendar — and, if you point it at a portfolio file you exported from the app, which events touched what you hold. It runs on your machine, talks only to CIOport's public data plane, and stores nothing.

Every tool returns context, never trade recommendations or investment advice. The connector cannot place orders, cannot see signed-in data, and never sends your holdings anywhere — the file you point it at is read locally, on your machine.

What you can ask

Tool	What it answers
`get_composite`	"How risky is Taiwan right now, and why?" — country/sector risk scores with their full decomposition
`get_events`	"Any high-severity protests this week?" — geolocated world events with sources and severity
`get_signals`	"What's market sentiment doing?" — gauges like Fear & Greed
`get_macro`	"Plot US CPI over the last year" — macro indicator series (FRED, World Bank)
`get_calendar`	"What releases are due this week?" — the economic calendar
`get_portfolio_hints`	"Which events touched my holdings?" — the event→holdings join over your exported portfolio
`get_exposure`	"Where is my geo-risk concentrated?" — exposure by country, sector, and issuer

Every answer can be asked as of a past moment — the connector reads the same retained snapshot history the app's time scrubber does, so "what did risk look like this morning?" is a first-class query. Estimated P&L is deliberately not a tool.

Setup

The connector lives in the CIOport repository (the mcp/ directory) and runs over stdio with Node 24 or newer — no build step, no account. Clone the repo, build the compute kernel once (make copy-wasm), then register it with your agent. For Claude Desktop, add to claude_desktop_config.json:

{
  "mcpServers": {
    "cioport": {
      "command": "node",
      "args": [
        "<repo>/mcp/src/index.ts",
        "--holdings", "<path>/cioport-portfolio.json"
      ]
    }
  }
}

The --holdings flag is optional — without it the five market/world tools work and the two portfolio tools explain what's missing. To enable them, export your portfolio from the app (portfolio → Export) and pass the file's path. The file is re-read on every question, so a fresh export is picked up without restarting anything.

What it can — and cannot — reach

It reads only CIOport's public snapshot plane. A built-in origin guard refuses any request to any other host — vendors, third parties, telemetry, anything.
Signed-in data (quotes, news) is not accessible — the connector runs anonymous by construction, exactly like the signed-out app.
Your portfolio file never leaves your machine; the join between world events and your holdings runs locally, in the same compute kernel the app uses.
Snapshot authenticity: the same signed-manifest verification the app performs runs in the connector before anything is computed.