
Zaps
design.zapsv1.1.0Updated Oct 7, 2026
Photos and a brief in, finished social-media designs out. First design free, no account.
Overview
Lets an assistant turn user photos and a written brief into finished social-media designs such as stories, carousels, reel covers and invites.
- What it does
- Zaps is a hosted design service exposed as a remote MCP server. Its main tool, create_designs, takes photos plus a brief, picks matching templates, places the photos and text, and returns finished images with a link to keep editing each one in the Zaps editor. Supporting tools upload local photos, rank the template catalogue by a description, and render one chosen template with photos.
- When to use it
- Useful when an assistant should produce ready-to-post social graphics from a user's own photos and a short brief, without the user opening a design tool first. Search and the first design are free with no account, so it is easy to try before committing.
- Requirements
- A remote MCP endpoint over Streamable HTTP; no package install is needed. No key or signup is required to start, but calls that need an account trigger a browser OAuth sign-in to Zaps, after which the session stays signed in. Photos must be reachable as links or uploaded through the upload tool.
Installation
In SourceWeft
- Open Zaps in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"zaps": {
"type": "http",
"url": "https://api.zaps.design/mcp"
}
}
}README
Zaps for agents
Turn someone's photos into finished social-media designs (stories, carousels, reel covers, invites) from any AI agent. Give it photos and a brief, and Zaps picks matching templates, places the photos and the words, and returns finished images with a link to keep editing each one in the Zaps editor.
- No key, no signup to start. Searching and the first design are free with no account.
- Signing in is a browser click. When a call needs an account, your client opens a Zaps sign-in page (OAuth). After that it stays signed in.
- One hosted server:
https://api.zaps.design/mcp(MCP, Streamable HTTP).
Install
No install at all? One GET makes a design:
https://api.zaps.design/make?brief=Birthday%20Party,%20Friends&photo=<public photo url>&text=Happy%20Birthday.
In a browser, https://api.zaps.design/make is a form that takes photo files.
What is in here
Tools
Docs: https://zaps.design/docs/api · Privacy: https://zaps.design/privacy · Terms: https://zaps.design/terms · Support: https://zaps.design/support
Privacy Policy
The photos and text you send are used to make your designs. How Zaps collects, uses, shares and retains data is set out in its privacy policy: https://zaps.design/privacy. Contact: https://zaps.design/support.
Source: README.md at commit abeb485
Tools
0Version history
1- v1.1.0LatestOct 7, 2026

