Get Ignaru

Use it in your browser, from your agent, or from your terminal. Every way works on the same workspaces, and nothing is sent until a person on your team presses Approve.

Start free Connect your agent

1,000 free credits. No card needed.

Available nowWeb appBuild workspaces on a board and approve every send. The main way in.Start free
Available nowMCP in your agentClaude Code, Cursor, Codex and Claude Desktop can work on your workspaces.Set up your agent
Coming to npmThe ignaru CLIBuilt and working from the repository. Not on npm yet.See what it does

Start in your browser

The web app is the main way to use Ignaru. Tell Iggy who you sell to and it builds the workspace. You watch what it finds, read what it writes, and approve what goes out.

Nothing to install. Sign up and your first workspace is one sentence away.
Drafts wait at Approve until a person on your team says yes.
Works with Gmail, Google Calendar, HubSpot, Slack, LinkedIn and 250+ apps.
Your whole team works in one place, with no price per seat.

Start free Book a demo

1,000 free credits. No card needed.

Run it from your own agent

Ignaru speaks MCP. Your agent can build a workspace, add steps and leads, and see what is waiting at Approve. Anything that reaches a person still needs a yes from your team.

Get a key
Open Ignaru and go to Settings, You, API keys. Name it after where it will live and copy it. It starts with ig_pk_ and is shown once. Use it wherever a snippet says ig_YOUR_TOKEN. Codex reads it from IGNARU_TOKEN.
Paste your client’s setup
Pick your agent app and copy the command or config. It talks to the server over Streamable HTTP.
https://ignaru.com/api/mcp/mcp

Run this once in your terminal.

Terminal

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

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

~/.cursor/mcp.json

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

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

~/.codex/config.toml

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

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

claude_desktop_config.json

{
  "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" }
    }
  }
}

Ask for what you want

Then talk to your agent as you would to a teammate.

Build me a workspace that finds seed-stage fintech founders and drafts a short intro. Stop before anything is sent.

It acts as youA key has the role you have in each team today, never more. Revoke it in Settings and it stops working straight away.
It cannot sendAgents can read drafts. They cannot approve, edit or send them, and a token that tries gets a 403.
One key per placeName a key after where it lives, like Laptop or Cursor, so you can revoke one without touching the rest.

Read the full MCP setup and tool list

The ignaru CLIComing to npm

Look at your workspaces, build them, and ask Iggy without leaving the terminal. It needs Node 18 or newer and has no dependencies.

It is not on npm yet, so there is nothing to install from npm today. From a checkout of the repository you can build it and link it:

From the repository, today

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

Once it is published, you will run npx ignaru login with nothing installed.

Install and sign-in details

Terminal

# Build a workspace 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 the next one passes to --after.

What it does

ignaru digest --week
What every workspace did in the last day or week, and what is stuck.
ignaru stuck
Stuck steps, each with one fix. Worked out by fixed rules, so it costs no credits.
ignaru new-loop "<name>"
Make a workspace and add steps to it, then see its board with colour in your terminal.
ignaru leads --stage warm -q acme
Search leads by text, stage or workspace. ignaru drafts lists what is waiting for approval.
ignaru enrich <lead id>
Find and check facts about leads, each with its sources. ignaru explain shows where a value came from.
ignaru ask "<prompt>"
Ask Iggy and print the answer. Point it at one workspace with a flag.

Every read command takes --json. ignaru login opens your browser, you check the code and press Approve, and that computer gets its own key.

The same rule in every way in

Nothing leaves your team without a person pressing Approve in the app. The web app, MCP and the CLI can all read drafts. None of them can approve, edit or send one.

Start free Read the docs