Gemini Image vs Build123d MCP
A side-by-side look at the Gemini Image and Build123d MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gemini Image for art & culture work as a local process; choose Build123d MCP for art & culture over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gemini Image when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GEMINI_API_KEY.
Choose Build123d MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 47/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | GEMINI_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 108 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gemini Image | View Build123d MCP |
Tools & capabilities
Gemini Image tools
No tool names declared yet. Check the project README from the listing page.
Build123d MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gemini Image
{
"mcpServers": {
"gemini-image": {
"command": "npx",
"args": [
"-y",
"@jimothy-snicket/gemini-image-mcp"
],
"env": {
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE"
}
}
}
}
Build123d MCP
{
"mcpServers": {
"pzfreo-build123d-mcp": {
"url": "http://localhost:8000/mcp"
}
}
}
Frequently asked questions
Gemini Image is categorized under Art & Culture and uses a local stdio subprocess. Build123d MCP belongs to Art & Culture and uses a remote HTTP/SSE transport. Pick Gemini Image for art & culture work and Build123d MCP for art & culture.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Gemini Image is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Build123d MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gemini-image and pzfreo-build123d-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gemini Image has a quality signal of 47/100 (Fair) with 3 views, 0 installs and 1 GitHub stars. Build123d MCP has 53/100 (Good) with 1 views, 0 installs and 108 GitHub stars.
