genart-mcp
Related Servers
Alternatives to genart-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP Server for ShaderToy, a site where people share GLSL shader. This MCP server allows LLMs to make complex shader they aren't normally capable of.51MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to create and run Processing sketches directly through natural language commands.4MIT
- AlicenseAqualityCmaintenanceMCP server that turns AI into an SVG artist. One rendering engine with a rich JSON schema, AI controls all design parameters. Renders animated SVGs with CSS @keyframes and SMIL animations. Supports 16+ element types, parametric curves, pattern groups, gradient/filter/clip/mask definitions, and PNG preview. No external dependencies, runs locally via npx.3127 npm31MIT
- AlicenseNot gradedqualityBmaintenanceProvides an MCP server that lets AI models build and patch typed SVG scenes, compute exact Bézier geometry, perceptual gradients and keyframe or spring motion, then rasterize the result to PNG or animated APNG and diff renders pixel-by-pixel. Ten math-backed tools replace guessed coordinates with deterministic geometry, color and animation output.MIT
- AlicenseCqualityBmaintenanceMCP server for creating pixel art, characters, and scenes for Aseprite, generating deterministic plans and Godot-compatible manifests.18516 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA MCP server that bridges web canvas with local Codex/Claude, exposing 23 tools for reading, creating, modifying, connecting, and generating canvas content via local HTTP bridge and stdio MCP.AGPL 3.0
TDQS
Scored across 312 tools
The set contains literal near-duplicates: design_add_water_surface vs design_design_add_water_surface, design_add_reflection vs design_design_add_water_reflection, design_add_shore vs design_design_add_water_shoreline, and three separate fog/mist/haze layers (design_add_fog, design_add_fog_layer, design_add_mist, design_add_haze). Many families also blur together (design_set_blend vs design_set_blend_mode, design_add_pattern vs design_create_pattern, design_add_plant vs design_randomize_plant vs design_create_garden). With 312 tools an agent must disambiguate between near-identical layer constructors, which is a real misselection risk.
Most tools use a snake_case design_* prefix, but a large block uses a doubled prefix (design_design_add_water_*), a whole sketch/workspace family has no prefix (save_sketch, create_sketch, merge_sketches), and one tool is underscore-prefixed (_get_sketch_data). Verb conventions are also mixed, with add_, create_, apply_, set_, generate_, and bare nouns used interchangeably for similar operations.
312 tools is an extreme mismatch for any single agent-facing server, far beyond what can be reliably discovered or selected from a single tool list. The surface should be decomposed into several scoped servers (sketch lifecycle, layers/filters, plants, terrain, typography, etc.).
Coverage of the generative-art/layered-design domain is exceptionally broad: sketch CRUD, workspace management, layer lifecycle, filters, typography, tracing, plants, terrain, water, atmosphere, patterns, symbols, animation, and export are all present. Gaps are minor (e.g. no undo/history or layer-rename operation), so agents can work around them.