Blender integration through the Model Context Protocol
Nothing to run from here
Zaps is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
4
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Photos and a brief in, finished social-media designs out. First design free, no account.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http zaps-mcp https://api.zaps.design/mcp
# 2 — ask your agent for something these tools do
# search_templates, upload_images, create_designs and 1 more
Zaps costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ZAAll 1 server
zaps1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http zaps-mcp https://api.zaps.design/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 Aest
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many templates to return. Default 5. |
| query | string | yes | Title Case phrases separated by commas, the way the catalogue describes itself. Five or six covering occasion, subject and mood. |
| segment | string | no | Optional shape filter, e.g. story or carousel. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| count | integer | no | Only when uploading the bytes yourself: how many links to mint. |
| files | array | no | The photos themselves, base64 encoded. We store them and hand back a url each. Use this unless you have a reason not to. |
| mimeType | string | no | The images' media type, e.g. image/png or image/jpeg. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | yes | The SEARCH QUERY for the template catalogue — you write it, we do not build it from anything else. Title Case phrases separated by commas, the way the catalogue describes itself: "Birthday Party, Frie |
| count | integer | no | How many finished designs to return. Default 5, at most 10. |
| images | array | no | Publicly reachable image URLs, in placement order. |
| photos | array | no | Photos the person attached in this conversation, in placement order. Use this OR images, not both. |
| segment | string | no | Optional shape filter, e.g. story or carousel. |
| text | array | no | The words to put ON the designs — headline first, then any supporting lines. WRITE THESE YOURSELF from the brief: a template ships with the designer's placeholder copy, and leaving it means a coffee s |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coverId | string | yes | Template id, from a search_templates result. |
| images | array | no | Publicly reachable image URLs, in placement order. |
| photos | array | no | Photos the person attached in this conversation, in placement order. Use this OR images, not both. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Zaps or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Zaps can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.