Search and read proofs, comments and activity, and add or resolve comments in Ziflow. For marketing and print teams that review proofs in Ziflow. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"ziflow": {
"url": "https://ziflow.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"ziflow": {
"type": "http",
"url": "https://ziflow.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Search proofs by name and status, for example proofs with changes required or late. Then read one proof's stages and deadlines.
ziflow_search_proofs ziflow_get_proof
List all comments on one proof, with their author, page and resolved state. Read one comment to see its replies.
ziflow_list_comments ziflow_get_comment
List who did what on a proof and when, optionally between two dates.
ziflow_list_proof_activities
Add a comment to a proof at a page. Every reviewer on the proof sees it. Resolve a comment, or reopen it.
Changes data · ziflow_add_comment ziflow_resolve_comment
The login page asks for your Ziflow API key.
Find it in Ziflow → View Profile → API Key. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Ziflow API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Ziflow connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
ziflow_list_proofs | read | List proofs List proofs (review items) visible to the API user, with name, status, owner and deadlines. Good first call to discover proof ids. Ziflow API: GET /proofs. |
ziflow_get_proof | read | Get a proof Get one proof by id: its name, status, stages, reviewers, deadlines, folder and version data. Ziflow API: GET /proofs/{id}. |
ziflow_search_proofs | read | Search proofs Search proofs by name and status. Use proof_status to find, for example, proofs with changes_required or late. Ziflow API: POST /proofs/search. |
ziflow_list_proof_activities | read | List proof activity List the activity log of one proof (who did what, and when), optionally between two dates. Ziflow API: GET /proofs/{id}/activities. |
ziflow_list_comments | read | List comments List all comments on one proof, with their author, location (page or time), and resolved state. Ziflow API: GET /proofs/{id}/comments. |
ziflow_get_comment | read | Get a comment Get one comment on a proof by its id, including its replies, labels and resolved state. Ziflow API: GET /proofs/{id}/comments/{comment_id}. |
ziflow_list_folders | read | List root folders List the root folders the API user can see. Ziflow API: GET /folders. |
ziflow_get_folder | read | Get a folder Get one folder by id, with its name and contents. Ziflow API: GET /folders/{id}. |
ziflow_list_users | read | List users List the users of the Ziflow account, with their roles and status. Ziflow API: GET /users. |
ziflow_get_user | read | Get a user Get one user by id or email address. Ziflow API: GET /users/{identifier}. |
ziflow_list_contacts | read | List contacts List the contacts (external reviewers saved in the account), with name and email. Ziflow API: GET /contacts. |
ziflow_list_workflow_templates | read | List workflow templates List the workflow templates (review stages and reviewer sets) that new proofs can start from. Ziflow API: GET /workflowtemplates. |
ziflow_list_webhooks | read | List webhook subscriptions List the webhook subscriptions set up on the account, with their event types and target URLs. Ziflow API: GET /webhooks. |
ziflow_add_comment | write | Add a comment Add a comment to a proof at a page (or a time range for audio/video). The comment is visible to every reviewer on the proof. Not idempotent: each call adds a new comment. Ziflow API: POST /proofs/{id}/comments. |
ziflow_resolve_comment | write | Resolve or reopen a comment Mark a comment as resolved, or reopen it. Setting the same state twice is harmless. Ziflow API: PUT /proofs/{id}/comments/{comment_id}/resolve. |
ziflow_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
ziflow_request_feature | Request a missing feature Tell usefulapi that the user needs something the Ziflow tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
ziflow_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Ziflow (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
ziflow_cancel_subscription | Cancel the Pro subscription Cancel the caller's Ziflow Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run ziflow_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Ziflow server only. Subscribe with ziflow_upgrade (it returns a Stripe Checkout link). Cancel any time with ziflow_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running ziflow_upgrade before then undoes the cancel. Or write to [email protected].
Find late proofs or proofs that need changes. Review open comments on a proof. Read the activity log of a proof. Add a comment and resolve a comment. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Ziflow. The server calls the Ziflow API with your own Ziflow access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Ziflow API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Ziflow API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Ziflow API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Ziflow.
Yes, if you approve it. 2 of the 15 Ziflow tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Ziflow server only. Cancel any time: Pro then runs to the end of the paid period. Run ziflow_usage_status to see how many calls you used.
Ask the AI to run ziflow_upgrade: it returns a Stripe Checkout link. To cancel, run ziflow_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with ziflow_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.