Postcards MCP

Ask Your Assistant for the Email. Get the HTML.

Postcards runs a public MCP server, so Claude, Cursor, and ChatGPT can reach your email projects directly. Browse folders, check what’s left of your export quota, and pull finished HTML — by asking, in a sentence.

Included on every plan, the free Start plan included. See plans →

  • Six tools your assistant can call
  • Works with the API key you already have
  • Claude, Cursor, ChatGPT, Zed
  • Export with your variables filled in
  • Nothing can be renamed, moved, or deleted
  • Revoke the key and access stops instantly

Six things your assistant can do without leaving the chat

MCP is the open standard Anthropic published for connecting assistants to outside tools. Our server exposes six, and the assistant picks the right one on its own.

  • List your projects

    Everything in the workspace, a page at a time, and filtered to one folder when you name it.

  • Open one project

    Pull the details for a single email once you know its id — either the numeric one or the short hex form.

  • Browse the folders

    Read the structure you already organized your work into, instead of hunting through a flat list.

  • Look inside a folder

    Ask what’s in Newsletters and get that folder’s projects back, paginated like the main list.

  • Check the quota

    Which plan is active, where the billing period sits, and how many exports you have left this month.

  • Export the email

    Render a project to HTML or a ZIP, with placeholder values supplied in the same request.

Connected in three steps

No separate MCP account, no second password. The server is a thin layer over the Postcards API, so your existing key is all it needs.

  • 1

    Copy a key

    Workspace Settings, API tab, create a key and copy it while it’s on screen. Already have one for the REST API? Use that.

  • 2

    Add the server

    Drop our endpoint into your client’s MCP settings with the key in the authorization header. Newer clients take the URL directly.

  • 3

    Ask for something

    “List my Postcards projects.” If the tools are wired up correctly, the answer comes back with your own work in it.

mcp settings

"postcards": {
  "type": "http",
  "url": "https://mcp-postcards.designmodo.com/mcp",
  "headers": { "Authorization": "Bearer YOUR_KEY" }
}

No syntax to remember. Just ask.

You don’t name the tool or format the request. Describe what you want and the assistant works out which call to make.

  • Finding things

    Plain questions about your workspace. The assistant pages through the results itself when there are more than fit in one answer.

    you type

    List my Postcards projects.

    What’s in the Newsletters folder?

    How many exports do I have left this month?

  • Getting the HTML

    Ask for an export and say what should replace the placeholders. The markup comes back ready to paste.

    you type

    Export the launch email as HTML with image hosting on.

    Export it again and replace {{first_name}} with Alex and {{company}} with Acme.

Whatever you already have open

Newer clients connect to the URL directly. Everything else reaches it through the standard stdio bridge, which is one extra line of configuration.

  • Claude Desktop

    Add the server to your Claude config file. Recent builds take the HTTP URL; older ones go through the bridge.

  • Cursor

    Native HTTP support from version 0.42 onward, so the endpoint and a header are the whole setup.

  • ChatGPT and Zed

    Register it as a custom connector in ChatGPT, or as a context server in Zed. Same URL, same key.

  • Anything else

    If your client speaks MCP but not HTTP yet, the stdio bridge covers it. Nothing about the server is proprietary.

Read the MCP setup guide →

An assistant with your projects, not with your permissions

Every tool on the server either reads or exports. There is no delete, no rename, no move — so a misread instruction can’t cost you a design.

  • Read and export only

    The six tools are the whole surface. Editing still happens in the editor, in front of somebody who can see the result.

  • Your key isn’t stored

    It’s passed straight through to the API on each call. The server doesn’t log it and doesn’t keep a copy.

  • The same rules apply

    Team scoping, plan gating, rate limits, and your export allowance are enforced exactly as they are for a direct request.

  • Off in one click

    Delete the key in your workspace settings and the next call from that client is refused. No other cleanup to do.

Building something that runs on its own?

MCP is for asking. When the work should happen on a schedule or inside your product, the same key drives the Postcards API directly.

MCP Questions

  • It is a public Model Context Protocol server that lets an AI assistant work with your Postcards projects. MCP is the open standard Anthropic published for connecting assistants to outside tools, and ours exposes six of them.

  • Claude Desktop, Cursor, ChatGPT custom connectors, and Zed all connect over HTTP. Any other MCP-capable client can reach the same endpoint through the standard stdio bridge.

  • List your projects, open a single project, browse folders, look inside one folder, check your export quota, and export a project to HTML or a ZIP. That is the complete list.

  • No. The MCP server runs on top of the Postcards API and authenticates with the same API key. If you already made one for the REST API, reuse it.

  • No. Every tool is read-only or a one-way export. Nothing on the server can rename, move, edit, or delete a project — creating and editing stay in the editor.

  • All of them, including the free Start plan. Your export allowance still depends on your plan, and CDN-hosted assets remain a Pro feature.

  • It is not. The key is forwarded to the API with each request and is never logged or cached. Deleting the key in your workspace settings cuts off access immediately.

  • The same limits as the API: sixty read requests and ten exports a minute, drawn against your monthly export allowance. ZIP exports returned through MCP are capped at 5 MB, so bulk work is better done against the API directly.

Your assistant is already open. Give it your emails.

One key, one endpoint, and the next export is a sentence away instead of a download.

Included on every plan, the free Start plan included. See plans →

Hey there 👋 Friends from designmodo are here to help!