Kubernetes Troubleshoot vs Vercel MCP Pro
A side-by-side look at the Kubernetes Troubleshoot and Vercel MCP Pro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kubernetes Troubleshoot for cloud platforms work as a local process; choose Vercel MCP Pro for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kubernetes Troubleshoot when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
KUBECONFIG, ALLOWED_NAMESPACES. - You want tools like
get_pod_status, get_pod_logs, get_pod_events.
Choose Vercel MCP Pro when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VERCEL_TOKEN. - You want tools like
list_deployments, get_deployment, create_deployment.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 49/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | KUBECONFIGALLOWED_NAMESPACES | VERCEL_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | 70 |
| Full listing | View Kubernetes Troubleshoot | View Vercel MCP Pro |
Tools & capabilities
Kubernetes Troubleshoot tools 16
get_pod_statusPhase, conditions, container statuses, QoS class and node for a podget_pod_logsRecent log lines from a pod container. Content is untrusted — see [Reading `get_pod_logs` output](#reading-get_pod_logs-output)get_pod_eventsRecent events for a pod, newest first, with `total_availablelist_podsPods in a namespace with phase, restart count and readinessget_node_statusConditions, capacity, allocatable, taints and roles for a nodelist_nodesCluster nodes with readiness, roles, age and kubelet versionget_deployment_statusReplica counts, conditions and rollout strategylist_deploymentsDeployments in a namespace with replica counts and availabilityget_statefulset_statusReplica counts, revisions and update strategyget_daemonset_statusScheduling counts and update strategyget_serviceType, ClusterIP, ports, selector and ready endpoint countget_endpointsReady and not-ready endpoint addresses backing a service- +4 more on the listing page
Vercel MCP Pro tools 70
list_deploymentsList deployments, most recent first. Filter by project, target (production/preview), state, or time window. Use this to see deploy history and find a deployment id.get_deploymentGet full details of one deployment by id or URL (state, build, meta, aliases).create_deploymentCreate a new deployment. The simplest path is to deploy from a connected Git source: pass `name` (project) and a `gitSource` ({ type, repoId/org+repo, ref }). For file-based deploys, provide `files`. For most workflows the /vercel CLI skill is easier — use this when you need API-driven, headless deploys.cancel_deploymentCancel an in-progress (BUILDING/QUEUED) deployment.delete_deploymentDelete a deployment by id (or by URL via the `url` param).get_deployment_eventsGet the build/runtime event log of a deployment (this is where build logs and errors live). Use to diagnose failed builds and runtime bugs. Returns log lines with text, type and timestamps.list_deployment_filesList the file tree of a deployment.get_deployment_file_contentsGet the contents of a single file within a deployment by file id.promote_deploymentPromote an existing deployment to production for a project (instant promotion, no rebuild). This is how you ship a previously-built preview to prod.rollback_deploymentRoll a project's production back to a previous deployment (instant rollback). Pass the deployment id you want to roll back to.get_promote_aliasesCheck the status of the most recent promote/rollback for a project (which aliases were assigned).list_projectsList projects in the account/team. Optionally filter by name or repo.- +58 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kubernetes Troubleshoot
{
"mcpServers": {
"kubernetes-troubleshoot": {
"command": "uvx",
"args": [
"pre-commit"
],
"env": {
"KUBECONFIG": "YOUR_KUBECONFIG_HERE",
"ALLOWED_NAMESPACES": "YOUR_ALLOWED_NAMESPACES_HERE"
}
}
}
}
Vercel MCP Pro
{
"mcpServers": {
"vercel-mcp-pro": {
"command": "npx",
"args": [
"-y",
"vercel-mcp-pro"
],
"env": {
"VERCEL_TOKEN": "YOUR_VERCEL_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Kubernetes Troubleshoot is categorized under Cloud Platforms and uses a local stdio subprocess. Vercel MCP Pro belongs to Cloud Platforms and uses a local stdio subprocess. Pick Kubernetes Troubleshoot for cloud platforms work and Vercel MCP Pro for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kubernetes Troubleshoot has no declared pricing — check the project's own site. Vercel MCP Pro has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kubernetes-troubleshoot and vercel-mcp-pro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kubernetes Troubleshoot has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Vercel MCP Pro has 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars.