Skip to content
PeekShot logo

PeekShot MCP server

Give your AI assistant 2 tools it can call in PeekShot, over one server URL.

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

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

About the PeekShot MCP server

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

Tools

PeekShot tools your AI can run

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

  • Capture Screenshot

    Captures Screenshot of a URL.

    8 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant PeekShot

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

PeekShot MCP, answered.

No. That is the point of it. One Activepieces server exposes PeekShot 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 PeekShot 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 2 tools, including Capture Screenshot, Custom API Call, 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.