Skip to content
Chat Aid logo

Chat Aid MCP server

AI-powered assistant for your knowledge base.

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

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

About the Chat Aid MCP server

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

Tools

Chat Aid tools your AI can run

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

  • Add Custom Sources

    Upload one or more files as custom sources for training

    2 fields

  • Ask Questions

    Query your Chat Aid knowledge base and receive AI-generated answers with source citations

    3 fields

  • Get Custom Source by ID

    Retrieve single source details by ID

    1 field

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Chat Aid

Connect Chat Aid 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.

Chat Aid MCP, answered.

No. That is the point of it. One Activepieces server exposes Chat Aid 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 Chat Aid 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 4 tools, including Add Custom Sources, Ask Questions, Get Custom Source by ID, 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.