Skip to content
Webling logo

Webling MCP server

Give your AI assistant 1 tool it can call in Webling, over one server URL.

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

Tools
1
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
August 2026

About the Webling MCP server

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

Tools

Webling tools your AI can run

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

  • Get Events by ID

    Gets event data by a list of event IDs and optional calendar ID to filter.

    2 fields

Triggers

Webling events your agent can watch

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

  • New or Updated Event

    Triggers when an event is added or updated.

    1 field

  • On Changed Data

    Triggers when anything was added, updated or deleted since last request.

Give your assistant Webling

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

Webling MCP, answered.

No. That is the point of it. One Activepieces server exposes Webling 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 Webling 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 1 tool, including Get Events 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.