Seedwall MCP
Related Servers
Alternatives to Seedwall MCP
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables agents to read and edit node-based design canvases, generate images, video, code, SVG, shaders, and HTML screens, and run saved workflows with results placed beside their prompts and references.MIT- AlicenseNot gradedqualityBmaintenanceConnects AI assistants to a running generative art studio over its HTTP API, letting them read live canvas state and parameters, move sliders, switch engines, save and apply presets, highlight controls, and capture PNG snapshots. It can also read and rewrite an engine's GLSL or TypeScript source so a new version hot-reloads into the canvas.MIT
- AlicenseAqualityBmaintenanceConnects Claude Code to image generation models (OpenAI GPT Image 2, Google Nano Banana) for generating, editing, and converting images via natural language.638 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude Code to create and edit presentation-grade visualizations such as cloud architecture diagrams, charts, KPI dashboards, and poster infographics, with auto-layout, themes, and export to SVG, PNG, JPG, and PDF.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to generate images from HTML/CSS templates, manage templates and galleries, and bulk-generate from datasources via the pixel-img API, exposed over SSE for remote hosting.3 npmMIT
- AlicenseBqualityDmaintenanceExposes Replicate's FLUX image generation models to Claude, enabling text-to-image generation, image variations, inpainting, and edge-guided creation with 6 different FLUX models.21MIT
TDQS
Scored across 4 tools
list_looks and describe_look are clearly split (all looks vs. one look's parameters), and render is a distinct parameterized generation tool. The only blurry boundary is seed, whose name reads like a render parameter and whose relationship to looks is unspecified, so an agent could hesitate between render and seed for a 'random image' request.
list_looks and describe_look follow a clean verb_noun pattern, but render drops the object and seed is a bare noun that doesn't follow the verb convention at all. The names remain readable, but the set mixes conventions rather than holding one pattern.
Four tools for a focused render/discovery service is lean but defensible: discovery (list/describe) plus two generation entry points. It is slightly thin, and seed arguably duplicates a mode that could live inside render, but nothing is bloated.
The core lifecycle is covered: discover looks and themes/sizes, inspect parameters and presets, then render to SVG/PNG with a studio edit link or grab a fixed/daily seed image. Minor gaps exist — no explicit standalone enumeration of sizes/themes, no way to combine a seed with a specific look, and no batch render — but agents can work around them.