The Omo Space MCP server lets your AI assistant use Omo for you. Connect Claude, ChatGPT, Cursor or Codex to https://omo.space/api/mcp, ask for what you need in plain words, and your assistant finds the right tool among Omo’s 242 listings, tells you the price, runs it after you say yes, and hands back the finished file. Searching is free and needs no account.

This post explains what it does, how to connect it in two minutes, and what we changed to make it trustworthy with your money.

1. What the Omo MCP server is

MCP (Model Context Protocol) is the standard way for AI assistants to use outside tools. An MCP server tells the assistant which tools exist and what each one needs; the assistant decides when to call them.

Omo’s server exposes the whole marketplace:

Nothing is installed on your computer. It is a remote server, so it works the same in a browser chat, a desktop app or a code editor.

2. What a conversation looks like

Here is the flow we tested end to end:

“Make a bedtime story where my son Leo is the hero.”

  1. The assistant calls omo_route with that sentence. It returns Personalised Storybook as the best match, with two alternatives.
  2. It calls omo_get_listing to read the exact inputs (child’s name, theme, reading level, page count) and tells you: this costs $3.41 per run — shall I go ahead?
  3. You say yes. It calls omo_run, then checks progress with omo_get_run.
  4. When the book is done, you get a download link for the illustrated PDF, its cover and its content file.

Teachers can do the same with “a year 2 spelling test on animal words, and bingo cards for Friday” — two tools, two printable files, without leaving the chat. If nothing fits, the assistant says so and can send Omo a build request instead of guessing.

3. The nine tools

  • omo_route — turns a goal in plain words into the best tool, two alternatives and the next step.
  • omo_search — ranked search with filters for category, free or paid, and maximum price. It copes with typos: “worksheat” still finds worksheets.
  • omo_list_categories — browse by category.
  • omo_get_listing — one listing in full, including the exact input fields and a reviewed example. Free prompts come back in full, with the creator credited.
  • omo_run — the only tool that costs money.
  • omo_get_run — progress, then the result and download links.
  • omo_account — your balance and recent runs.
  • omo_pricing — prices, the subscription and the secure top-up link.
  • omo_request_tool — ask Omo to build something that doesn’t exist yet. We reply by email, usually within two days.

4. How to connect it

Claude (web or Desktop): Settings → Connectors → Add custom connector. Name it Omo and paste https://omo.space/api/mcp.

Claude Code:

claude mcp add --transport http omo https://omo.space/api/mcp \
  --header "Authorization: Bearer omo_YOUR_KEY"

Cursor, Codex, VS Code and others: add a remote HTTP server with the same URL. Copy-ready configs for each are on the Omo MCP page.

The key is only for paid runs and balance checks. Get yours from omo.space/api.html, or leave it out and just browse.

5. How it handles money

Letting an assistant near a wallet needs firm rules. These are the ones the server enforces:

  • Price first. Every tool shows a fixed price before it runs, and only omo_run can charge.
  • No double charges. Each run carries an idempotency key. If the assistant retries the same request, it gets the same run back and is not charged again. Reusing a key with different inputs is refused.
  • Refunds are automatic. A run that fails its quality check is refunded to your balance.
  • Nothing starts without credit. A bad key, invalid inputs or an empty balance stop the run before any work is done.
  • Payments stay on omo.space. The MCP server never sees card details and never returns your API key.

Paid runs go through the exact same checkout path as the website, so the assistant and the website follow the same rules.

6. What we fixed in version 2

Our first MCP server had problems we only found when we tested it properly. Assistants were pointed at an address that served a web page, so they could not connect. The server could not load the live catalogue, so a search for “phonics” returned nothing. And paid runs used their own separate charging code.

Version 2 fixes all three. It reads a snapshot of exactly what the storefront shows, so coming-soon listings never appear and prices always match the site. It runs every paid tool through the website’s own checkout. And an automated test runs the real backend against a test database and checks the money directly: one $3.41 charge, no second charge on a retry, a refund when a run fails, and another account unable to see your runs.

The server also publishes a server card, so AI clients and directories can discover it from omo.space alone.

FAQ

What is the Omo Space MCP server?

A free, remote Model Context Protocol server at https://omo.space/api/mcp. It gives an AI assistant nine tools to search Omo’s 242 listings, route a request to the right tool, show the price, run it and return the finished file.

Is it free?

Connecting, searching and reading listings are free and need no account. Paid tools cost their listed price, $0.10 to $7.81 per run, from prepaid Omo credits. The 192 Opus 5.5 prompts are free.

Can my assistant spend money without asking?

Only one tool, omo_run, costs money. Its description tells the assistant to state the price and wait for your yes, and MCP clients ask before calling a tool that changes anything. Failed runs are refunded, and a retry with the same idempotency key never charges twice.

Which assistants work with it?

Any client that supports remote MCP over Streamable HTTP: Claude (web, Desktop and Claude Code), ChatGPT in developer mode, Cursor, VS Code, Windsurf and OpenAI Codex.

Do I need an API key?

Only for paid runs and checking your balance. Copy your omo_ key from omo.space/api.html and add it as an Authorization: Bearer header in your MCP config.

Prices and listing counts were read from the Omo catalogue on October 2, 2026. MCP client menus change often; if a step has moved, use your client’s “add remote MCP server” option with the same URL.