Skip to content
Chatling logo

Chatling MCP server

Build AI chatbots trained on your data.

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

Tools
3
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
August 2026

About the Chatling MCP server

Connect Chatling 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 Chatling and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Chatling tools your AI can run

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

  • Send Message

    Send a message to the chatbot and receive an AI response.

    8 fields

  • Create Chatbot

    Create a new chatbot using a template or from scratch.

    2 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Chatling events your agent can watch

These start a run the moment something happens in Chatling, so work gets picked up on its own.

  • New Conversation

    Triggers when a new conversation is started by a customer.

    1 field

  • New Contact/Lead

    Triggers when a new contact or lead is collected by the chatbot.

    1 field

Chatling MCP, answered.

No. That is the point of it. One Activepieces server exposes Chatling 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 Chatling 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 3 tools, including Send Message, Create Chatbot, Custom API Call, 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.