Integration

DitLead integration

DitLead is a cold outreach platform (email sequences, mailbox warmup, lead lists). Through its API an agent can create, read, update, search and delete contacts, add or remove a contact from a list, create, read and delete lists, list campaigns with their send, open, reply and bounce counts, verify an email address, check a domain's SPF, DKIM and DMARC records, and subscribe or unsubscribe a webhook to DitLead events. Connecting, editing, warming and deleting sender mailboxes, batch DNS checks, the mailbox analytics route and the API key check are not exposed. Authentication is a DitLead API key sent as a Bearer token in the Authorization header.

Connect DitLead How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in DitLead.Built from the 18 DitLead tools below, on the connection you add once.

What you can do with DitLead

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 7 operations

add_contact_to_listAdd contact to listPOSTAdds an existing contact to a list. Pass the contact's public ID and the list's public ID (from list_lists). Answers 404 when either does not exist.
create_contactCreate contactPOSTCreates a contact from its attributes (first_name, last_name, email, company...). Optionally pass listId to put it in a list or campaignId to add it to a campaign. Answers 409 when the contact already exists.
delete_contactDelete contactDELETEPermanently deletes a contact by its public ID and returns the deleted contact's public ID and email.
get_contactGet contactGETGets one contact by its public ID: its email addresses with verification status, attributes, list and campaign memberships, labels and how it was added.
list_contactsList contactsGETLists the workspace's contacts, 20 per page by default (pageSize up to 100). Use search to filter on attribute values and listId to keep one list's contacts; read data.pagination.totalPages to page.
remove_contact_from_listRemove contact from listPOSTRemoves a contact from a list without deleting the contact. Pass the contact's public ID and the list's public ID (from list_lists).
update_contactUpdate contactPUTUpdates a contact's attributes: send the attribute keys to change (for example first_name, company, phone) in attributes. The vendor does not document whether attributes left out are kept or cleared.

List, 4 operations

create_listCreate listPOSTCreates a new empty contact list and returns it; its data.publicId is the listId other tools take.
delete_listDelete listDELETEPermanently deletes a list and removes it from every contact that belonged to it; the contacts themselves are kept. Returns the deleted list's public ID and name.
get_listGet listGETGets one contact list by its public ID: name, type, prospect counts, valid, invalid and unknown email counts, verification flag, status and creation date.
list_listsList listsGETLists the workspace's contact lists with prospect counts and email validity counts, 20 per page by default (pageSize up to 100). Read data.pagination.totalPages to page.

Webhook, 2 operations

create_webhookCreate webhookPOSTSubscribes a URL to DitLead events; DitLead then posts each chosen event to it. Keep the returned id: delete_webhook needs it as subscriptionId.
delete_webhookDelete webhookDELETEDeletes a webhook subscription: pass the id that create_webhook returned as subscriptionId. DitLead stops sending events to its URL.

Campaign, 1 operation

list_campaignsList campaignsGETLists campaigns with their schedule, status and counts (sent, replies, opens, unsubscribes, bounces, prospects contacted, completed). Filter with status; page with page (starts at 1).

Dkim record, 1 operation

check_dkim_recordCheck dkim recordPOSTLooks up a domain's DKIM DNS record for one selector and reports whether it exists (data.hasDkim), its text (data.record) and whether it is valid (data.isValid).

Dmarc record, 1 operation

check_dmarc_recordCheck dmarc recordPOSTLooks up a domain's DMARC DNS record and reports whether it exists (data.hasDmarc), its text, whether it is valid and its policy.

Email, 1 operation

verify_emailVerify emailPOSTChecks the validity of an email address; msg holds the verification result as text.

Spf record, 1 operation

check_spf_recordCheck spf recordPOSTLooks up a domain's SPF DNS record and reports whether one exists (data.hasSpf), its text (data.record) and whether it is valid (data.isValid).

Use DitLead from Claude Code, Cursor or Codex

Connect DitLead in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DitLead operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect DitLead

Create your workspace
Sign up free. Nothing to install.
Connect DitLead once
Add your DitLead connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.