okama MCP
okama-mcp

MCP (Model Context Protocol) server that exposes the okama investment portfolio toolkit to AI assistants — Claude Desktop, Claude Code, Cursor, Codex, and any other MCP-compatible client.
With okama-mcp installed, you can ask an AI things like:
"Backtest a portfolio of 30% gold and 70% real estate over the last 15 years."
"Run a Monte Carlo retirement forecast on that portfolio, withdrawing $1,000/month indexed to inflation, over 25 years."
"What's the tangency portfolio of SPY, BND, and GLD with a 3% risk-free rate?"
…and the AI uses the MCP tools to call okama directly — no Python code needed.
Built on FastMCP. Single codebase, two transports:
stdio (for local clients) and streamable-http (for self-hosting).
okama-mcp is free and open source — no hosted service, no registration; you run it
yourself, locally or on your own server.
Install
Requires Python ≥ 3.11 (same floor as okama itself); okama ≥ 2.2.0 is installed automatically.
The easiest way — no clone, no venv — is uv or pipx:
uvx okama-mcp stdio # run straight from PyPI
# or
pipx install okama-mcpPlain pip works too:
pip install okama-mcpWith pip, prefer a dedicated virtual environment: on most modern Linux distros the
system Python is marked externally managed (PEP 668), so pip install outside a venv
fails, and a shared environment risks dependency conflicts. In your MCP client config,
point command at the absolute path of the okama-mcp script inside the venv — GUI
clients don't see your shell PATH. uvx and pipx avoid all of this by isolating
the install automatically.
To work on the code, install from source instead:
git clone https://github.com/mbk-dev/okama-mcp
cd okama-mcp
poetry installRelated MCP server: ctrader-mcp-server
Run
# stdio — for Claude Desktop, Claude Code, Cursor (local IPC)
okama-mcp stdio
# streamable HTTP — for self-hosting on your own server
okama-mcp http --host 127.0.0.1 --port 8765When running from a source checkout, prefix each command with poetry run.
Connect a client
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or
%APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"okama": {
"command": "uvx",
"args": ["okama-mcp", "stdio"]
}
}
}Restart Claude Desktop; the server appears in the tools menu.
Claude Code
To make the server available in every project (works from any directory):
claude mcp add --scope user okama -- uvx okama-mcp stdioDevelopers running from a source checkout can use claude mcp add okama -- poetry run okama-mcp stdio from the project root instead.
Or commit a .mcp.json at the project root so the whole team picks it up:
{
"mcpServers": {
"okama": {
"command": "uvx",
"args": ["okama-mcp", "stdio"]
}
}
}Cursor
Add the server to .cursor/mcp.json in your project (or ~/.cursor/mcp.json to make
it global):
{
"mcpServers": {
"okama": {
"command": "uvx",
"args": ["okama-mcp", "stdio"]
}
}
}Codex (CLI & Desktop)
Add the server with one command:
codex mcp add okama -- uvx okama-mcp stdioOr declare it in ~/.codex/config.toml (or a project-scoped .codex/config.toml
in trusted projects):
[mcp_servers.okama]
command = "uvx"
args = ["okama-mcp", "stdio"]The Codex CLI, desktop app, and IDE extension share this configuration — set it up once and it works in all three.
Self-hosting (streamable HTTP)
Run okama-mcp on your own server and share it across your MCP clients:
okama-mcp http --host 127.0.0.1 --port 8765 --path /mcp(From source: poetry run okama-mcp http ...)
Then point your MCP client at http://<your-server>:8765/mcp. For a production
setup put nginx + TLS in front; ready-made examples live in deploy/:
deploy/systemd/okama-mcp.service— systemd unit (hardened, runs as a dedicated user)deploy/nginx/self-hosted.conf— nginx vhost: TLS, SSE-friendly proxying of/mcp
The server is open by design — free to run, no registration. If your instance must not be public, restrict access at the nginx level (allow-list, VPN, or HTTP basic auth).
Tool catalog
A Monte Carlo retirement forecast (30% gold / 70% real estate, withdrawing $1,000/month indexed to inflation over 25 years) and the efficient frontier of SPY/BND/GLD — the exact examples from the top of this page:


All tools are stateless — pass the full portfolio specification with every call.
The server caches expensive okama objects (Portfolio, EfficientFrontier) by content
hash, so repeated calls on the same spec are fast.
Nested portfolios. Wherever a list of assets is accepted — the assets field of
PortfolioSpec/FrontierSpec, or the portfolios argument on the comparison tools —
an entry may be a ticker string or a nested portfolio object (the same spec shape).
This lets you treat a whole portfolio as a single component: e.g. compare a 60/40
portfolio against gold, or put a sub-portfolio on the efficient frontier.
Search & metadata
Tool | Purpose |
| Free-text search across all okama symbols by name / ticker / ISIN. |
| Show the available okama namespaces. |
| Metadata for one symbol — name, country, currency, type, date range. |
Single asset & comparisons
Tool | Purpose |
| Time series for one asset. |
| Side-by-side statistics ( |
| Correlation matrix of monthly returns. |
| Rolling annualized risk per asset. |
| Return metrics per asset: CAGR, cumulative return, mean / real mean return, monthly geometric mean, annual returns table. |
| Rolling CAGR and rolling cumulative return per asset. |
| Beta, correlation, annualized tracking difference and tracking error of each asset vs a benchmark/index. |
| LTM dividend yield, 5y mean yield, paying/growing streaks per asset. |
Portfolio backtest
Tool | Purpose |
| Headline metrics (CAGR, annual mean/risk, Sharpe, Sortino) + full |
| Drawdown time series + max drawdown / recovery period. |
| Historical Value at Risk and CVaR. |
| Wealth-index series (cumulative growth of 1000). |
| Rolling CAGR time series (optionally inflation-adjusted). |
| Historical probability of CAGR below a target (e.g. of a loss) over N-year periods. |
Monte Carlo DCF
Tool | Purpose |
| Forward simulation with one of five cash-flow strategies ( |
| Historical money-weighted return (IRR) for a contribution/withdrawal plan. |
| Largest sustainable withdrawal (Monte Carlo) for a |
| Monte Carlo distribution of future cash flows over time (percentile bands). |
The mc argument accepts distribution_parameters to override the fitted distribution (e.g. a fixed Student-t df); see the MCSpec shape below.
Distribution diagnostics
Tool | Purpose |
| Goodness-of-fit for the return distribution: fitted parameters, Jarque-Bera, Kolmogorov-Smirnov (chosen + all distributions), and backtesting error (theoretical vs empirical mean/VaR/CVaR). |
| Skewness & kurtosis time series — expanding, or rolling when a window (months) is given. |
| Degrees of freedom for a Student-t that best matches empirical VaR/CVaR. |
| Simulated CAGR at each percentile, plus the probability of a CAGR at/below |
DCF (historical cash-flow analysis)
Tool | Purpose |
| Historical wealth index with the cash-flow plan (FV nominal or PV discounted). |
| Historical contribution/withdrawal time series (FV or PV). |
| Historical wealth index for the portfolio and each underlying asset. |
| Historical longevity: survival period (years) and depletion date. |
| Present value (PV) and future value (FV) of the initial investment. |
Efficient Frontier
Tool | Purpose |
| Full EF point table (Risk / Mean return / CAGR + per-asset weights). |
| Max-Sharpe portfolio on the EF. |
| Global Minimum Variance portfolio. |
| Most Diversified Portfolio (maximises the diversification ratio) on the EF. |
Macro
Tool | Purpose |
| Inflation series for a currency ( |
| Central-bank policy rate ( |
| Macro indicator from the RATIO namespace (e.g. |
Charts
Each tool renders a PNG (default 1500×900) and returns it as MCP image content —
clients like Claude Desktop display it inline. Every chart tool also accepts
optional width / height (pixels, 300–4000) for custom sizes and aspect ratios,
and an optional save_path — the chart is then also written to that file and the
path reported back. Use save_path in clients that don't render MCP images in
their UI (e.g. Claude Code's terminal): ask for a chart "saved to /tmp/chart.png"
and open the file reference. Note: in self-hosted (streamable-http) deployments
save_path is written on the server's filesystem, not the client's machine.
Tool | Chart |
| Portfolio wealth index (+ inflation line). |
| Drawdown depth over time. |
| Monte Carlo forecast fan (percentile bands). |
| Histogram of IRR across Monte Carlo scenarios (percentile markers). |
| Q-Q plot of historical returns against the fitted distribution (norm/lognorm/t). |
| Histogram of historical returns with the fitted distribution PDF overlaid. |
| EF curve with individual asset points. |
| Transition map: asset weights along the efficient frontier (x-axis = risk or CAGR). |
| Wealth-index comparison of individual assets. |
| Line chart of inflation / central-bank rate / CAPE10 series. Overlay multiple symbols (e.g. |
Spec shapes
The complex tools take typed dicts validated by pydantic. The full schemas live in
src/okama_mcp/schemas.py; here are the headline shapes:
// PortfolioSpec
{
"assets": ["GLD.US", "VNQ.US"], // each entry: a ticker OR a nested PortfolioSpec
"weights": [0.3, 0.7], // optional, must sum to 1.0
"ccy": "USD",
"first_date": "2010-01",
"last_date": "2024-12",
"rebalancing_strategy": { // mirrors okama.Rebalance
"period": "year", // month | quarter | half-year | year | none
"abs_deviation": 0.05, // optional, |actual - target| threshold, 0 < x <= 1
"rel_deviation": 0.1 // optional, |actual / target - 1| threshold, > 0
},
"inflation": true
}
// MCSpec
{
"distribution": "norm", // norm | lognorm | t
"period_years": 25,
"scenarios": 500, // ≥ 1, no upper limit
"percentiles": [5, 50, 95],
"random_seed": 42, // optional, for reproducibility
"distribution_parameters": null // optional; null = fit from history (MLE). Lengths: norm [mu, sigma]; lognorm/t [shape|df, loc, scale]. Any element null = fit that one (e.g. [4, null, null])
}
// CashflowSpec — discriminated by `type`
{ "type": "indexation", "initial_investment": 1000000, "frequency": "month", "amount": -1000, "indexation": "inflation" }
{ "type": "percentage", "initial_investment": 1000000, "frequency": "year", "percentage": -0.04 }
{ "type": "time_series", "initial_investment": 100000, "events": { "2030-06": -50000 }, "time_series_discounted_values": false }
{ "type": "vanguard", "initial_investment": 1000000, "percentage": -0.04, "floor_ceiling": [-0.025, 0.05], "indexation": "inflation" }
{ "type": "cut_if_drawdown", "initial_investment": 1000000, "frequency": "year", "amount": -60000, "indexation": "inflation",
"crash_threshold_reduction": [[0.2, 0.4], [0.5, 1.0]] }
// FrontierSpec
{
"assets": ["SPY.US", "BND.US", "GLD.US"],
"ccy": "USD",
"bounds": [[0.0, 0.7], [0.1, 1.0], [0.0, 0.3]], // optional
"n_points": 20,
"rebalancing_strategy": { "period": "year" },
"inflation": false
}
// Nesting — a portfolio used as a single component (works in PortfolioSpec /
// FrontierSpec `assets`, and the `portfolios` argument of the comparison tools):
{
"assets": [
"GLD.US",
{ "assets": ["SPY.US", "AGG.US"], "weights": [0.6, 0.4], "symbol": "bench6040.PF" }
],
"weights": [0.3, 0.7] // one weight per top-level entry
}Development
The project follows TDD (see AGENTS.md). After every code change run:
poetry run pytest -q
poetry run ruff check .To run the live-API integration test (hits api.okama.io):
poetry run pytest -m integrationProject layout
src/okama_mcp/
├── server.py # FastMCP instance + registration entry point
├── transport.py # CLI: `okama-mcp stdio | http`
├── schemas.py # PortfolioSpec, MCSpec, CashflowSpec, FrontierSpec
├── cache.py # TTL+LRU cache keyed by sha256 of canonical spec
├── serialization.py # pandas → JSON-safe with smart truncation
├── errors.py # Translate okama exceptions to actionable MCP errors
└── tools/
├── search.py, asset.py, asset_list.py
├── portfolio.py, monte_carlo.py
├── frontier.py, macro.py
└── plots.pyLicense
MIT — same license as okama itself.
This server cannot be installed
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mbk-dev/okama-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server