MCP, CLI, and skills

There are three ways for an agent or a terminal to work with Audryo. Pick the first one unless you have a reason not to.

• npm: npmjs.com/package/audryo
• Source, skills and issues: github.com/Audryo/agent-toolkit

Hosted MCP server (recommended)

Start at audryo.com/mcp. Step-by-step for every client, with screenshots: Connect your agent.

https://mcp.audryo.com/mcp is a remote MCP server. The first time your agent uses it, it opens Audryo in the browser: sign in, pick the workspace, and choose what the agent may do. There is no key to create, store or rotate, and you can disconnect the agent anytime under Settings → Developer → Connected agents.

Claude Code

claude mcp add --transport http audryo https://mcp.audryo.com/mcp

Run /mcp in Claude Code to sign in.

Codex

codex mcp add audryo --url https://mcp.audryo.com/mcp
codex mcp login audryo

Claude app (desktop, web, mobile): Customize → Connectors → + Add → Add custom connector, paste the URL, then Connect.

Cursor and other JSON configs

{
  "mcpServers": {
    "audryo": { "url": "https://mcp.audryo.com/mcp" }
  }
}

Add the skills separately with npx skills add audryo/agent-toolkit.

Access levels on the consent screen map to the API scopes: Read (read), Draft and set up (write) and Send and go live (deliver). Sending is never preselected; when a task needs it, the agent asks you to approve it in the browser.

Beyond the tools in the catalog below, the hosted server adds create_project and connect_sending_provider (which returns a link; provider keys are never entered in chat). projectId is optional when the connected workspace has a single project. The hosted tools preview_email and preview_email_draft also display rendered email previews inside MCP Apps clients; see the preview guide.

Local MCP server and CLI (API key)

For scripts, CI jobs and servers without a browser, create an API key under Settings → Developer. Requires Node 20 or newer.

Claude Code: plugin

Installs the MCP server and all skills in one step.

export AUDRYO_API_KEY="sf_live_..."
claude plugin marketplace add Audryo/agent-toolkit
claude plugin install audryo@audryo

Skills for any agent

Works with Claude Code, Codex, Cursor and other agents that read skills.

npx skills add audryo/agent-toolkit

MCP server by hand

Codex

codex mcp add audryo \
  --env AUDRYO_API_KEY=sf_live_... \
  --env AUDRYO_PROJECT_ID=<project-id> \
  -- npx -y audryo mcp

Claude Code

claude mcp add audryo \
  -e AUDRYO_API_KEY=sf_live_... \
  -e AUDRYO_PROJECT_ID=<project-id> \
  -- npx -y audryo mcp

Cursor and other JSON configs

{
  "mcpServers": {
    "audryo": {
      "command": "npx",
      "args": ["-y", "audryo", "mcp"],
      "env": {
        "AUDRYO_API_KEY": "sf_live_...",
        "AUDRYO_PROJECT_ID": "<project-id>"
      }
    }
  }
}

Ask the agent to "list my Audryo journeys" to check the connection.

Environment (local server and CLI)

Skills

Skills give an agent Audryo-specific know-how before it starts working.

Install them with npx skills add audryo/agent-toolkit or the Claude Code plugin above. The source lives at github.com/Audryo/agent-toolkit.

CLI

npx audryo bootstrap
npx audryo contacts ingest contacts.json
npx audryo events ingest events.json
npx audryo emails create --title "July update" --subject "What's new in July"
npx audryo journeys list
npx audryo journeys inspect "$WORKFLOW_ID"
npx audryo campaigns draft --name "July update" --audience-id "$AUDIENCE_ID" --subject "What's new"
npx audryo delivery health

Ingest files can be a plain array or { "contacts": [...] } / { "events": [...] }.

Sending commands need a deliver key and should only run when you mean it:

npx audryo journeys activate "$WORKFLOW_ID"
npx audryo transactional send --message-id "$MESSAGE_ID" \
  --email amelia@example.com --idempotency-key receipt-ord_1842

MCP tool catalog

A worked propose → dry-run loop: Agent walkthrough.

What each scope unlocks

Related

• Agent quickstart
• Agent walkthrough
• Design emails with your agent
• Agent API reference