Skip to main content
Glama
Sign In
@hyperstar/mcp

@hyperstar/mcp

Official
by Hyperstar-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @hyperstar/mcp

No user-submitted related servers found.

    Related Servers

    • orbit-mcp

      Devotel
      A
      license
      Not graded
      quality
      D
      maintenance
      A stdio-based MCP server that exposes the Orbit CPaaS API as tools, enabling sending SMS, managing campaigns, and other communication workflows through natural language in MCP clients.
      7 npm
      MIT

    • mcp-hey

      Sealjay
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server for Hey.com email - read, search, send, reply, and manage the screener via stored session cookies. Runs over stdio, stores no credentials.
      37
      13
      MIT

    • @nightsquawktech/gohighlevel

      NightSquawk
      A
      license
      A
      quality
      B
      maintenance
      Stdio MCP server for curated GoHighLevel API v2 coverage, enabling create, update, and delete operations on custom fields, contacts, opportunities, tags, conversations, calendars, and more, with safe guarded destructive tools requiring explicit confirmation.
      56
      16 npm
      2
      AGPL 3.0

    • GHL Coaching MCP Server

      Jadelaawar42027
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools to interact with GoHighLevel CRM data, including contacts, conversations, call transcripts, broker lead overviews, pipelines/opportunities, and task creation. Supports both stdio and HTTP transports for local and remote use.
      ISC

    • connectif-mcp

      Yoryoboy
      A
      license
      C
      quality
      B
      maintenance
      Minimal MCP server exposing the Connectif HTTP API to MCP clients over stdio, enabling operations like contacts, purchases, products, exports, imports, workflows, and more.
      12
      6 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

    B3.1/5.0

    Scored across 59 tools

    Disambiguation4/5

    Most tools target a distinct resource+action pair (campaigns, roster creators, email waves, inbox threads, files, imports, usage) and the descriptions draw the boundaries explicitly, e.g. dry-run gates vs. real sends vs. job status reads. A few near-neighbors could still be confused at a glance: get_campaign_email_wave vs list_campaign_email_waves, get_campaign_workflow_counts vs get_campaign_performance, and list_campaign_creator_performance vs list_campaign_video_performance.

    Naming Consistency4/5

    The surface follows a predictable verb_noun snake_case pattern (list_*, get_*, create_*, update_*, cancel_*, start_*, check_*), with matching get/cancel pairs for each job type. The only deviations are the two 'hyperstar_' prefixed entries (hyperstar_whoami, get_hyperstar_workflow_guide), which break the verb-first convention.

    Tool Count2/5

    59 tools for one creator-marketing platform is heavy; whole clusters (email waves, imports, files, uploads, usage) each contribute 4-6 closely related tools. The domain is broad enough to justify many operations, but the number of parallel job-status/cancel/prepare variants makes the set hard to hold in context.

    Completeness4/5

    Coverage is deep: discovery/search, campaign lifecycle, roster edits, email unlock and send gates, inbox triage and reply, forms CRUD, file upload/download, CSV import, and usage checks are all present with terminal-state reads. Minor gaps remain, such as no campaign deletion/archival tool and no draft workflow for inbox replies before send.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources