dsh-vercel-mcp
DeepSeek Harness 的 Vercel MCP 连接：针对 mcp.vercel.com 的官方 OAuth 2.0 流程（动态客户端注册 + PKCE）、mcp__vercel__* 下的 Vercel API 工具，以及 Web 设置面板
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:zhengjy01/dsh-vercel-mcp#3b8f421221064c9a623d687314a570c922d356c5Vercel Mcp 以 dsh-vercel-mcp 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →English | 中文
Vercel MCP connection for DeepSeek Harness (DSH): the official Vercel API MCP server (mcp.vercel.com) with the full OAuth 2.0 client dance — dynamic client registration, PKCE S256, loopback callback on the GUI's own web server, refresh-token grant — plus a web settings panel.
Once authorized, the Vercel platform tools (deployments, projects, domains,
environment variables, DNS records, deploy code, and more) become available
in agent sessions as mcp__vercel__*, auto-refreshing its token on 401.
DSH's built-in @deepseek-ai/dsh-mcp-client supports static headers only —
it cannot complete the OAuth flow that mcp.vercel.com requires
(WWW-Authenticate: Bearer realm="OAuth"). This plugin implements the
OAuth client itself on the official @modelcontextprotocol/sdk primitives,
so the connection is genuinely authenticated, not token-pasted.
# local development (link)
dsh plugin --profile web add link:/path/to/dsh-vercel-mcp
The bundle patch mounts the plugin row automatically; a Host restart is
needed for the layer to compose. Tokens live in
~/.dsh/dsh-vercel-mcp.json (mode 0600).
Two ways, both starting the same OAuth flow against Vercel:
vercel_mcp_oauth_start, open the
returned authorizeUrl, or paste the callback code back into
vercel_mcp_oauth_finish.Agent-facing helpers (mounted on ctx.tools):
| tool | what it does |
|---|---|
vercel_mcp_status | authorization + connection state, tool count (no secrets) |
vercel_mcp_oauth_start | begin the OAuth flow, return the browser URL |
vercel_mcp_oauth_finish | manual code-paste fallback |
vercel_mcp_test | connect and list the MCP server's tools |
vercel_mcp_clear | wipe credentials and disconnect |
Plus the MCP server's own tools as mcp__vercel__*.
All loopback-only (127.0.0.1), except the OAuth callback which accepts
the cross-site landing from mcp.vercel.com while still verifying the
OAuth state:
GET /api/dsh-vercel-mcp/statusPOST /api/dsh-vercel-mcp/oauth/startGET /api/dsh-vercel-mcp/oauth/callback (browser landing)POST /api/dsh-vercel-mcp/oauth/finishPOST /api/dsh-vercel-mcp/oauth/refreshPOST /api/dsh-vercel-mcp/testPOST /api/dsh-vercel-mcp/clearpnpm install
npm run typecheck
npm run test # offline store/provider smoke
DSH_VERCEL_MCP_LIVE=1 npm run test # live OAuth phase-1 against mcp.vercel.com
npm run build # tsc declarations + tsdown (lib/ + lib/client.js)
MIT