design.zaps/zaps · v1.1.0 · design
Zaps is healthy: it completed an MCP handshake in 3502 ms and exposes 4 tools. It scores 62/100.
Photos and a brief in, finished social-media designs out. First design free, no account.
Endpoint: https://api.zaps.design/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| health | 17 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 7 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 8 / 10 |
Scoring v0.3, computed 2026-10-15T02:36:22.716Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T23:10:36.059Z | Healthy | 3502 |
search_templates | Find design templates. YOU write the query, and its wording decides the match: the catalogue describes each template as Title Case phrases separated by commas, and a query in that same register scores about 0.11 higher than the same intent written as a sentence. Write five or six phrases covering th |
upload_images | Call 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. Simplest way: read each file and pass it in `files` as base64; the reply gives you a publicUrl per photo to hand straight to create_designs |
create_designs | The 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. Use this when someone wants options — it is |
fill_template | Render a finished image: give it a template id from search_templates and the photo URLs to place, and it returns the rendered design. Photos are placed into the template's image slots in the order given, so pass them in the order you want them to appear. Photos attached in the conversation go in `ph |