Connect
CLI
For terminal agents like Claude Code and Codex, the CLI is easiest. Install in one line, log in, and Yumi auto-registers as an MCP server — verified venue data, right in your shell.
@heyyumi/cli isn't live yet. The steps below are a preview of how connecting will work once it ships. To use the same data today, call the REST API.
No API key to paste. Just a heyyumi account and a one-time login the CLI keeps securely.
Create an account →Install → log in → register
Install, log in, then run mcp install — and Yumi attaches as an MCP server to terminal agents like Claude Code and Codex.
terminal
# install & log in npm i -g @heyyumi/cli heyyumi login # register as an MCP server (Claude Code, Codex, ...) heyyumi mcp install
* On login the CLI stores your token locally. No API key in your source or env vars.
Install
One npm line installs it globally. Node 18+ and you're set.
Log in
heyyumi login → authenticate in the browser. The CLI keeps the token safely.
Register MCP
heyyumi mcp install → Yumi auto-registers as an MCP server for your terminal agent.
What happens once you connect?
Every time your agent calls a Yumi tool, it spends tokens — richer data costs more. During Open Season personal, conversational use is free — up to 70 tokens a day. Only commercial use inside a company product or service falls under a separate license.
Using this at a company? Talk to us →Why the CLI
Built for terminal agents
For shell-based agents like Claude Code and Codex, a one-line install beats hand-editing config files.
No key in your code
The CLI holds your login token, so your API key never lands in source or env vars.
Auto-connects via MCP
One install registers it as an MCP server — you get MCP's context calls and per-tool pricing for free.