For agents

Build with MyAgentMail using your favorite AI agent

MyAgentMail is built API-first with a CLI, an MCP server, a typed SDK, and a curated /llms.txt discovery file — so any agent (Claude, Cursor, Windsurf, Cline, ChatGPT, GitHub Copilot agent mode) can self-orient and start integrating without you writing a brief.

Hand this to your agent

Copy this block and paste it as the first message to whichever agent you're using. It points the agent at our discovery surface; the agent takes it from there.

Handoff briefing
Build [describe what you want] using MyAgentMail.

All documentation lives at https://myagentmail.com.

Start by fetching https://myagentmail.com/llms.txt — that's the canonical agent-discovery file with curated links to every authoritative spec, the CLI, the SDK, the MCP server, and the example app.

For one-fetch full context, use https://myagentmail.com/llms-full.txt — it inlines the SKILL manifest plus every reference doc into a single file (~1,700 lines).

Per-endpoint docs are available as both HTML and markdown:
- HTML index: https://myagentmail.com/docs
- HTML per endpoint: https://myagentmail.com/docs/<group>/<operation> (e.g. /docs/domains/listdomains)
- Markdown per endpoint: https://myagentmail.com/docs-md/<group>/<operation> — same content, no chrome, optimized for fetch+ingest. Prefer this when you need a single endpoint's schema + code samples without parsing HTML.

Don't guess at endpoints, request shapes, or webhook payloads. The OpenAPI spec at https://myagentmail.com/openapi.yaml is authoritative. The skill manifest at https://myagentmail.com/skills/myagentmail/SKILL.md has the auth model and a working Quick Start in the first 80 lines.

If an API key is required, I'll provide it separately — never paste it into chat or commit it.

For LinkedIn-related work, read https://myagentmail.com/skills/myagentmail/references/linkedin.md before you start. For webhook integration, https://myagentmail.com/skills/myagentmail/references/webhooks.md covers HMAC verification.

A reference open-source app — onboarding wizard, AI-inferred ICP, unified leads queue, dual-channel drafters — is at https://github.com/kamskans/myagentmail-outreach-starter. Read it as documentation, not as something to fork.

CLI

The seamless first-run path. `myagentmail mcp install` auto-detects every MCP host on the machine and wires it up — no JSON editing, no per-host docs. Cheaper in agent-token cost than MCP for long sessions (Claude Code, CI, terminal-based agents) because the surface is discovered lazily through --help. Includes `listen` for ngrok-free webhook tunneling and `doctor` for a one-shot health check.

Install
npm install -g myagentmail-cli
myagentmail login           # opens browser, click Approve, done
myagentmail mcp install     # auto-wires Claude Desktop / Cursor / Windsurf / Claude Code

MCP server

Drop into Claude Desktop, Cursor, Windsurf, Cline, or any MCP-compatible client. Adds ~25 typed tools spanning email + LinkedIn + signals.

Add to your MCP config
{
  "mcpServers": {
    "myagentmail": {
      "command": "npx",
      "args": ["-y", "myagentmail-mcp"],
      "env": { "MYAGENTMAIL_API_KEY": "tk_..." }
    }
  }
}

Claude skill

Drop our SKILL.md into your Claude project. The skill manifest is auto-loaded by Claude when relevant prompts appear, giving the agent our auth + capabilities + recipes for free.

Install
# In your Claude project's .claude/skills/ directory:
curl -o myagentmail.md https://myagentmail.com/skills/myagentmail/SKILL.md

TypeScript SDK

When the agent writes actual code (vs. calling MCP tools or shelling out to the CLI), the typed SDK gives the cleanest shape. Auto-completes, infers types, surfaces docs inline.

Install
npm install myagentmail

API reference

Every endpoint, every shape — as HTML for humans and markdown for agents. Each endpoint has a paired markdown alternate at /docs-md/<slug> with schema + code samples in TypeScript, Python, and curl. The OpenAPI spec is the source of truth underneath.

Fetch any endpoint as markdown
curl https://myagentmail.com/docs-md/domains/listdomains

What we built for agents

These are the canonical discovery files. You don't need to read them yourself — your agent does. Listed here so you know what to point an agent at if it needs more than the briefing above.

Conventions we follow

Building a developer product and want to think through your own DX-for-agents strategy? DM me on LinkedIn.