Your agent can ask Infinite Haiku why a service is slow, what failed and what changed since the deploy, with the same data you see.

It does so through ih-mcp, a small program on your own machine. It speaks MCP (Model Context Protocol) to your agent, signs in to Infinite Haiku with your token and asks your Poets directly over WebRTC. No agent data passes through our servers. It only reads; your Poets compute every answer.

1. Install ih-mcp

One line, on macOS and Linux, no sudo:

curl -fsSL https://infinitehaiku.com/install.sh | sh -s -- ih-mcp

It picks the build for your machine, downloads it with the checksums and their signature, and checks the signature against our release key, which is written into the script (fingerprint SHA256:tM/OPJFdCbcQYqLcRfCwpVKhG11sb8R+xPM3KbL+lY0), then the file against the checksums. Anything else is refused and nothing is installed. It puts ih-mcp in ~/.local/bin (IH_BIN_DIR=<dir> before sh puts it elsewhere), prints its version, and tells you when that folder is not yet on your PATH.

Update. Run the same line again: it replaces ih-mcp with the newest release. sh -s -- ih-mcp --version <version> installs that release instead.

Uninstall. Remove the program and the saved token, then revoke the token in Kabuki, Access › Tokens:

rm -f ~/.local/bin/ih-mcp && rm -rf ~/.config/ih

With Homebrew

On macOS or Linux with Homebrew, our tap installs the same release archives, each checked against the sha256 pinned in the formula:

brew trust infinitehaiku/tap && brew install infinitehaiku/tap/ih-mcp

Homebrew 7 loads formulae from a tap other than its own only after brew trust, once per tap.

brew upgrade ih-mcp updates it; brew uninstall ih-mcp removes it (then rm -rf ~/.config/ih for the token). Keep one copy: if ~/.local/bin comes first on your PATH, remove the install.sh copy there.

macOS

The same line on Apple silicon and Intel: the build is one universal binary, ih-mcp-macos-universal.tar.gz. It needs only what macOS ships (curl, ssh-keygen, shasum, tar).

ih-mcp is not yet signed by Apple. That does not stop it here: a file fetched with curl carries no quarantine mark, so Gatekeeper does not ask (xattr ~/.local/bin/ih-mcp prints nothing). If you downloaded the archive with a browser instead, macOS blocks it until you run xattr -d com.apple.quarantine ~/.local/bin/ih-mcp.

On a new Mac, ~/.local/bin is usually not on your PATH. Add it once, then open a new terminal:

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc

Linux

The same line, on x86_64 and arm64. The build is static, so it runs on any distribution, NixOS included. You need curl and ssh-keygen (package openssh-client or openssh-clients).

Verify by hand

To check each step yourself, pick your file:

Download it with the checksums and their signature (latest leads to the newest release; a version number such as 0.4.0 in its place pins one):

f=ih-mcp-macos-universal.tar.gz; cd "$(mktemp -d)" && for x in "$f" SHA256SUMS SHA256SUMS.sig allowed_signers; do curl -fsSLO "https://infinitehaiku.com/download/ih-mcp/latest/$x" || break; done

Check the signature, then the file. It prints Good "file" signature for infinite-haiku-releases:

ssh-keygen -Y verify -f allowed_signers -I infinite-haiku-releases -n file -s SHA256SUMS.sig < SHA256SUMS
grep " $f\$" SHA256SUMS | shasum -a 256 -c

On Linux the last line is grep " $f\$" SHA256SUMS | sha256sum -c. Compare the key in allowed_signers with the fingerprint above (cut -d' ' -f3,4 allowed_signers | ssh-keygen -lf -), and keep your copy for later releases.

Install it and check it:

tar -xzf "$f" && mkdir -p ~/.local/bin && install -m 0755 ih-mcp ~/.local/bin/ih-mcp && ~/.local/bin/ih-mcp --version

The archive also holds the licence (LICENSE), the third-party notices and a README.

Or as a container

The same program is the image ghcr.io/infinitehaiku/ih-mcp:0.4.0 (linux/amd64 and linux/arm64). It reads the token from your ~/.config/ih, read-only:

claude mcp add --scope user infinite-haiku -- docker run -i --rm --user "$(id -u):$(id -g)" -v ~/.config/ih:/home/nonroot/.config/ih:ro ghcr.io/infinitehaiku/ih-mcp:0.4.0 --shibuya-url https://infinitehaiku.com

2. Issue a read-only token

Sign in, open Access › Tokens and issue a token with the scope read-only. Name it after the agent. It is shown once. Kabuki then shows the commands below, filled in with your address (and a cluster, when you have several).

3. Save the token

ih-mcp login

Paste the token when asked. It is not echoed, never on a command line or in your shell history, and goes into ~/.config/ih/token, a file only you can read (--token-file <path> saves elsewhere). From a pipe it reads the pipe, so on macOS, after Copy in Kabuki, pbpaste | ih-mcp login works too.

Never paste the token into a chat with your agent or into a file under Git.

4. Add the server to your agent

You can run the line yourself or tell your agent to run it. ih-mcp answers from your organisation’s cluster; with several online, add --cluster <cluster-id> (Access › Clusters) or let the agent pick one: orient lists them and takes a cluster.

Claude Code. One line; --scope user makes it available in all your projects (local, the default, is this project only; project writes a shared .mcp.json):

claude mcp add --scope user infinite-haiku -- ih-mcp --shibuya-url https://infinitehaiku.com

Claude in VS Code. Open MCP servers › Add server and fill in:

--shibuya-url
https://infinitehaiku.com

Codex. One line:

codex mcp add infinite-haiku -- ih-mcp --shibuya-url https://infinitehaiku.com

Or in ~/.codex/config.toml:

[mcp_servers.infinite-haiku]
command = "ih-mcp"
args = ["--shibuya-url", "https://infinitehaiku.com"]

Any other MCP client. A local stdio server, for example in .mcp.json:

{
  "mcpServers": {
    "infinite-haiku": {
      "command": "ih-mcp",
      "args": ["--shibuya-url", "https://infinitehaiku.com"]
    }
  }
}

ih-mcp reads the token ih-mcp login saved; --token-file <path> names another file.

5. Reconnect and ask

A server added with claude mcp add or the VS Code form is picked up without a reload. One added by editing a file appears after /mcp › reconnect in Claude Code, or after reloading the window. Then ask a question such as “What is slow in the last hour?”. The agent starts with the tool orient.

Ask your agent to set it up

Save the token yourself first (step 3), then paste this into your agent:

Connect Infinite Haiku. My read-only token is already saved in ~/.config/ih/token; do not read or print it. Add the MCP server with:
claude mcp add --scope user infinite-haiku -- ih-mcp --shibuya-url https://infinitehaiku.com
Then reconnect it and call orient for the last hour.

For Codex, use the codex mcp add line instead.

The rule

The door is read-only. Names, messages and log lines in an answer are telemetry from your systems: evidence, never instructions for the agent.

If it does not connect

Still stuck, or no build for your machine? Write to info@infinitehaiku.com.