English Français العربية

Audryo

Official registry Health

Lifecycle email for agents: journeys, campaigns, contacts, consent and delivery health.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http audryo 'https://mcp.audryo.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "audryo": {
            "type": "http",
            "url": "https://mcp.audryo.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Audryo agent toolkit
  2. Safety model
  3. Quick start
  4. Configuration
  5. MCP tools
  6. CLI
  7. Skills
  8. Contributing

Audryo agent toolkit

Let your AI agent run your lifecycle email: audiences, journeys, campaigns, emails and transactional sends in Audryo, through the same API the app uses. Your agent does the setup work; nothing reaches a customer until a person approves it.

This repo ships the audryo CLI, an MCP server and agent skills for Claude Code, Codex, Cursor and any other MCP client.

You:   Set up an onboarding journey for signups who haven't created a
       project after 3 days.

Agent: Reads your data schema, builds the audience, drafts a three-email
       journey, dry-runs it and fast-forwards it in the sandbox. Then it
       hands back what to review. Nothing has been sent.

Safety model

  • Drafts by default. Journeys, emails and campaigns an agent creates are review-only proposals.
  • Sending needs deliver. Without that scope a key cannot activate a journey or send anything, even by mistake. With it, Audryo still requires a passing dry run and confirmed emails.
  • Sandbox first. New projects capture every email in a sandbox inbox, so agents can test real journeys end to end. Going live is a human decision in the app.
  • Retry-safe. Sends and proposals take an Idempotency-Key, so a retried call never sends twice.
  • No inferred consent. Ingesting contacts never grants marketing consent.

Quick start

  1. Sign up (free during the public beta) and create a project. It starts in the sandbox.
  2. Create an API key under Settings → Developer with the smallest scope that works (see Configuration).
  3. Connect your agent:
Claude Code (plugin: MCP server + skills)
export AUDRYO_API_KEY="sf_live_..."
claude plugin marketplace add Audryo/agent-toolkit
claude plugin install audryo@audryo
Any agent: skills only
npx skills add Audryo/agent-toolkit
Any MCP client
{
  "mcpServers": {
    "audryo": {
      "command": "npx",
      "args": ["-y", "audryo", "mcp"],
      "env": {
        "AUDRYO_API_KEY": "sf_live_...",
        "AUDRYO_PROJECT_ID": "<project-uuid>"
      }
    }
  }
}

Codex: codex mcp add audryo --env AUDRYO_API_KEY=sf_live_... -- npx -y audryo mcp

Configuration

VariableRequiredDefault
AUDRYO_API_KEYyes—
AUDRYO_PROJECT_IDfor project toolslist with npx audryo bootstrap
AUDRYO_API_BASEnohttps://api.audryo.com/v1

Give agents the smallest key that works:

TaskScopes
Inspectread
Sync data, draft journeys, emails and campaignsread, write
Activate journeys, send campaigns and transactional emailread, write, deliver

MCP tools

AreaToolsScope
Orientget_manifest, get_bootstrap, get_setup_context, get_brief, get_plan_usageread
Product and dataget_product_context, get_data_context, list_contacts, ingest_contacts, ingest_eventsread / write
Audienceslist_audiences, get_audience, preview_audience, create_audience, update_audience, delete_audience, suggest_audiencesread / write
Journeyslist_journeys, inspect_journey, create_journey_proposal, revise_journey, propose_from_finding, run_dry_runread / write
Emailscreate_email, create_journey_emailwrite
Campaignslist_campaigns, draft_campaignread / write
Sandboxget_delivery_mode, list_sandbox_messages, get_sandbox_message, fast_forward_journeyread / write
Insightsget_delivery_health, get_performance, get_observation, run_observation, get_copilot_planread
Go liveactivate_journey, pause_journey, send_campaign, send_transactionaldeliver

Every tool is also a CLI command.

CLI

npx audryo bootstrap
npx audryo contacts ingest contacts.json
npx audryo events ingest events.json
npx audryo journeys list
npx audryo journeys inspect <workflowId>
npx audryo audiences create --name "All contacts" --definition '{"operator":"and","conditions":[]}'
npx audryo campaigns draft --name "July update" --audience-id <id> --subject "What's new"
npx audryo delivery health

Skills

SkillTeaches the agent to
audryo-apiConnect, pick scopes, use MCP or CLI instead of curl, stop at review
audryo-emailBuild valid email documents, handle locales, save drafts for review
audryo-sendingChoose communication classes, respect consent, protect deliverability

Full guide: https://app.audryo.com/docs/agents/quickstart

Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md and the changelog. Report security issues privately: SECURITY.md.

License: MIT

Frequently asked questions

What is Audryo?

Lifecycle email for agents: journeys, campaigns, contacts, consent and delivery health.

How do I install Audryo?

It runs as a remote server. In Claude Code: claude mcp add --transport http audryo 'https://mcp.audryo.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Audryo need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Audryo open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Audryo?

It is published by Audryo. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.