theo
mcp

One endpoint. Every agent. Infinite output.

The Theo MCP server hands your AI agent the whole OpenCharts studio — 87 tools for decks, sheets, sites, boards, songs, images, and video. Ask in chat; a real, editable artifact comes back.

Theo MCP
Turn our onboarding doc into a deck.
create_presentationRunning
Q3 onboarding — 12 slides
Editable deck, live in your workspace
Open
87 toolsOne endpointFree on every plan120 requests / minStreamable HTTPNothing to host87 toolsOne endpointFree on every plan120 requests / minStreamable HTTPNothing to host
A chartreuse keycap drifting through soft white clouds
Works with every agent

Anything that holds an MCP config holds your whole studio.

No SDK, no glue code. One hosted Streamable HTTP endpoint means new OpenCharts tools appear on your agent the day they ship.

Warp
Warp
Claude
Claude
Cursor
Cursor
theo
Theo
VS Code
VS Code
Codex
Windsurf
Windsurf
WarpWarpClaudeClaude Desktop / Claude CodeClaude CodeClaude Code (CLI)CursorCursorVS CodeVS Code (GitHub Copilot)Codex (OpenAI)WindsurfWindsurf (Codeium)AmpOpenCodeOpenCode+ any MCP client
The tool universe
87tools your
agent can call

Everything Theo builds in the app, your agent can build over MCP — organized into 14 groups.

5Readable resources
9+Agents, one-block setup
120/minRequests per key
Setup

Connected in three minutes.

Nothing to install, nothing to host. Create a key, hand your agent one block of config, and the whole studio is on its tool belt.

Set up Warp

  1. 1Open Warp and go to Settings → MCP Servers.
  2. 2Click "Add Server" or edit the MCP config file directly.
  3. 3Paste the config JSON above, replacing {{YOUR_API_KEY}} with the user's actual API key.
  4. 4Save and restart Warp or reload the MCP configuration.
  5. 5Verify by running the `whoami` tool to confirm authentication.

Skip the config entirely — paste the setup prompt into Warp and it installs the server itself, then verifies with a whoami call.

Warp Settings → MCP Servers (or ~/.warp/mcp.json)
{
  "mcpServers": {
    "opencharts": {
      "type": "http",
      "url": "https://www.opencharts.com/api/mcp",
      "headers": {
        "Authorization": "Bearer {{YOUR_API_KEY}}"
      }
    }
  }
}

Swap {{YOUR_API_KEY}} for the key you created — that's the whole setup.

Fastest paths

npx add-mcp https://www.opencharts.com/api/mcp
claude mcp add --transport http opencharts https://www.opencharts.com/api/mcp --header "Authorization: Bearer {{YOUR_API_KEY}}"
What your agent ships

Not answers. Deliverables.

MCP calls don't return walls of text — they return living OpenCharts projects. Editable, shareable, and already in your workspace when you open the link. These demos play right here.

OpenCharts presentation builderPresentations

Slides from a sentence

A one-line brief becomes a themed, editable deck — your agent replies with the link to open it.

create_presentation
Theo Sheets spreadsheetTheo Sheets

Live spreadsheets, real formulas

Workbooks built cell by cell — formulas recalculate the moment you open the sheet.

apply_sheet_ops
OpenCharts BoardsBoards

Work filed onto your boards

Cards land on your boards and the board's rules run in the same write, so automations fire instantly.

add_board_card
OpenCharts NotesNotes

A notes hub, written for you

Research, briefs, and specs come back as structured Markdown notes you can edit and share.

create_notes
Theo Agents designerTheo Agents

Agents that run the repeat work

Dispatch a Theo Agent that runs in the background and reports back when the job is done.

run_agent
Code Canvas building a siteCode Canvas

Sites shipped to a live preview

Real files, real edits — every change lands on the project's live preview URL.

update_code_project
How it feels

Your agent asks. Theo ships.

From a chat message to an editable artifact in four moves — no context-switching, no copy-paste, no dead ends.

1
Free on every plan

Mint a scoped key

Create a read · write · ai key in the Developers hub. Rotate or revoke it any time.

2
One block, no SDK

Paste one block of config

Drop the endpoint into your agent — or hand it the setup prompt and it wires itself.

3
Plain English

Ask for real work

“Build a flowchart of our onboarding.” The right tool runs against your workspace.

4
Editable, shareable

An artifact link comes back

Not a wall of text — a living OpenCharts project, open in the editor and ready to ship.

Build a flowchart of our onboarding
create_flowchart

Onboarding Flow

Flowchart · opens in the editor

Open
The tool universe

87 tools. One universe.

Everything Theo builds in the app, organized into 14 groups. Tap a group to see every tool inside it.

Plus 5 ambient resources your agent can read for context:

projectsprojecttemplatescanvasescanvas
Built for developers

Scoped keys. Real guardrails.

Agents get exactly the access you grant — nothing more. Every key is scoped, every call is logged, and everything can be revoked in one click.

read · write · ai scopes

Mint a key per agent with exactly the powers it needs — and revoke it instantly from the Developers hub.

Rate-limited by design

120 requests a minute per key keeps a runaway loop from ever touching your workspace.

An immutable audit log

Status, latency, tokens, and credits for every call — filterable per key in Developer Analytics.

Questions

Everything you need to plug in.

The details developers ask before wiring an agent to the whole OpenCharts studio.

What is the Theo MCP server?
It's OpenCharts exposed over the Model Context Protocol — an open standard that lets AI agents call tools. One hosted endpoint (https://www.opencharts.com/api/mcp) gives any MCP client 87 tools and 5 readable resources over Streamable HTTP, so your agent can create and edit real OpenCharts projects from chat.
Which agents and apps work with it?
Warp, Claude, Claude Code, Cursor, VS Code, Windsurf, Codex CLI, Amp, and OpenCode all have one-block setups — and any other MCP client that speaks Streamable HTTP works with the same endpoint.
How does authentication work?
Create an API key in the Developers hub and send it as a Bearer token. Keys are scoped (read, write, ai), free to create on every plan, and you can rotate or revoke them instantly.
Do I need to install or host anything?
No. The server is fully hosted — there's nothing to run, update, or deploy. Paste the config block into your agent, or run npx add-mcp with the endpoint URL, and you're connected.
What can my agent actually create?
Flowcharts, whiteboards, notes, presentations, spreadsheets with live formulas, project boards, page designs, visual canvases, songs, images, video, and full code projects with live preview URLs — every artifact lands in your OpenCharts workspace, editable and shareable.
Is the MCP included in my plan?
Yes — MCP access is available on every plan, including Free. AI-powered tools spend the same Theo credits they would in the app, and non-AI tools (projects, boards, sheets) don't cost credits at all.
What are the rate limits?
120 requests per minute per key. Heavier renders like video and songs run as background jobs — your agent gets a job id back immediately and polls a status tool until the result is ready.
Can agents read my existing work?
Read-scoped tools can list and open your own projects, read sheet ranges, board cards, and canvases — always scoped to the account that owns the key. Nothing outside your workspace is ever visible.
How do images and video come back to the agent?
generate_image returns a hosted image URL synchronously. generate_video starts a background job; get_video_status reports progress and returns the final URL, ready to embed anywhere.
Where can I see what my key has been doing?
Developer Analytics logs every API and MCP call — which tool ran, its status, latency, tokens, and credits — with an immutable per-call audit trail you can filter by key.
Soft clouds drifting across a bright sky

One endpoint. Every agent. Infinite output.

Give your agent the whole OpenCharts studio in about three minutes. Free on every plan, nothing to host.