The platform has two modes. This guide covers the first one: you bring your lists, LDM handles delivery, and the whole process is driven by your AI agent or a chat with an MCP connector. From sign-up to replies in the Inbox.
There was a wave when everyone lived in chats. Now people are moving to agents. For us it's the same thing: the MCP connector plugs into a chat (Claude Desktop, Perplexity) and into an autonomous agent (Claude Code, Cursor, any MCP client) alike. A person in a chat gives tasks in plain words; an agent does the same on its own.
Either way, the same LDM sits on the other side: the same tools, the same expert layer, the same legal guardrails. The interface is a matter of habit, not capability.
Chat or agent doesn't matter. What matters is that the process follows a proven flow, not gut feeling.
However smart your agent is, it doesn't see the whole context: deliverability state, domain history, the typical pitfalls of each stage. So LDM answers not as a bare API but as a market expert: every response carries an _expert block — what to do next, the typical flow, where people usually fail.
Think of it as a consultation: a lawyer and a doctor can each be brilliant alone, but exchanging opinions in the moment prevents expensive mistakes. Your agent makes the decisions — our layer keeps reminding it what's going on around. The capability map and end-to-end scenario live at /api/v1/agent-guide; the agent reads it itself.
A person can do all of this alone. Our job is to keep them — and their agent — from failing where everyone fails.
This is the recommended path — one of several, but the one that genuinely makes life easier. Nothing is invented here: every step has an MCP tool and a documentation page behind it.
Every stage has a legal layer. You don't have to remember it: the platform won't let you skip it.
An MCP agent can walk the whole path — from sign-up to the first campaign — in one session. You confirm the launch.
Copy the config for your client — or just hand the agent a ready-made prompt and it does the rest.
{
"mcpServers": {
"ldm": {
"command": "npx",
"args": ["-y", "--package=@live-direct-marketing/sdk@latest", "ldm-mcp"],
"env": { "LDM_API_KEY": "ldm_..." }
}
}
}Connect to LDM over MCP (use the config from the guide; ask me for the key — or register a new account). Read /api/v1/agent-guide. Then walk me through the first launch: add a sending account, import my list, suggest variable enrichment, prepare a creative, send a test to my address, and show campaign readiness. Launch only after my confirmation.
https://api.live-direct-marketing.online/mcpThese clients can’t spawn a local process — connect them to our hosted server at https://api.live-direct-marketing.online/mcp. In claude.ai / Claude Desktop add it as a custom connector with a request header Authorization: Bearer ldm_.... In ChatGPT (developer mode), where custom headers aren’t supported, use the personal URL https://api.live-direct-marketing.online/mcp/k/<your-key> with authentication set to None — and treat that URL as a secret.
The “your lists — our delivery” mode works white-hat only. The rules are built into the conveyor:
We won't send what must not be sent — even if the agent asks.