Install
In a terminal, in the project where you use your agent:
npx skills add https://ignaru.comIt asks which agents to add the skill to. Then tell your agent “set up Ignaru”: it follows the skill to connect the MCP server and makes its first call, context, to check it works.
Your key
- Open Ignaru and go to Settings, You, API keys. Make a key named after the agent, like “Claude Code”.
- Put it in your shell profile (
~/.zshrcor~/.bashrc), not in a project file, then open a new terminal:
export IGNARU_TOKEN="ig_pk_..."The skill’s setup for each agent reads the key from IGNARU_TOKEN, so no file in your projects holds it. A key acts as you, never above an Operator, and you can revoke it from the same page.
What it teaches your agent
- Start with
context: your team, your role, credits, limits and what is waiting, in one call. - Build a workspace from a sentence in one
create_loopcall, with Approve after every step that writes to people. - Find companies and the people at them with Iggy. Adding anyone Iggy found takes your yes in the app; then it enriches them with a cost estimate first.
- Draft outreach, read replies, move leads on, and say what waits for your Approve.
- Read errors: each one says what to call next and which values would have worked.
The skill is 6 short files:
| File | Read it |
|---|---|
SKILL.md | The skill |
references/setup.md | setup |
references/workspaces.md | workspaces |
references/finding.md | finding |
references/outreach.md | outreach |
references/tools.md | tools |
Other ways in
- The skill alone: /skill.md. The whole folder: /skill.zip, to unzip into
~/.claude/skills/or your agent’s skills folder. - The MCP server by hand, for every client: CLI and MCP.
- The agent guide on its own: Ignaru for agents, or plain text at /llms-full.txt.
What it never does
Your agent never approves or sends. It drafts, and every email, note and reply waits at Approve until an admin on your team says yes in the Ignaru app. It asks before it spends credits on a big search or emails an invite.
Questions
How do I use Ignaru from Claude Code, Codex or Cursor?
Run npx skills add https://ignaru.com to install the Ignaru skill, export your Ignaru API key as IGNARU_TOKEN, and ask your agent to set up Ignaru. It connects to the MCP server at https://ignaru.com/api/mcp/mcp.
Can my agent send emails through Ignaru?
No. Your agent can draft emails, notes and replies, and every one waits at Approve until an admin on your team says yes in the Ignaru app. No key, tool or command can approve or send.
Where does my API key go?
In an environment variable, IGNARU_TOKEN, set in your shell. The skill's setup reads it from there and never writes it into a project file.
What can my agent do in Ignaru?
Build a workspace from a sentence, find companies and the people at them with Iggy, add and enrich leads, draft outreach, read replies and see what waits for Approve, acting as you with an Operator's rights at most.
Does it cost anything?
Installing the skill is free. Work your agent asks for uses your team's Ignaru credits the same way the app does, and the skill runs a dry run first where one exists.