Skip to main content
Glama

Related Servers

Alternatives to Vercel MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides various tools for interacting with the Vercel API, enabling management of deployments, DNS records, domains, projects, and environment variables through natural language commands.
      7
      998 npm
      20
      MIT
    • 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
      Not graded
      quality
      D
      maintenance
      MCP Server simplifies the implementation of the Model Context Protocol by providing a user-friendly API to create custom tools and manage server workflows efficiently.
      14 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A template for running Model Context Protocol servers on Vercel with Redis support, allowing developers to deploy their custom tools, prompts, and resources using the MCP TypeScript SDK.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP Server provides a simpler API to interact with the Model Context Protocol by allowing users to define custom tools and services to streamline workflows and processes.
      20 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A serverless, multi-tenant implementation of MCP servers that runs on Vercel with fluid compute mode, allowing multiple users to connect to the same endpoint while maintaining session state through Redis.
      12
      -

    TDQS

    C2.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different aspects of deployments. The actions (cancel, delete, get, list) are well-differentiated and operate on specific resources like deployments, events, files, or file contents with no overlap in functionality.

    Naming Consistency4/5

    The naming follows a consistent verbNoun pattern with camelCase throughout, such as 'getDeployment' and 'listDeploymentFiles'. The only minor deviation is 'getDeploymentEvents' which uses plural 'Events' while others use singular or plural appropriately, but overall the pattern is highly predictable and readable.

    Tool Count5/5

    With 7 tools, the count is well-scoped for managing deployments in a Vercel context. Each tool earns its place by covering essential operations like listing, retrieving, canceling, deleting, and accessing deployment details and files, without being excessive or insufficient for the domain.

    Completeness4/5

    The toolset provides strong coverage for deployment lifecycle management, including create (implied by deployment actions), read (get/list), update (cancel as a state change), and delete operations. A minor gap is the lack of explicit tools for creating or updating deployments, but core workflows are well-supported with no dead ends.