DEV Community

RPScripts
RPScripts

Posted on

Shipping chat mockups from your terminal: an MCP server for realistic message screenshots

Most teams need a realistic chat screenshot long before they need a production chat backend. A landing page that promises "your messages, everywhere" but shows a grey rectangle of lorem ipsum reads as a half-finished product. Hand-built Figma mockups work right up until someone asks for a third platform, a dark mode variant, or a change in the copy at 6pm on a Friday.

MockupChat takes that job away from the design file: it renders conversations for 16 messaging apps (WhatsApp, iMessage, Discord, Slack, Telegram, Tinder, TikTok, and friends) with platform-accurate bubbles, ticks, tails, read receipts and status bars, then exports a PNG — or an MP4 that plays the conversation out message by message.

The interesting part for this audience: it is not locked inside a web UI. There is a public REST API and a stateless MCP server, so an agent can compose a conversation, validate it, and hand back an editor link without a human opening a browser tab.

Wiring it into an agent

The MCP endpoint is a single streamable HTTP URL. No auth, no key, no account:

{
  "mcpServers": {
    "mockupchat": {
      "type": "streamable-http",
      "url": "https://mockupchat.com/mcp"
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Five tools are exposed, and they are scoped deliberately small:

Tool What it gives you
list_platforms The 16 platform skins, their capabilities, and where the free/Pro export boundary sits
list_templates Public templates, filterable by platform or name, paginated
get_template One template as editable chat JSON plus a link that opens it in the editor
compose_chat Up to 8 participants and 40 messages, with validated senders and dates
validate_chat Checks a version-1 chat document without saving, fetching media or rendering

A typical agent loop looks like this:

  1. list_platforms to confirm the platform and its export rules.
  2. list_templates to find a starting point for the tone you need (a support thread, a launch announcement, a group chat).
  3. compose_chat with the script you wrote — it validates participant ids and timestamps for you.
  4. validate_chat if you assembled the JSON by hand.
  5. Open the returned editorUrl, review it, export.

The REST route, when you do not want MCP

Same data, plain HTTP, if you are wiring this into a build script rather than an agent:

curl https://mockupchat.com/api/v1/compose \
  -H 'Content-Type: application/json' \
  --data '{
    "platform": "whatsapp",
    "title": "Fictional launch demo",
    "participants": [
      {"id": "me", "name": "Alex", "isMe": true},
      {"id": "sam", "name": "Sam", "isMe": false}
    ],
    "messages": [
      {"senderId": "sam", "text": "Ready for the demo?", "at": "2026-10-15T09:41"}
    ]
  }'
Enter fullscreen mode Exit fullscreen mode

The response contains the chat document and an editorUrl. The API hands you a document and a link — it does not render images server-side. Export stays in the browser, which keeps the service simple and keeps your content off a server.

There is an OpenAPI 3.1 spec at https://mockupchat.com/openapi.json if you would rather generate a client.

The rules that matter

Invented content only. The service is for fictional conversations: demos, lessons, marketing mockups, stories. Not for repackaging a real person's messages, and not for anything that looks like a genuine quote from a real customer. The API response carries a fictional provenance marker, and you are expected to keep that label when you publish.

Free means watermarked. Exporting a PNG for WhatsApp, iMessage or Instagram works without an account, with a small watermark. Other platforms, device frames, social formats (1080×1350, 1080×1920) and silent MP4 export are part of Pro.

The MCP server has no access to you. No OAuth, no scopes, no project access, no uploaded files. It only ever sees the chat you send it.

Rate limits exist. 64 KiB per request, 60 requests per minute per IP per Cloudflare location, shared across MCP and API. A 429 comes with a Retry-When header.

Editor links are readable by anyone who has them. Conversation data is encoded in the URL fragment, so treat those links as shareable artifacts, not secrets.

When it is the wrong tool

If you need a real chat backend, real users, real message history — none of this applies. This is a mockup and content generator. And if you need pixel-perfect control over every bubble, a design file is still the better tool. The sweet spot is the middle: a convincing conversation, generated in seconds, in a format you can drop into an ad, a deck, an app store page or an onboarding flow.

Top comments (0)