Skip to content
Open app Talk to sales
Roe AI logo

Roe AI MCP server

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

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

Start building See the Roe AI integration
Tools
3
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Roe AI MCP server

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

Tools

Roe AI tools your AI can run

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

  • Run Agent

    Execute an agent with provided inputs and return results immediately

    3 fields

  • Run Query

    Execute a query synchronously and return results

    3 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Roe AI

Connect Roe 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.

Get your server URLTalk to sales

Roe AI MCP, answered.

No. That is the point of it. One Activepieces server exposes Roe 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 Roe 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 Run Agent, Run Query, 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.