otto
Enables AI agents to operate a local financial terminal, including market data, backtesting, paper portfolio management, and news digest, through safe, gated tools over MCP.
README
Otto
An effortless, local, AI-operated financial terminal. You say what you want in plain language; an AI agent drives the terminal for you — pulling market data, running backtests, managing a paper portfolio, digesting news, and more. Everything runs on your machine.
Otto is built to be operated by an AI rather than clicked by hand: the whole product is exposed as a safe, machine-operable tool surface over MCP, so a coding agent (Claude Code / Codex) can run it end to end while a human watches the dashboard.

Highlights
- Single-process local app — a FastAPI backend serves both the JSON API and the built
React UI at
http://127.0.0.1:8765/. - AI operator surface — a standard-library-only MCP
server (
src/local_terminal/mcp_server.py) exposes routes and gated actions as tools. - Safety-gated by design — live trading, credential entry, and code execution are off by default and refuse loudly; the default runtime is read-only / paper / dry-run.
- Public, no-key market data where available (crypto, equities, FX, macro), with an optional local key vault for free-tier providers (Finnhub / FRED / Twelve Data).
- Workbenches — Markets, Crypto, Portfolio (create / import / export / demo), Backtest, News digest, Algo scan, and an AI-chat research surface over local artifacts.
- ~460 tests covering the contract, safety gates, providers, and UI end-to-end.
Screenshots
Multi-asset markets board (crypto, US/TW equities, FX) and the live crypto workbench — public, no-key data where available; live trading and code execution stay gated off:
| Markets | Crypto |
|---|---|
![]() |
![]() |
Run
Single-process self-use (serves the built UI + API at http://127.0.0.1:8765/):
# Windows
.\.venv\Scripts\python.exe -m src.local_terminal
# macOS / Linux
python -m src.local_terminal
Build the frontend once (or after UI changes):
npm --prefix frontend install && npm --prefix frontend run build
Developer hot-reload UI stays available via npm --prefix frontend run dev (proxies /api
to the backend).
AI operation
Otto is driven by plain-language commands: you tell the agent what you want, and it operates
the terminal through the MCP tool surface (python -m src.local_terminal.mcp_server,
registered in .mcp.json). See docs/AI_OPERATOR_GUIDE.md.
Live trading, credential entry, and disabled runtimes stay gated behind explicit contracts.
Architecture
src/local_terminal/— FastAPI backend: routes, action contract, provider adapters, safety/secret gates, local state storage, and the MCP operator server.frontend/— React + Vite single-page UI, served static in production.tests/— pytest suite (contract, gates, providers) plus Playwright e2e.docs/— the AI operator guide, architecture notes, and the planning/audit ledger.
Clean-room note
Otto is a clean-room reimplementation: it was built by observing a reference
terminal's workflow and shape, never by reading, copying, porting, or adapting its code or
assets. Implementation independence is enforced, not just claimed —
AGENTS.md defines the source wall and
tests/test_clean_room_source_wall.py fails the
build if product runtime surfaces reference the observed source or leak third-party branding.
The private third-party observation notes are intentionally not published, to keep the
clean-room boundary intact (see docs/reference/). It is not a fork,
crack, asset copy, or continuation of any commercial product; branding, commercial
mechanics, and unsafe execution paths are replaced with local equivalents.
Safety model
Out of scope unless a later, separately reviewed safety contract explicitly permits it:
- Third-party branding, logos, trademarks, commercial copy, subscriptions, billing.
- Reachable real orders, private API-key order flows, real balance reads, margin, leverage, short exposure, or derivatives live execution.
The default build is paper / dry-run / read-only.
Testing
python -m pytest -q # ~460 tests
python -m ruff check .
License
MIT.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

