# Klenty
ID: 04-klenty
Page: https://gtmmcps.com/tools/04-klenty
JSON: https://gtmmcps.com/data/tools/04-klenty.json
Documentation references: https://gtmmcps.com/docs/04-klenty/
Category: AI SDRs
MCP support: official
Testing: RESEARCHED
API access: paid
Last checked: 2026-09-07
Endpoint check: docs-only; date: 2026-09-04

A sales engagement platform whose AI layer ("Agentic Cadences") researches accounts across 150+ data sources, drafts tailored 1:1 emails and value propositions per account, and suggests next actions after sales conversations ("Action AI").

## MCP links
- https://api.klenty.com/mcp
- https://zapier.com/mcp/klenty
- https://runbear.io/solutions/integrations/slack/mcp/servers/klenty

## Sources
- https://www.klenty.com
- https://www.klenty.com/pricing
- https://zapier.com/mcp/klenty
- https://runbear.io/solutions/integrations/slack/mcp/servers/klenty
- https://api.klenty.com/mcp

## Research notes
SWEEP FLAG - could not verify the "SDRx" product name specifically; homepage describes AI features under "Agentic Cadences" / "Action AI" branding instead. Either the product was renamed/discontinued or the naming in the seed list is stale - re-verify before publishing any "SDRx" reference. [api_gate 2026-08-25] Reclassified unknown -> paid from the vendor's own page (https://www.klenty.com/pricing): API Connections is listed in the feature set of the lowest tier, Starter at $50/mo billed annually, self-serve with a card; there is no free plan. 2026-09-02: mcp_status none-found -> community. Two third-party hosted connectors answer today: https://zapier.com/mcp/klenty (9 triggers such as On Reply and On Bounce, 10 write actions such as Add Prospect, Start Cadence, Stop Cadence and Update Prospect) and Runbear's Klenty MCP for Slack (Update Prospect, Start Cadence, Add Prospect to List). Neither is Klenty-published; klenty.com has no llms.txt or MCP page and the official MCP registry has no klenty entry. Same treatment as WorkRamp in 11-enablement-coaching.md: community, unofficial. 2026-09-07: https://api.klenty.com/mcp returned 401 with a JSON-RPC body: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Missing credentials: provide Authorization: Bearer <token> or x-api-key"},"id":null} (https://api.klenty.com/mcp). mcp_status raised community to official on this evidence: the route sits on Klenty's own api.klenty.com domain and the control path https://api.klenty.com/zzznotamcp returns an Express 404, so /mcp is a purpose-built first-party MCP route, not a blanket auth wall; https://app.klenty.com/mcp answers identically. The previous community status rested on a Zapier-hosted connector, retained below as a secondary path.

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: none-found

Read current vendor documentation before configuring or running commands.