Skip to content
Copy.ai logo

Copy.ai MCP server

AI-powered content generation and copywriting platform

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

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

About the Copy.ai MCP server

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

Tools

Copy.ai tools your AI can run

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

  • Run Workflow

    Start a Copy.ai workflow execution.

    2 fields

  • Get Workflow Run Status

    Retrieves the status of a workflow execution.

    2 fields

  • Get Workflow Run Outputs

    Retrieves the outputs of a completed workflow run.

    2 fields

Triggers

Copy.ai events your agent can watch

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

  • Workflow Run Completed

    Triggered when a workflow run is completed.

    1 field

Give your assistant Copy.ai

Connect Copy.ai 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.

Copy.ai MCP, answered.

No. That is the point of it. One Activepieces server exposes Copy.ai 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 Copy.ai 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 3 tools, including Run Workflow, Get Workflow Run Status, Get Workflow Run Outputs, 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.