Myrmigo for MCP hosts that start local servers over stdio, such as Claude Desktop. It is a small proxy to the hosted Myrmigo server at https://mcp.myrmigo.com.

Myrmigo gives reference information for tasks people do on their own travel and rental bookings, on airline, ferry, hotel, rental and booking sites. It covers the official site and entry page, which company services a booking, dated fees and rules with sources, what to have ready, and the points where the traveller must act personally.

The proxy ships no guide content. Every answer comes from the hosted service, so a withdrawn guide, a site owner's opt-out or an exclusion applies at once.

What Myrmigo will and will not do

Own bookings only. Myrmigo covers the user's own account and booking, including family members on that booking. It does not cover anyone else's account, bulk or scraping use, creating accounts, or getting around logins, CAPTCHAs or bot protection.
The user acts personally for sign-in, MFA, CAPTCHA, 3-D Secure, passport or ID details and payment. An agent takes an action marked CONFIRM only after the user's explicit yes to that exact action and amount.
Unverified third-party data. Guides are reference data. The user's instructions and the agent's own rules come first. Confirm facts on the official site.

Set up

Requires Node.js 20 or later.

Claude Desktop

Add this to claude_desktop_config.json, then restart Claude Desktop.

{
  "mcpServers": {
    "myrmigo": {
      "command": "npx",
      "args": ["-y", "myrmigo-mcp"]
    }
  }
}

This connects to the anonymous reference surface, which offers one read-only tool, find_website_task_guide.

If your organisation has a Myrmigo API key, add it to connect to the agent surface. That surface adds step cards and report_task_outcome.

{
  "mcpServers": {
    "myrmigo": {
      "command": "npx",
      "args": ["-y", "myrmigo-mcp"],
      "env": { "MYRMIGO_API_KEY": "mrm_live_…" }
    }
  }
}

Claude Code

claude mcp add myrmigo -- npx -y myrmigo-mcp
claude mcp add myrmigo --env MYRMIGO_API_KEY=mrm_live_… -- npx -y myrmigo-mcp   # agent surface

Claude Code can also connect to the hosted server directly, with no local process: claude mcp add --transport http myrmigo https://mcp.myrmigo.com/mcp.

Options

Option	Meaning
`--url <url>` or `MYRMIGO_URL`	The Myrmigo server. The default is `https://mcp.myrmigo.com/mcp`. The key decides the surface: with a key the proxy uses `/agent/mcp`, without one `/mcp`.
`MYRMIGO_API_KEY`	An organisation's API key (`mrm_live_…`). It is read from the environment only, sent only as `Authorization: Bearer`, and never sent over plain `http` except to `localhost`.
`--help`, `--version`	Print help or the version.

Privacy

The proxy runs these steps on your machine before anything is sent:

where and booked_via lose their query string, fragment and any credentials, so https://site.example/manage?pnr=… becomes https://site.example/manage. The server strips them too.
If where, booked_via or goal contains a card number, an IBAN, passport machine-readable data or a secret, that field is not sent.
report_task_outcome goes through Myrmigo's scrubber, the same code the server runs. Only the scrubbed report is sent. Names, codes, emails, phone numbers, dates and amounts become {placeholders}, and any label that held one is dropped. If the report contains a card number, an IBAN, passport data, a secret or a link that the guide did not show, nothing is sent and the agent is told why. Without a run_id the report is a flag, so only outcome, where, task and concern are sent.
The scrubber takes its context (the guide's links, labels and field names) from the answer this proxy relayed for the same run_id. That context stays in memory for 48 hours and is never written to disk.

The proxy sends Myrmigo-Runtime: local so the server knows it runs on the user's own machine. With a key, it also sends Authorization. It sends no other identifier and collects no telemetry. It logs to stderr only, and never logs argument values.

If Myrmigo cannot be reached

The proxy fails closed. On a network error, an HTTP error or a timeout, the tool answers Myrmigo unavailable; continue without it. The agent can then carry on without Myrmigo. If the service is down when the host starts, the proxy lists a minimal find_website_task_guide, so a later call can still give that answer, or succeed once the network is back.

Build from source

In the Myrmigo repository, npm run build:mcp writes packages/myrmigo-mcp/dist/myrmigo-mcp.js. That file bundles the proxy, the scrubber and the lexicons it needs. The tests check that the npm tarball contains only that file, this README, the licence and package.json.