Skip to main content
Glama
felixjoy89hevo

Hevo MCP Server

by felixjoy89hevo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Hevo MCP Server

No user-submitted related servers found.

    Related Servers

    • GHL MCP Server

      mnewby20305
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to manage GoHighLevel CRM contacts, pipelines, and workflows through natural language commands.
      20 npm
      MIT

    • lyra-mcp

      Ralf090102
      F
      license
      A
      quality
      B
      maintenance
      Enables Claude to inspect, configure, run, and modify individual RAG/agent pipeline stages (retrieve, rerank, generate, eval) as structured typed tool calls, and execute the full pipeline end to end.
      5
      -

    • hetzner-mcp-server

      nityeshaga
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude Code to manage Hetzner Cloud servers, including creating, deleting, powering on/off, and rebooting servers, as well as managing SSH keys and listing resources.
      14
      9 npm
      1
      MIT

    • mcp-openhexa

      mcrimi
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with OpenHEXA platform through Claude Desktop, allowing users to query workspaces, list datasets, search pipelines, and view pipeline runs using natural language.
      1
      -

    • Pipedrive MCP

      expertintegrado
      A
      license
      B
      quality
      F
      maintenance
      Enables natural language interaction with Pipedrive CRM via Claude Code, allowing users to manage deals, contacts, activities, and more through conversational commands.
      26
      11 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action and object (list, get, create, enable, disable, resync, update pipeline config, update source config). The two update tools are clearly separated by scope (pipeline-level vs source-level) with descriptions that prevent confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: list_pipelines, get_pipeline, create_pipeline, enable_pipeline, disable_pipeline, resync_pipeline, update_pipeline_config, update_source_config. The naming style and verb choice are uniform.

    Tool Count5/5

    With 8 tools, the server covers the essential pipeline management operations without bloat. Each tool serves a distinct, necessary purpose for managing Hevo pipelines.

    Completeness4/5

    The surface covers list, get, create, enable/disable, resync, and update operations, which are core to pipeline management. The only notable gap is the absence of a delete_pipeline tool, which is a minor lifecycle gap that agents can work around by disabling pipelines.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources