Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "zaps": {
      "type": "http",
      "url": "https://api.zaps.design/mcp"
    }
  }
}

claude mcp add --transport http zaps https://api.zaps.design/mcp

[mcp_servers.zaps]
url = "https://api.zaps.design/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zaps": {
      "type": "remote",
      "url": "https://api.zaps.design/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "zaps": {
      "type": "http",
      "url": "https://api.zaps.design/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=zaps&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLnphcHMuZGVzaWduL21jcCJ9"
}

{
  "servers": {
    "zaps": {
      "type": "http",
      "url": "https://api.zaps.design/mcp"
    }
  }
}

{
  "mcpServers": {
    "zaps": {
      "httpUrl": "https://api.zaps.design/mcp"
    }
  }
}

extensions:
  "zaps":
    enabled: true
    name: "zaps"
    type: streamable_http
    uri: "https://api.zaps.design/mcp"
    timeout: 300

Quality 94 / 100strong

protocol100 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
pass
protocol.list_ttltool list is cacheable (ttlMs 300000)

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene86 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations4 of 4 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: search_templates (idempotentHint); create_designs (idempotentHint); fill_template (idempotentHint); …
pass
tools.token_costabout 1,437 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

4 tools, about 1,437 tokens to load them all · tool set e4e544e8dde2 · checked 2026-10-20 06:17 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 96 / 100

provenance85

liveness100

freshness100

hygiene100

+repository +dns-namespace +website +reachable +uptime-100% +updated-13d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://api.zaps.design/mcp` streamable-http	none	yes	100%	366 ms	2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26	2026-10-20

Tools (4)

`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 search and render together, so there is no need to call search_templates and fill_template yourself. Templates that hold every photo you supplied are preferred, so pass all of them. Photos attached in the conversation go in `photos`; photos already on the web go in `images`. Each returned design spends one agentic token.
`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 `photos`; photos already on the web go in `images`. Each render spends one agentic token.
`search_templates`read-only	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 the occasion, the subject and the mood — "Coffee Shop, Cafe Vibes, Grand Opening, Latte Art, Cafe Aesthetic" rather than "grand opening of a neighbourhood coffee shop". A single word is worst of all. Returns templates with an id to fill and a link a person can open to keep editing.
`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, with nothing else to run. If you would rather upload the bytes yourself, pass `count` instead and you get presigned links to PUT to. Costs nothing either way.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "design.zaps/zaps",
  "title": "Zaps",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://api.zaps.design/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.1.0",
  "repository": {
    "url": "https://github.com/turnip-agentic/zaps-agent",
    "source": "github"
  },
  "websiteUrl": "https://zaps.design",
  "description": "Photos and a brief in, finished social-media designs out. First design free, no account."
}