Skip to content
Klenty logo

Klenty MCP server

Sales engagement platform for managing prospects and adding them to outreach cadences.

Klenty is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
5
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Klenty MCP server

Connect Klenty once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Klenty and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Klenty tools your AI can run

Once connected, your assistant can call any of these Klenty actions by asking in plain language.

  • Create Prospect

    Create a new prospect in Klenty.

    23 fields

  • Update Prospect

    Update an existing prospect in Klenty by email address.

    24 fields

  • Get Prospect by Email

    Find a prospect by email address in Klenty.

    1 field

  • Add Prospect to Campaign

    Add a prospect to a Klenty campaign/cadence using the startcadence endpoint.

    2 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Klenty

Connect Klenty once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Klenty MCP, answered.

No. That is the point of it. One Activepieces server exposes Klenty alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Klenty in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 5 tools, including Create Prospect, Update Prospect, Get Prospect by Email, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.