Design
zaps.design
An MCP server for design automation that searches templates, uploads local images, and renders customized designs with photos and text.
ENDPOINT 1
https://api.zaps.design/mcp
MCP server metadata
- Name
- zaps
- Version
- 2
Zaps turns someone's photos into finished social-media designs. Call create_designs with a search query you have written, the photo URLs and the words to put on the design: it finds matching templates, renders each with those photos and your copy, and returns finished images plus a link to keep editing each one. YOU write the query — the catalogue describes each template as Title Case phrases separated by commas, and a query in that register matches markedly better than a sentence: "Birthday Party, Friends, Celebration, Confetti, Party Invite". Look at the photos you were given and let what you see inform it, rather than asking what the design is for. If the photos are on the caller's machine, call upload_images first — the renderer fetches over the network and cannot read a local path. The first design is free and needs no account. search_templates and fill_template are the same work in two steps, for picking the template yourself.
Known tools 4
upload_imagesCall this FIRST when the photos are on the caller's machine rather than already on the web — our renderer fetches over the network and cannot read a local path.
Inferred read-onlycreate_designsThe whole job in one call: give it a SEARCH QUERY you have written, your photo URLs and the words you want on the design, and it finds templates that fit, renders each with your photos and your copy, and returns several finished designs to choose between.
Inferred read-onlyfill_templateRender a finished image: give it a template id from search_templates and the photo URLs to place, and it returns the rendered design.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.zaps]
url = "https://api.zaps.design/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"zaps": {
"type": "http",
"url": "https://api.zaps.design/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: zaps
Remote MCP URL: https://api.zaps.design/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"zaps": {
"url": "https://api.zaps.design/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"zaps": {
"type": "http",
"url": "https://api.zaps.design/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "zaps",
"transport": "streamable-http",
"url": "https://api.zaps.design/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for zaps.design was fetched 2026-10-13T00:16:12.172Z.
zaps.design is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.