Skip to content
Manual Trigger logo

Manual Trigger MCP server

Give your AI assistant 0 tools it can call in Manual Trigger, over one server URL.

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

Tools
0
Works with
Any MCP client
License
MIT, open source
Updated
August 2026

About the Manual Trigger MCP server

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

Triggers

Manual Trigger events your agent can watch

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

  • Manual Trigger

    Manually start your own flow without any extra configurations

    1 field

Give your assistant Manual Trigger

Connect Manual Trigger 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.

Manual Trigger MCP, answered.

No. That is the point of it. One Activepieces server exposes Manual Trigger 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 Manual Trigger 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 watch Manual Trigger for events and hand the work to 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.