# Myrmigo

> A shared trail map for AI agents. Before an agent changes a booking, checks you in or asks for a refund, it asks Myrmigo how that task is done on that site. It gets back the official page, what you’ll need and exactly where you take over. Where the site’s terms allow it, it also gets the steps and the traps to avoid.

Myrmigo is in private beta, opening soon, and the read-only reference server below is open to anyone now. The first trails are travel in Europe: ferries and airlines. Myrmigo is built by a small team in Greece. Say meer-MEE-go, from Greek μυρμήγκι, “ant”.

## Connect

The hosted MCP server is live. It is the reference surface: anonymous (no sign-up, no API key) and read-only, with three tools: `check_booking_change_cancel_refund` (change, cancellation and refund rules for the traveller’s own booking), `find_official_booking_site` (a travel company’s official booking site, for a new booking) and `check_flight_compensation` (an EU261/UK261 flight compensation check; not legal advice). It stores nothing about you.

- MCP server (Streamable HTTP): https://mcp.myrmigo.com/mcp
- Claude (claude.ai and Claude Desktop): open https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Myrmigo&connectorUrl=https%3A%2F%2Fmcp.myrmigo.com%2Fmcp to get the Add custom connector form filled in, then confirm. Or add it yourself: Customize → Connectors → + → Add custom connector, then paste https://mcp.myrmigo.com/mcp. Team and Enterprise: an Owner adds it first under Organization settings → Connectors → Add → Custom → Web.
- Claude Code: `claude mcp add --transport http --scope user myrmigo https://mcp.myrmigo.com/mcp`
- Cursor (not tested yet; from Cursor’s documentation): add `{ "mcpServers": { "myrmigo": { "url": "https://mcp.myrmigo.com/mcp" } } }` to `~/.cursor/mcp.json`
- VS Code (not tested yet; from VS Code’s documentation): add `{ "servers": { "myrmigo": { "type": "http", "url": "https://mcp.myrmigo.com/mcp" } } }` to `.vscode/mcp.json`
- Apps that only start local (stdio) servers: `npx -y myrmigo-mcp`. The npm package `myrmigo-mcp` is a small proxy to the same server; it needs no key. The npm name `myrmigo` is reserved.
- REST: `POST https://mcp.myrmigo.com/v1/reference` with `{"task":"ferry.change","where":"Blue Star","booked_via":"Ferryhopper"}`
- MCP Registry: `com.myrmigo/myrmigo`
- [Setup for every client](https://myrmigo.com/connect/): Claude, Claude Code and the Claude API. Not tested yet (setup from each app’s documentation): Cursor, VS Code, Gemini CLI, Zed and others

## For developers

- REST (anonymous, JSON): `POST https://mcp.myrmigo.com/v1/reference` with a JSON body: `task` (an id from `GET https://mcp.myrmigo.com/v1/intents`, or a short English phrase), `where` and `booked_via`. Sites: `GET https://mcp.myrmigo.com/v1/sites`. The same answers as the MCP tools `check_booking_change_cancel_refund` and `find_official_booking_site`.
- Answer format myrmigo.route/1: https://mcp.myrmigo.com/v1/schema/route.json (JSON Schema). OpenAPI 3.1: https://mcp.myrmigo.com/openapi.json.
- Flight compensation check (EU261/UK261): `POST https://mcp.myrmigo.com/v1/rights` with the facts of one flight (`flight_date`, `from`, `to`, `carrier`, `event` and, when known, the delay, the notice and the reason); the same as the MCP tool `check_flight_compensation`. Answer format myrmigo.rights/1: https://mcp.myrmigo.com/v1/schema/rights.json. verdict depends means: ask the user the questions in questions, then call again. A descriptive check from dated official sources, not legal advice; the traveller files any claim personally. 10 per minute and 100 per day per network.
- Read best_route, entry_url, site (the company that services the booking), facts, ask_user_first and human_only, and show disclosure to the user whenever it is present. match none with coverage L0 or L1 is a normal answer. For match question, servicing_question or need_site, ask the user question.ask_user, then call again with the chosen option’s task or booked_via (or with where). If the option has no booked_via (another site or travel agent), send the name the user gives as booked_via, or “not sure”. card is text for a model and may change: parse the fields.
- Errors: JSON with `error` (one line with the fix) and a stable `code`; on 429, wait for Retry-After.
- Claude API: the MCP connector (beta header mcp-client-2025-11-20) needs the server in mcp_servers and an mcp_toolset entry in tools.
- Not tested yet (from each vendor’s documentation): the OpenAI Agents SDK (HostedMCPTool, or MCPServerStreamableHttp from your process) and the Responses API mcp tool; LangChain 1.4 (langchain.mcp, beta). Browser Use starts only local (stdio) servers: use `npx -y myrmigo-mcp`.
- [Code for each framework, and REST helpers](https://myrmigo.com/developers/): TypeScript, Python and curl

## What Myrmigo does not do

- It does not book, pay or sign in for anyone. Your agent does the task, in your own session. Myrmigo’s servers never go to the sites on your behalf.
- Payments, passport and ID details, and logins are always entered by the person, never the agent. Before anything paid or irreversible, the agent stops, shows exactly what will happen and waits for a clear yes.
- It covers only tasks people do on their own bookings and accounts. No scraping, and no getting around logins, CAPTCHAs or bot protection.
- It never stores names, booking codes, emails or card numbers.
- Myrmigo is independent and isn’t endorsed by the companies whose sites it describes. Guides always point to each company’s official site.

## Disclosure

Myrmigo’s founder also owns Paros Summer Travellers (paros-summer.com), a vehicle rental company on Paros, Greece, and one of the sites Myrmigo describes. Every answer about that site carries this disclosure, and the same rules apply to it as to any other site.

## Site owners

See how Myrmigo covers your site in the Agent Terms Register: https://mcp.myrmigo.com/register. You can switch guides off for your whole site or a single task, and it takes effect at once:

1. `POST https://mcp.myrmigo.com/v1/owner/claims` with `{"domain":"example.com"}` returns a secret claim token and a DNS TXT record to publish at `_myrmigo.example.com`.
2. `POST https://mcp.myrmigo.com/v1/owner/claims/verify` with `{"domain":"example.com","claim_token":"…"}` checks the record (within 72 hours) and returns an owner token and the site ids it covers.
3. `POST https://mcp.myrmigo.com/v1/owner/disallows` with `{"site":"…","intent":"*"}`, sent with the owner token as `Authorization: Bearer`, switches the guides off.

- [Terms of Use, section 9: Site owners](https://myrmigo.com/terms#site-owners)

## Policies

- [Privacy Policy](https://myrmigo.com/privacy/)
- [Terms of Use](https://myrmigo.com/terms/)
- [security.txt](https://myrmigo.com/.well-known/security.txt): how to report a security problem

## Optional

- [Home page](https://myrmigo.com/): how it works, the guide card, principles and FAQ
- [llms-full.txt](https://myrmigo.com/llms-full.txt): this file plus the text of How it works, Principles and the FAQ