Skip to main content
Glama
Sign In
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Heliyos MCP server

No user-submitted related servers found.

    Related Servers

    • MCP Suite CRM

      rehanhaider
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with a CRM covering companies, people, leads, deals, and more, with role checks, scoped agent keys, approval gates, and a shared audit trail.
      AGPL 3.0

    • HubSpot MCP Server

      TomaszSheikh2801
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with CRM contacts, companies, activity, and conversations, and to perform semantic search across previously retrieved data.
      -

    • crm-cases

      sm2774us
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and IDE clients to query CRM case, customer, and order data and to perform guarded actions such as issuing refunds, updating cases, and drafting customer emails.
      6
      MIT

    • ParcelPilot MCP Server

      PraneethGoud04
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve customer, order, ticket, policy, and agreement information, and to prepare or execute state-changing support actions like escalations and follow-ups with confirmation and access control.
      -

    • com.addtocrm/crm

      crm-inputs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to look up work contact and company details, search prospects, check existing CRM records, and add or update people and companies in a connected CRM without exposing CRM credentials.
      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.8/5.0

    Scored across 73 tools

    Disambiguation4/5

    Tools are organized by resource and action, and the descriptions explicitly differentiate near-neighbors such as records_list vs lookup vs get, records_timeline vs records_events, and global scouts vs company scouts. Some overlap remains around finding records and initiating AI work, but an agent can generally choose correctly.

    Naming Consistency4/5

    Nearly all tools follow a clear heliyos_<resource>_<verb> snake_case pattern with plural resource nouns. A few actions break the create/update/delete convention, such as knowledge_entries_set, files_upload, signals_mark_read, team_members_change_role, and ask, but the overall pattern is still predictable.

    Tool Count1/5

    With 73 tools, the surface is far beyond the well-scoped 3-15 range and exceeds the 50-tool extreme threshold. The broad workspace domain explains some breadth, but the set should be consolidated or split into narrower servers for agent usability.

    Completeness4/5

    Core domains have strong coverage: records, fields, tasks, notes, labels, workers, scouts, knowledge, files, team, reviews, and runs all expose appropriate read/write or lifecycle operations. Minor gaps exist, such as no custom-object schema mutation, no run cancellation, and no file update operation, but they are mostly workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources