Vectorize

dev.dudkoPublished by dudko.devOfficial publisherv1.0.0Updated Oct 24, 2026

Hosted MCP front door to the Vectorize API: raster-to-vector tracing to SVG, PDF, EPS or DXF.

The publisher's own server: PDF to Markdown

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Hosted MCP front door to the Vectorize API that lets an assistant prepare raster-to-vector tracing requests producing SVG, PDF, EPS or DXF output.

What you can do
Learn how the Vectorize API works and what its tracing presets, options and limits are (photo, poster, black and white). Validate trace options and get the exact ready-to-run HTTP request, including URL, headers and a curl command, with a short-lived credential. Choose the output format: SVG, PDF, EPS, DXF or JSON. The server does not trace images itself; the assistant runs the returned request wherever the image file is.
When to use it
Use it when you want an assistant to help convert raster images such as PNG or JPG into vector drawings and need the correct Vectorize API request built for you, without pasting an API key.
Requirements
A remote streamable HTTP endpoint at the Vectorize MCP URL, reachable over the network. OAuth 2.1 sign-in with a dudko.dev account; compliant MCP clients discover the authorization server automatically. No API key or environment variables. A Vectorize account plan with remaining tracing quota.
Before you install
Signing in grants the server a 15-minute credential for your account, and each request the assistant runs counts against your account's plan quota; the MCP tools themselves are free. When the quota is spent, requests fail with a plan-used-up error. The server holds no files or content, but the returned request carries a short-lived credential, so treat it as sensitive.

Installation

In SourceWeft

  1. Open Vectorize in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.dudko%2Fvectorize/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "vectorize": {
      "type": "http",
      "url": "https://vectorize.dudko.dev/mcp"
    }
  }
}

README

Vectorize — MCP setup

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.

  • Server: vectorize
  • Transport: streamable HTTP
  • URL: https://vectorize.dudko.dev/mcp
  • Auth: OAuth 2.1 via auth.dudko.dev — you'll be prompted to sign in.

What you can do

Three tools, all free:

ToolWhat it does
api_accessHow the Vectorize API works.
trace_optionsThe presets (photo, poster, black & white), the options and the limits.
api_requestChecks 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.

Install in Claude Code (plugin)

/plugin marketplace add dudko-dev/vectorize-mcp-setup/plugin install vectorize@vectorize/reload-plugins

Then run /mcp and complete the sign-in when prompted.

Prefer not to use the marketplace? Add the server directly:

claude mcp add --transport http vectorize https://vectorize.dudko.dev/mcp

Connect from other clients

Same remote URL, same sign-in — only the config location differs.

Claude Desktop / claude.ai connectors

  1. Open Settings → Connectors → Add custom connector.
  2. Name: Vectorize
  3. URL: https://vectorize.dudko.dev/mcp
  4. Save, then connect and sign in when prompted.

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

json
{  "mcpServers": {    "vectorize": {      "url": "https://vectorize.dudko.dev/mcp"    }  }}

VS Code (GitHub Copilot / MCP) and other clients

json
{  "servers": {    "vectorize": {      "type": "http",      "url": "https://vectorize.dudko.dev/mcp"    }  }}

Authentication

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/mcp

which 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.

Troubleshooting

  • 401 / asked to sign in again — the token expired; reconnect in the client.
  • "plan used up" / 402 — the tracing quota for your account is spent; retrying will not help. See https://auth.dudko.dev/account.
  • Tools don't appear — check the client finished the sign-in (/mcp in Claude Code shows connected).

Support

Source: README.md at commit 4e9170b

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 26, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Dudko integrations

PDF to Markdown

dev.dudkoOfficial publisher

Hosted MCP front door to the pdf2md API that lets an assistant look up conversion options and get a ready-to-run request with a short-lived credential.

Streamable HTTPWeb executableAuth
Files & StorageCredential requiredOct 24, 2026

Tabellum

dev.dudko

Bridges an AI assistant to the Tabellum desktop database client so it can inspect schemas, run reads and draft SQL, with writes approved in the app.

STDIODesktop only
DatabasesNot validated · the server did not complete the MCP handshakeOct 25, 2026

Baton

dev.dudko

Local MCP server for Baton, a git-native API client, letting an assistant read and edit requests, collections, environments and scripts in a YAML workspace.

STDIODesktop only
Files & StorageNot validated · the server did not startOct 25, 2026