CLI and MCP

What it is

In one line: Ignaru’s MCP server is https://ignaru.com/api/mcp/mcp; connect it with your personal key as a Bearer header and your agent can build canvases, add and enrich leads and draft outreach, while every send waits for a person’s Approve. The quickest setup is the Ignaru skill: npx skills add https://ignaru.com.

Ignaru has three ways in besides the app. A command line, ignaru. An MCP server, so Claude Code, Claude Desktop, Cursor and Codex can work on your canvases. And a small REST API under /api/v1 that both of them use. They all act as you, with your own personal key.

Writing an agent? Read Ignaru for agents (also markdown at /docs/for-agents.md): the first call to make, the rules, how to save calls, and every common job as one MCP tool or CLI command.

Get a key

The quickest way is ignaru login: it shows a code, opens Ignaru, and once you approve, that computer has its own key. For an agent, a script or CI, make one yourself:

1. Open Ignaru and go to Settings, You, API keys.
2. Name it after where it will live, like “Laptop” or “Cursor”, pick all your teams or one, and an expiry.
3. Copy it. It starts with ig_pk_ and is shown once.

A key acts as you. In each team it has the role you have there today, never more, and it stops reaching a team you leave. A key for all your teams picks one with the X-Ignaru-Team header (the CLI sends it after ignaru teams switch). Revoke a key from the same page and it stops working straight away. Keep it out of repositories: put it in the CLI’s config, an environment variable, or your client’s secret store. Older ig_ team tokens keep working in their one team.

Install

The CLI needs Node 18 or newer and has no dependencies. It is not on npm yet. From a checkout of the repository, build it and link it:

npx tsc -p cli
npm i -g ./cli
ignaru login

Once it is published you will be able to run npx ignaru with nothing installed.

ignaru login prints a code, opens ignaru.com/cli/authorize, and waits while you check the code and press Approve. The code lasts 10 minutes and works once. The new key is saved to ~/.config/ignaru/config.json with permissions for you only. To skip the file, set IGNARU_TOKEN or pass --token. To point at another server, use --api or IGNARU_API.

Commands

A <loop> can be the full id, the first few characters of it, or the canvas’s name in quotes. Add --json to any read command for machine-readable output, and --no-color or NO_COLOR=1 for plain text.

A canvas built from the terminal:

ignaru new-loop "Seed-stage founders"
ignaru add-step "Seed-stage founders" signals
ignaru add-step "Seed-stage founders" enrich     --after n_ab12cd34
ignaru add-step "Seed-stage founders" coldemail  --after n_ef56gh78
ignaru add-step "Seed-stage founders" approve    --after n_ij90kl12
ignaru loop "Seed-stage founders"

Each add-step prints the new step’s id, which is what the next one passes to --after.

MCP

The server speaks Streamable HTTP at https://ignaru.com/api/mcp/mcp and takes the same token as a Bearer header. Run ignaru mcp to print these with the address filled in. Without a valid key it answers 401 with WWW-Authenticate: Bearer realm="ignaru", error="invalid_token": create an ig_pk_ key in Settings, API keys. Sign-in with a browser (OAuth) for Claude or Cursor is not offered yet.

Claude Code

claude mcp add --transport http ignaru https://ignaru.com/api/mcp/mcp \
  --header "Authorization: Bearer ig_YOUR_TOKEN"

Claude Desktop

Add this to claude_desktop_config.json (Settings, Developer, Edit Config). It uses the mcp-remote bridge, which needs Node.

{
  "mcpServers": {
    "ignaru": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://ignaru.com/api/mcp/mcp", "--header", "Authorization:${IGNARU_AUTH}"],
      "env": { "IGNARU_AUTH": "Bearer ig_YOUR_TOKEN" }
    }
  }
}

Cursor

Add this to ~/.cursor/mcp.json, or .cursor/mcp.json inside a project.

{
  "mcpServers": {
    "ignaru": {
      "url": "https://ignaru.com/api/mcp/mcp",
      "headers": { "Authorization": "Bearer ig_YOUR_TOKEN" }
    }
  }
}

Codex

Add this to ~/.codex/config.toml, with IGNARU_TOKEN exported in your shell.

[mcp_servers.ignaru]
url = "https://ignaru.com/api/mcp/mcp"
bearer_token_env_var = "IGNARU_TOKEN"

Tools

Also: social_status, create_social_workspace, list_demo_boards, add_video, list_projects, get_project, make_client, add_card, update_card, post_update, list_feedback, triage_feedback, list_node_templates, list_custom_nodes, get_custom_node, validate_custom_node, dry_run_custom_node, save_custom_node, archive_custom_node, add_custom_step, upgrade_custom_step, list_custom_actions, list_pages, get_page, get_page_data, create_page, update_page, reorder_pages, pin_page, delete_page, get_prices, generate_video, list_calendar, find_free_slot, create_event, move_event, connect_app, list_loop_templates, create_loop_from_template. ignaru tools lists every tool in one line each.

Tools take canvases, leads and steps by name as well as by id, and every write takes an optional idempotencyKey. Errors end with Fix: (what to call next) and, where it helps, Valid: (the values that would have worked).

Resources: ignaru://context, ignaru://step-kinds, ignaru://guide and ignaru://loops/{id}. Prompts: quickstart and build_workspace. Try a prompt like “Build me a canvas that finds seed-stage fintech founders and drafts a short intro. Stop before anything is sent.”

REST

Everything above is a plain JSON API. Send the token as Authorization: Bearer ig_…. Errors come back as { "ok": false, "code": "...", "message": "...", "hint": "...", "valid": [...] }: hint says what to do next, valid lists the values that would have worked. Writes take an Idempotency-Key header: a retry with the same key returns the first answer. Each token gets 120 requests a minute. Writes are capped at 60 a minute, exports at 5 and questions to Iggy at 10.

curl https://ignaru.com/api/v1/loops \
  -H "Authorization: Bearer $IGNARU_TOKEN"

What it cannot do

Nothing leaves your team without a person pressing Approve in the app. The CLI, the MCP server and the API can read drafts. They cannot approve, edit or send them, and a token that tries to approve gets a 403 that says so.

Cold email and LinkedIn steps write drafts. Send with Glasa and social likes or follows go out only after an Admin approves. Setting a canvas live starts the finding and the writing, not the sending. An agent can build and run a whole canvas up to the Approve step, and then it waits for you.

In a team’s canvases and leads a key does at most what an Operator can, even an Admin’s key: approving sends, billing and team settings stay in the app. The one Admin power a key keeps is setting up teams: an Admin’s key can invite people, and only with an explicit confirm, because each invite emails a real person. Make a separate key for each place you use one, so you can revoke it without touching the others.