PopMCP
copy_ai_Find out what a Copy.ai workflow takes before running it.
Copy.ai MCP server for your AI
Run a prospect research workflow for a list of companies and read the results in your chat, find out why last week's runs failed, or get a webhook when a run finishes.
PopMCPCopy.ai
Run my prospect research workflow for Acme and show me what comes back
Supported Copy.ai tools
Every endpoint of Copy.ai's API, plus tools that start a run and wait for its output, learn a workflow's input names from its earlier runs, and add up credits, so a run is never started twice by accident.
13 tools in the full catalog: 7 read and 6 write. 13 load by default, and the rest are found with tool search.
copy_ai_Read one workflow run: status, done, input, output, metadata, created_at and credits spent.
copy_ai_List the runs of one workflow, a page at a time.
copy_ai_Run a Copy.ai workflow and wait for its output: the usual way to run one.
copy_ai_Run one Copy.ai workflow for up to 10 sets of inputs, one run each, and wait for the outputs.
copy_ai_Start one run of a Copy.ai workflow and return straight away with its run_id, before any output exists.
copy_ai_Add up the recent runs of one Copy.ai workflow: how many by status, credits spent, and the ids of failed runs.
copy_ai_Wait for a Copy.ai workflow run that has already started, up to wait_seconds (default 40, at most 45), and return its status, done, output and credits.
copy_ai_Remove a webhook, so Copy.ai stops sending those events to its link.
copy_ai_Make sure Copy.ai sends an event to a link: reuses a webhook with the same url, event and workflow, or registers one.
copy_ai_Read one webhook: webhook_id, url, event_type, workflow_id and scope.
copy_ai_List the webhooks registered for the Copy.ai workspace, a page at a time.
copy_ai_Ask Copy.ai to POST to a link when a workflow event happens.
Connect Copy.ai to Claude, ChatGPT and Claude Code
Credentials off one Copy.ai screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
Paste an API key from Copy.ai: click Configuration in the left sidebar, then View API Keys, then Create. The key is shown once. PopMCP checks it with a read that spends no credits. A key reaches one workspace, so there is nothing else to choose. Copy.ai's pricing page lists API access on its Enterprise plan.
API key
••••••••••••3f7aConnectionVerified
Running a workflow and changing webhooks are writes and wait until an owner or admin allows write actions; new connections start read-only. Every run spends workflow credits from your Copy.ai plan, so tick Copy.ai on the PopMCP consent screen only for clients that need it.
Reach Copy.ai
Reach other connectors
Teammates on read-only
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Copy.ai credential never leaves the server.
app.popmcp.com/mcp
Claude wants to connectApproveAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
Run my prospect research workflow for Acme and show me what comes back
copy_ai_get_workflow_inputsok
Then just ask for the work
“Run my prospect research workflow for Acme and show me what comes back”
- get_workflow_inputs
- run_workflow
“Run this workflow once for each of these five companies and put the results in a table”
- get_workflow_inputs
- run_workflow_batch
- wait_for_workflow_run
“How many runs of this workflow failed this month, and how many credits has it used?”
- summarize_workflow_runs
- get_workflow_run
“Tell my endpoint whenever a workflow run fails, and show me the webhooks already set up”
- list_webhooks
- ensure_webhook
Use Copy.ai from the assistant you already open
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Claude DesktopCustom connector
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
Claude WebCustom connector
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
ChatGPTCustom connector
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
CodexDesktop & CLI
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
OpenCodeCoding agent
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
ZCodeDesktop app
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
Explore other MCP servers
Every one of them runs on the same hosted endpoint, with the same controls.
FAQ
Copy.ai MCP server questions
What teams ask before putting Copy.ai behind an AI client.
What does the Copy.ai MCP server need to connect?
One Copy.ai API key. In Copy.ai click Configuration, then View API Keys, then Create, and paste the key. No developer app is needed. Copy.ai's pricing page lists API access on its Enterprise plan, so if you do not see API Keys, ask your Copy.ai contact. A key reaches one workspace; for a second workspace, add a second connection.
How does the AI know which workflow to run?
You tell it. Copy.ai's API has no way to list workflows, so give the AI the workflow's id: open the workflow in Copy.ai, then its API tab, and copy the end of the API endpoint link, or the whole link. The API also does not describe a workflow's inputs, so get_workflow_inputs reads the names its earlier runs used. For a workflow that has never run, tell the AI the input names.
What does a run cost?
Each run spends workflow credits from your Copy.ai plan. The amount depends on the workflow's steps, and every result shows what that run used. Reading runs and managing webhooks spend none. The API does not report your balance. When the workspace reaches its credit limit, Copy.ai refuses new runs and the AI tells you why.
What happens with a workflow that takes a long time?
run_workflow waits for up to 45 seconds. If the run is not finished it returns the run id, and wait_for_workflow_run carries on from there, so nothing is lost and nothing is charged twice. A start is never retried automatically, because a second start would spend credits again.
Can it write copy without a workflow?
No. Copy.ai's API runs workflows you have already built in Copy.ai and reports on them. It cannot build or edit a workflow, and it has no endpoints for Copy.ai's chat, Tables or Prospect Finder. Your AI client can write text itself, and call a workflow for the steps you have built.
Is Copy.ai still its own product?
Fullcast announced it had acquired Copy.ai in October 2025. Copy.ai's site, app and API were still running under the Copy.ai name when this page was written, and its API guide now lives on Fullcast's help site. Fullcast describes bringing these workflows into its own platform as Fullcast Propel, so check with your Copy.ai contact about your account's plans.
Which Copy.ai events can PopMCP watch?
Four triggers, delivered by webhooks PopMCP can register with your key: a workflow run started, finished or failed, and the workspace reaching its credit limit. You can also register your own webhooks with ensure_webhook, which reuses a matching one so events are not delivered twice.
Can I limit what the AI is allowed to do?
In PopMCP, yes: a connection starts read-only, so the AI can read runs and webhooks, and running workflows, which spends credits, stays blocked until an owner or admin allows write actions. Copy.ai's own keys have no permission options, and a key can run every workflow in its workspace.
Do I have to run or host the Copy.ai MCP server myself?
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Which AI clients can use this MCP server?
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
How do I connect Copy.ai to Claude Code?
Connect Copy.ai in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Copy.ai on the consent screen. The Copy.ai tools are then available in that session, and no Copy.ai credential is stored on your machine.
Do all 13 Copy.ai tools load by default?
Yes. The Copy.ai catalog is small enough that all 13 tool definitions load into every conversation, so your AI never has to search for one before it can call it.
What is the difference between a tool and a trigger?
A tool is something your AI calls, and there are 13 here. A trigger is something PopMCP watches for you: 4 Copy.ai events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Copy.ai.
Connect Copy.ai to your AI in minutes
Launch a hosted MCP endpoint for Copy.ai, keep tool access under control, and start testing real workflow prompts right away.