Integration

Klenty integration

Klenty is a sales engagement platform that emails, calls and follows up with prospects through cadences. Create, update and look up prospects (personal data), read their status, tag them, unsubscribe them or set them to Do Not Contact; start, stop and resume cadences, which send emails on the user's behalf; read lists, cadences, cadence email and per-step engagement metrics and completed calls; manage webhooks. Not exposed: bulk prospect creation and custom-field values in prospect lookups. Authentication is the Klenty API key (Settings > Integrations > Klenty API Key) in the x-API-key header, plus the Klenty username (login email) that every request URL contains.

Connect Klenty How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Klenty

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.

Prospect, 3 operations

create_prospectCreate prospectPOSTCreates a prospect in Klenty and puts it in a list (the default list, or a list created on the fly when the name is new), with optional tags, custom fields and owner. Answers status true or false.
list_prospectsList prospectsGETLooks up prospects (personal data: name, email, phone, company, title, location, social links, list, tags, owner). Pass Email for one prospect, or listName to page through a list, or a created or last-updated date range.
update_prospectUpdate prospectPOSTUpdates a prospect, found by its current email address: its fields, list, tags, outcome or custom fields. Sending Email sets a new email address for the prospect.

Cadence, 1 operation

list_cadencesList cadencesGETLists the cadences (email, call and task sequences) of the team with their id and name, or only those of one user when username is given.

Call, 1 operation

list_completed_callsList completed callsGETLists the completed calls of the user over a date range within the last 30 days, 200 per page, with disposition, direction, duration, numbers, notes and the prospect's name, email, phone and company (personal data).

Change status to do not contact, 1 operation

mark_prospect_do_not_contactMark prospect do not contactPOSTSets a prospect's status to Do Not Contact, which stops future emails to them. Reversible with revert_prospect_do_not_contact.

Delete, 1 operation

delete_webhookDelete webhookPOSTDeletes a webhook, so Klenty stops sending its event to the webhook's URL.

Email engagement, 1 operation

get_email_engagementsGet email engagementsPOSTReturns the email engagement counts of one cadence over a date range: prospects added, in cadence and completed, opens, clicks, replies, unsubscribes, bounces, positive and negative replies. Read-only.

Getall, 1 operation

list_webhooksList webhooksGETLists the user's webhooks with each one's id, destination URL and triggering event.

Hook, 1 operation

create_webhookCreate webhookPOSTCreates a webhook: Klenty calls subscription_url whenever the chosen event happens (reply, cadence started or completed, email open, click, bounce, unsubscribe and more). Answers the webhook id, URL and event.

List, 1 operation

list_listsList listsGETLists the prospect lists of the team, with each list's id and name.

Remove tag, 1 operation

remove_prospect_tagsRemove prospect tagsPOSTRemoves one or more tags from a prospect.

Resume, 1 operation

resume_cadenceResume cadencePOSTResumes the paused cadence of a prospect, so its remaining emails are sent on the user's behalf again.

Revert status to do not contact, 1 operation

revert_prospect_do_not_contactRevert prospect do not contactPOSTTakes a prospect out of Do Not Contact so they can be emailed again. The status becomes Not Contacted if it was before, otherwise Manually Stopped.

Startcadence, 1 operation

start_cadenceStart cadencePOSTAdds a prospect to a cadence and starts it. The cadence then sends its emails to the prospect on the user's behalf, and schedules its calls and tasks.

Status, 1 operation

get_prospect_statusGet prospect statusGETReturns a prospect's current status and its cadence status (for example In Cadence), looked up by email address or Klenty id.

Step wise engagement, 1 operation

get_stepwise_engagementsGet stepwise engagementsPOSTReturns the metrics of each step of one cadence over a date range: step number and type, emails sent, opens, replies, clicks, completions, tasks and calls, with the template name and subject of email steps. Read-only.

Stop, 1 operation

stop_prospect_emailsStop prospect emailsPOSTStops every email scheduled to be sent to a prospect.

Stopcadence, 1 operation

stop_cadenceStop cadencePOSTRemoves a prospect from one cadence, or from every cadence when cadenceName is left out, so no more cadence steps run for them.

Unsubscribe, 1 operation

unsubscribe_prospectUnsubscribe prospectPOSTSets a prospect's status to Unsubscribed, which stops every future email to them from Klenty.

Update, 1 operation

update_webhookUpdate webhookPOSTChanges a webhook's destination URL and triggering event. Klenty expects both with the webhook id: resend the current value (see list_webhooks) for the one that stays the same.

Use Klenty from Claude Code, Cursor or Codex

Connect Klenty in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Klenty 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 Klenty

Create your workspace
Sign up free. Nothing to install.
Connect Klenty once
Add your Klenty 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.