Skip to content
Open app Talk to sales
Manual Trigger logo

Manual Trigger MCP server

Start a flow on demand with a button click.

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

Start building See the Manual Trigger integration
Tools
0
Works with
Any MCP client
License
MIT, open source
Updated
September 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

    Start the flow on demand with the Run Flow button

    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.

Get your server URLTalk to sales

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.

More core apps on the same server

Browse all MCP apps
Webhook

Webhook

Receive HTTP requests and trigger flows using unique URLs.

Core2 actions · 1 trigger
HTTP

HTTP

Send HTTP requests to any URL and use the response in your flow

Core2 actions
Storage

Storage

Store or retrieve data from key/value database

Core6 actions
Tables

Tables

Core9 actions · 3 triggers
SMTP

SMTP

Send emails using Simple Mail Transfer Protocol

Core1 action
Sub Flows

Sub Flows

Trigger and call another sub flow.

Core3 actions · 1 trigger