Skip to main content
MCP is an open protocol that gives an agent tools it can call on your behalf. SudoMock runs a remote MCP server, so a client that speaks MCP lists your templates and renders them from inside the conversation. The same account and the same credits sit behind it, so a render this way is billed exactly as an API render is.

​
Remote MCP server

SudoMock hosts the server at:
Connect any MCP client that supports remote servers over HTTP. There is nothing to install and no local process to run. The client opens a browser window where you sign in to SudoMock and approve access.
No client asks you to paste a password, a one time code or an API key into the conversation, and no client needs your sm_ key to use the server.
Each tab below is the install for that client.
Then open /mcp in Claude Code and select sudomock to complete the sign in.
Some clients only publish new tools after a reconnect or a restart. Hand an agent the setup prompt instead and it works out the client it is running in, adds the server, and stops at the sign in step:
Call get_account once the client is back. An authenticated response means the connection is live, and discovery lists the tools below. Nothing else needs to run: a render, an upload or a webhook call would spend credits to tell you what you already know. The setup prompt ends on that same read-only check, so a setup run generates nothing and spends nothing. SudoMock also publishes a skill file that tells an agent what this product can do, what a call needs and what an account allows, so it gets the call right the first time. Install it in a client that is not connected to the server above.

Install the SudoMock skill into your agent.

Open in Cursor

​
MCP server tools

Grouped by the part of the product they touch.
  • PSD mockups: upload_psd, list_psd_mockups, get_psd_mockup, render_psd_mockup, update_psd_mockup, delete_psd_mockup
  • Photo mockups: create_photo_mockup, list_photo_mockups, get_photo_mockup, update_photo_mockup_print_areas, render_photo_mockup, delete_photo_mockup
  • Video: render_video
  • Images and files: remove_background, create_upload_url
  • Fonts: list_fonts
  • Background work: get_job, list_jobs, wait_for_job
  • Webhooks: create_webhook_endpoint, list_webhook_endpoints, update_webhook_endpoint, delete_webhook_endpoint, test_webhook_endpoint, rotate_webhook_secret, list_webhook_deliveries, replay_webhook_delivery, replay_failed_webhook_deliveries
  • Account: get_account
The server also publishes four reference resources (docs://quickstart, docs://pricing, docs://formats, docs://errors) and guided prompts. The @sudomock/mcp package for local clients serves the same tools, plus upload_local_file for a file on your own machine. Some tools answer to a second, older name: use whichever the connection offers, and read its schema rather than assuming it mirrors the REST endpoint of the same name. There is no batch render tool, so one call produces one output and several outputs mean several calls. What an agent does with them:

​
Before you promise a result

An account on trial credits renders at a reduced width and its output carries a watermark. Check the account with get_account first, because a request above the cap answers OUTPUT_RESOLUTION_LIMIT rather than a quietly smaller image.

Use an API key instead

Write the calls yourself from a backend or a job runner.

Errors

Every error code, and which statuses are worth retrying.

Usage limits

The request rate, the parallel ceiling, and the headers.