Zaps

What Zaps MCP server does

The Zaps MCP server connects an AI agent to the Zaps design service for creating finished social-media graphics. An agent supplies photos and a short creative brief, and Zaps selects suitable templates, places the images and text, and returns completed designs. Results include a link for continuing edits in the Zaps editor.

Supported output types described by the project include stories, carousels, reel covers, and invitations. The primary workflow is create_designs, which accepts the source photos and brief and returns several design options. The service also provides lower-level operations for discovering templates and rendering a selected one.

How it works

The hosted MCP endpoint is https://api.zaps.design/mcp and uses Streamable HTTP. Clients that support remote MCP servers can connect directly to that URL. The repository also contains client-specific manifests and an installation helper, including a stdio bridge for clients that cannot use the remote connection directly.

Photos can be supplied as links or as inline image bytes through upload_images. Once images are available, an agent can ask create_designs to generate multiple results from a brief. For more control, it can use search_templates to rank the template catalogue against a description, then call fill_template with one selected template and the photos.

The Zaps MCP server does not require a key or account for template searches and the first design. If a request requires authentication, the client opens a Zaps sign-in page using OAuth. The resulting session remains signed in for later requests.

Setup and configuration

Connect a compatible client to https://api.zaps.design/mcp as a remote HTTP MCP server. The repository documents installation paths for Claude Code, Codex, Gemini CLI, Cursor, Windsurf, VS Code with GitHub Copilot, and other agent environments. It also provides a GET-based /make endpoint for producing a design without an MCP client, using a brief, a public photo URL, and optional text.

No environment variables or API keys are documented as required. The service's privacy policy governs how submitted photos and text are collected, used, shared, and retained.

Tools and capabilities

• create_designs: Generate several finished designs from photos and a brief.
• upload_images: Provide photos as URLs or inline bytes; the README describes this operation as free.
• search_templates: Rank available templates according to a natural-language description; free to use.
• fill_template: Render a chosen template with supplied photos.

The Zaps MCP server is suited to workflows where an agent must turn a small set of images and campaign or event text into ready-to-review social assets. It also supports workflows that need template discovery or a specific template render rather than automatic selection.

Limitations and notes

The material does not specify image dimensions, supported file formats, design-count limits, request quotas, or detailed tool schemas. It also does not describe an export API beyond the returned finished images and links to continue editing in the Zaps editor. Review the service privacy policy before sending photos or text that require special handling.