MCP server for Quiver AI — generate and vectorize SVGs from Claude Code
Server has three well-named tools with explicit input schemas and descriptions. Naming follows verb_noun convention (quiver_list_models, quiver_generate_svg, quiver_vectorize_image). Descriptions are present and moderately detailed. However, parameter descriptions are minimal, and output schemas are not explicitly documented. Error handling is functional but lacks recovery guidance for specific error conditions. The server implements proper secret injection (QUIVERAI_API_KEY via environment variable) and includes HTTP status code handling (401, 402, 429). Overall structure is sound but several parameters lack detailed guidance on constraints, ranges, and format expectations.
Generate SVG vector graphics from a text prompt using Quiver AI.
List all models available via Quiver AI, including supported operations and pricing.
Convert a raster image (PNG, JPEG, WebP) into an editable SVG using Quiver AI.
Output schemas not explicitly documented. Tools return summary objects (savedFiles, usage) but LLMs cannot predict exact field structure, types, or whether usage object is always present. This breaks downstream tool chaining and forces LLMs to guess at response shape.
Parameter 'instructions' (quiver_generate_svg) and 'auto_crop' (quiver_vectorize_image) lack format/constraint guidance. 'instructions' is a free-form string with no guidance on length or style expectations. 'auto_crop' boolean is well-typed but description does not explain the visual impact or when to use it.
Error handling returns formatted text but does not provide actionable recovery guidance for all error paths. The 429 (rate limit) error says 'Wait and try again' but does not specify a backoff window. 402 (insufficient credits) points to a URL but agent cannot act on it. Generic API errors ('Quiver AI error: ...') lack context for recovery.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 68 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 45 | - | v1 |
Parameter 'references' (quiver_generate_svg) accepts array of strings but description says 'Up to 4 reference image URLs or local file paths', the type should enforce maxItems: 4 constraint in schema. This prevents LLMs from passing more than 4 and invites API errors.
Default output_path behavior is stated in description ('default: public/assets/<auto>.svg') but not enforced in schema, if LLM omits output_path, tool generates a default name but description does not guarantee this is safe or idempotent across calls. No documentation of what '<auto>' expands to.