The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Vectorize listing page.
Connect your AI assistant to Vectorize — raster images (PNG, JPG, …) traced into vector drawings: SVG, PDF, EPS or DXF — through our hosted Model Context Protocol (MCP) server. Sign in once with your dudko.dev account; no API key to paste.
The server is the front door to the Vectorize HTTP API, not a tracer: a picture never travels through the model or through the server. The assistant asks for a request, and runs it wherever the image is.
vectorizehttps://vectorize.dudko.dev/mcpauth.dudko.dev — you'll be prompted to sign in.Three tools, all free:
| Tool | What it does |
|---|---|
api_access | How the Vectorize API works. |
trace_options | The presets (photo, poster, black & white), the options and the limits. |
api_request | Checks trace options and returns the exact request — URL, headers, a curl command — with a 15-minute credential for your account. Output: svg, pdf, eps, dxf or json. |
Then run /mcp and complete the sign-in when prompted.
Prefer not to use the marketplace? Add the server directly:
Same remote URL, same sign-in — only the config location differs.
Vectorizehttps://vectorize.dudko.dev/mcp~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):
The server is an OAuth 2.1 resource server. The first call answers 401 with a
WWW-Authenticate header pointing at its protected-resource metadata:
https://vectorize.dudko.dev/.well-known/oauth-protected-resource/mcpwhich names https://auth.dudko.dev as the authorization server (scope
usage). Compliant MCP clients discover this automatically — you only need the
server URL, and you sign in with your dudko.dev account. Tokens are
audience-bound to https://vectorize.dudko.dev/mcp and are refused anywhere else.
The server itself carries no files and no content: its tools return a ready-to-run HTTP request with a short-lived credential (15 minutes, good for this API only) for the account you signed in as. Your assistant runs that request wherever the file is, and the API answers the caller directly. Each request counts against your account's plan like any other API call; the MCP tools themselves are free.
401 / asked to sign in again — the token expired; reconnect in the client.402 — the tracing quota for your account is spent;
retrying will not help. See https://auth.dudko.dev/account./mcp in
Claude Code shows connected).