Skip to content
Schedule logo

Schedule MCP server

Trigger flow with fixed schedule

Schedule 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 Schedule MCP server

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

Triggers

Schedule events your agent can watch

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

  • Every X Minutes

    Triggers the current flow every X minutes

    1 field

  • Every Hour

    Triggers the current flow every hour

    1 field

  • Every Day

    Triggers the current flow every day

    3 fields

  • Every Week

    Triggers the current flow every week

    3 fields

  • Every Month

    Triggers the current flow every month

    3 fields

  • Cron Expression

    Trigger based on cron expression

    2 fields

Give your assistant Schedule

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

Schedule MCP, answered.

No. That is the point of it. One Activepieces server exposes Schedule 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 Schedule 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 Schedule 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.