Skip to content
Knock logo

Knock MCP server

Notification infrastructure for developers. Manage users, trigger workflows, and track messages.

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

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

About the Knock MCP server

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

Tools

Knock tools your AI can run

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

  • Trigger Workflow

    Trigger a Knock notification workflow for one or more recipients.

    5 fields

  • Identify User

    Create or update a user in Knock.

    6 fields

  • Get User

    Retrieve a user from Knock by their ID.

    1 field

  • Delete User

    Delete a user from Knock by their ID.

    1 field

  • Get Message

    Retrieve a Knock message by its ID.

    1 field

  • List Messages

    List Knock messages with optional filters and pagination.

    6 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Knock

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

Knock MCP, answered.

No. That is the point of it. One Activepieces server exposes Knock 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 Knock 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 7 tools, including Trigger Workflow, Identify User, Get User, 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.