Vectorize

dev.dudko由 dudko.dev 發布官方發布者v1.0.0更新於 Oct 24, 2026

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

發布方自己的服務：PDF to Markdown

已驗證Streamable HTTP可網頁執行開發者工具媒體與設計

服務詳細資訊

識別碼: dev.dudko/vectorize
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 26, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 dudko.dev，且該網域同時執行其端點。這可以確認發布者，但並不代表該服務的工具是安全的。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.dudko%2Fvectorize.svg)](https://sourceweft.com/mcp/dev.dudko%2Fvectorize?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

Vectorize API 的託管 MCP 入口，讓助理準備點陣轉向量的描摹請求，輸出 SVG、PDF、EPS 或 DXF。

可以做什麼: 了解 Vectorize API 的運作方式，以及相片、海報、黑白等描摹預設、選項與限制。驗證描摹選項，並取得可直接執行的完整 HTTP 請求，包含 URL、標頭與 curl 指令，附帶短期憑證。選擇輸出格式：SVG、PDF、EPS、DXF 或 JSON。伺服器本身不進行影像描摹；助理會在影像檔案所在位置執行回傳的請求。
適用情境: 當你希望助理協助把 PNG、JPG 等點陣圖轉成向量圖，並需要自動產生正確的 Vectorize API 請求、又不想手動貼上 API 金鑰時使用。
執行需求: 需要可連上網路的遠端 streamable HTTP 端點（Vectorize MCP 位址）。使用 dudko.dev 帳號透過 OAuth 2.1 登入；相容的 MCP 用戶端會自動探索授權伺服器。無需 API 金鑰或環境變數。需要 Vectorize 帳戶方案仍有描摹額度。

安裝前請注意

登入後伺服器會取得你帳戶的 15 分鐘憑證，助理執行的每次請求都會計入帳戶方案額度；MCP 工具本身免費。額度用完時請求會因方案已用盡而失敗。伺服器不保存檔案或內容，但回傳的請求帶有短期憑證，應視為敏感資訊。

安裝

在 SourceWeft 中

開啟儀表板中的 Vectorize，將其新增到工作區。
連接所需的憑證。它們會被私密儲存，絕不會在公開頁面上展示。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/dev.dudko%2Fvectorize/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。客戶端會在首次連接時完成 OAuth 登入。

{
  "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:

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

Install in Claude Code (plugin)

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

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

Connect from other clients

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

Claude Desktop / claude.ai connectors

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

Cursor

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

VS Code (GitHub Copilot / MCP) and other clients

json

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

{  "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).