Skip to content
Returning AI logo

Returning AI MCP server

Give your AI assistant 3 tools it can call in Returning AI, over one server URL.

Returning AI 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
September 2026

About the Returning AI MCP server

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

Tools

Returning AI tools your AI can run

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

  • Send Channel Message

    Posts a message to a specified channel as a chosen user

    6 fields

  • Reply Message

    Reply to a specific message as a chosen user in a channel.

    4 fields

  • React to Message

    Add an emoji reaction to a specific message as a chosen user.

    4 fields

Give your assistant Returning AI

Connect Returning AI 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.

Returning AI MCP, answered.

No. That is the point of it. One Activepieces server exposes Returning AI 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 Returning AI 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 Channel Message, Reply Message, React to Message, 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.