IMG.LY CodeSign MCP alternatives
6 servers that overlap with IMG.LY CodeSign MCP. Compared on install command, provenance, and the tags they share — not on a feature checklist nobody maintains.
What these have in common
All of them overlap with IMG.LY CodeSign MCP on at least one capability tag. Overlap is not equivalence: two servers can both say "database" and solve different problems. Read the full entry for what the current one is actually for before switching.
Side by side
| Server | Install | Source | Shared tags |
|---|---|---|---|
| IMG.LY CodeSign MCP | npx -y @imgly/codesign-mcp | Official | design, images, generation |
| Meshy MCP | npx -y @meshy-ai/meshy-mcp-server | Official | 3d, generation, assets |
| Hugeicons MCP | npx -y @hugeicons/mcp-server | Official | icons, design, assets |
| Figma MCP | npx -y figma-developer-mcp | Community | figma, design, tokens |
| Figma Console MCP | npx -y figma-console-mcp | Community | figma, design, tokens |
| Excalidraw MCP | npx -y mcp-excalidraw-server | Community | diagrams, excalidraw, design |
| Kie.ai MCP | npx -y @felores/kie-ai-mcp-server | Community | image, video, generation |
How to choose
Prefer the official server when one exists, unless its install path or auth model does not fit. Prefer the smaller surface area: a server that exposes four tools you use beats one that exposes forty you do not, because every definition costs context on every request.