Skip to main content
Glama

Related Servers

Alternatives to Vercel MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      Not graded
      maintenance
      An MCP server that provides tools for interacting with Vercel API, enabling management of deployments, DNS records, domains, projects, and environment variables through natural language.
      7
      998 npm
      19
      -
    • A
      license
      A
      quality
      B
      maintenance
      A comprehensive MCP server with 70 tools covering the entire Vercel REST API, enabling management of deployments, projects, environment variables, domains, DNS, aliases, certificates, logs, checks, webhooks, edge config, and teams via a Vercel access token.
      70
      158 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Deployable MCP server for GitHub and Vercel integration. Enables creating repos, pushing multiple files in a single commit, deploying projects to Vercel, managing environment variables, and combined deploy workflows via natural language.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A powerful Model Context Protocol (MCP) server enabling seamless Vercel project management, including deployments, domains, environment variables, and team configurations through Cursor's Composer or Codeium's Cascade.
      998 npm
      63
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A reference MCP server for observing Vercel projects and deployments over stdio. It provides read-only tools to list and fetch details of Vercel projects and deployments.
      4
      75 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server for Vercel Serverless Functions using Streamable HTTP Transport, offering built-in tools for calculations, text analysis, and time utilities, with easy deployment to Vercel.
      -

    TDQS

    B3.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Tools like cancelDeployment, deleteDeployment, getDeployment, and getDeployments target specific actions on deployments, while getDeploymentEvents, getDeploymentFileContents, and listDeploymentFiles handle related but separate data retrieval tasks. The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    The tool names follow a highly consistent verb_noun pattern throughout, using camelCase uniformly. All tools start with a verb (cancel, delete, get, list) followed by a noun (Deployment, DeploymentEvents, DeploymentFileContents, etc.), with no deviations or mixed conventions. This predictability aids in agent comprehension and usage.

    Tool Count5/5

    With 7 tools, the server is well-scoped for managing Vercel deployments. Each tool earns its place by covering essential operations like listing, retrieving, canceling, deleting, and accessing deployment-related data (events, files, contents). This count is neither too thin nor excessive, fitting typical deployment management workflows effectively.

    Completeness4/5

    The tool set provides strong CRUD/lifecycle coverage for deployments, including create (implied via deployment actions), read (get, list), update (cancel as a state change), and delete operations. Minor gaps exist, such as no explicit tool for creating or triggering deployments, but agents can likely work around this given the focus on post-deployment management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues