Audryo

com.audryoPublished by audryo.comOfficial publisherv0.2.0Updated Oct 30, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Audryo lets an assistant build lifecycle email in Audryo: audiences, journeys, campaigns, emails and transactional sends, with human approval before anything…

What you can do
  • Orient and inspect: read the manifest, bootstrap and setup context, briefs and plan usage.
  • Manage contacts and data: list contacts, ingest contacts and events, read product and data context.
  • Build audiences: list, preview, create, update, delete and suggest audiences.
  • Draft journeys and emails: create and revise journey proposals, run dry runs, create emails and journey emails.
  • Draft campaigns and test in the sandbox: list and draft campaigns, read sandbox messages, fast-forward journeys.
  • Review insights and go live: delivery health, performance and observations, plus activating or pausing journeys and sending campaigns or transactional email.
When to use it
Useful when you want an assistant to do the setup work of lifecycle email — defining audiences, drafting multi-step journeys and campaigns, and testing them in a sandbox — while a person reviews and approves before anything reaches customers.
Requirements
A remote MCP endpoint with OAuth sign-in, or the local npm package run through npx. An Audryo account and project are needed; the README also describes an API key in AUDRYO_API_KEY with scopes read, write and deliver, a project ID in AUDRYO_PROJECT_ID, and an optional AUDRYO_API_BASE.
Before you install
Sending and activation require the deliver scope, which lets a key send real email; grant the smallest scope that works. Tools can write and delete audiences, ingest contacts and events, and send campaigns or transactional email. Drafts are review-only by default and new projects start in a sandbox, but going live is a human decision. Ingesting contacts does not grant marketing consent.

Installation

In SourceWeft

  1. Open Audryo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.audryo%2Faudryo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

Audryo agent toolkit

[npm] [CI] [License: MIT] [Listed on mcpservers.org]

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.

text
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)

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

Any agent: skills only

bash
npx skills add Audryo/agent-toolkit

Any MCP client

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

bash
npx audryo bootstrapnpx audryo contacts ingest contacts.jsonnpx audryo events ingest events.jsonnpx audryo journeys listnpx 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

Source: README.md at commit 379e73f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestOct 22, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts