DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Vercel Mcp — DSH Plugin for DeepSeek Harness
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
V

dsh-vercel-mcp

Vercel Mcp

Vercel MCP connection for DeepSeek Harness: official OAuth 2.0 flow (dynamic client registration + PKCE) against mcp.vercel.com, Vercel API tools under mcp__vercel__*, and a web settings panel

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:zhengjy01/dsh-vercel-mcp#3b8f421221064c9a623d687314a570c922d356c5
READMECompatibilityVersions

Compatibility and provenance

Vercel Mcp is published as dsh-vercel-mcp and currently resolves to version 0.1.0. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
web
Release source
github
Registry updated
8/30/2026

Versions

0.1.0stable
8/30/2026

Related plugins

Loading related plugins…

Latest
0.1.0
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
web
License
MIT
Source
github
GitHub
★ 0
Weekly downloads
0
Last push
9/11/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in integrations-communication.

Acp App@deepseek-ai/dsh-acp-appThe dsh ACP profile bundle: automation-only JSON-RPC stdio and process lifecycle over dsh-baseIm@xmanrui/dsh-im把十一种 IM 渠道和公网 AI Office 接入本机 DeepSeek Harness。 Connect eleven IM channels and a public AI Office to a local DeepSeek Harness.Pocketdsh-pocketPut DeepSeek Harness in your pocket: one package, one settings page, and scan a QR code on your phone to access DSH on your computer in sync (LAN + public network, real-time screen mirroring).DSCODE@toddzheng024/dscode-bundleA complete DeepSeek coding agent with persistent shell, Ultra collaboration and automatic permission review.

README

English | 中文

dsh-vercel-mcp

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.

Why this plugin

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.

Install

# 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).

Authorize

Two ways, both starting the same OAuth flow against Vercel:

  1. Settings panel (Web GUI → 设置 → Vercel MCP): click 开始授权, the browser opens Vercel's consent page, and the loopback callback completes automatically. 测试连接 lists the discovered tools.
  2. Chat: ask the agent to run vercel_mcp_oauth_start, open the returned authorizeUrl, or paste the callback code back into vercel_mcp_oauth_finish.

Tools

Agent-facing helpers (mounted on ctx.tools):

toolwhat it does
vercel_mcp_statusauthorization + connection state, tool count (no secrets)
vercel_mcp_oauth_startbegin the OAuth flow, return the browser URL
vercel_mcp_oauth_finishmanual code-paste fallback
vercel_mcp_testconnect and list the MCP server's tools
vercel_mcp_clearwipe credentials and disconnect

Plus the MCP server's own tools as mcp__vercel__*.

API routes

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/status
  • POST /api/dsh-vercel-mcp/oauth/start
  • GET /api/dsh-vercel-mcp/oauth/callback (browser landing)
  • POST /api/dsh-vercel-mcp/oauth/finish
  • POST /api/dsh-vercel-mcp/oauth/refresh
  • POST /api/dsh-vercel-mcp/test
  • POST /api/dsh-vercel-mcp/clear

Development

pnpm 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)

License

MIT