Skip to main content
Glama
da-troll

Planhat MCP

by da-troll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Planhat MCP

No user-submitted related servers found.

    Related Servers

    • Zenskar MCP Server by zenskar

      Zenskar MCP Serverofficial

      zenskar
      A
      license
      B
      quality
      A
      maintenance
      Enables natural language interaction with the Zenskar billing platform, covering customers, contracts, invoices, payments, accounting, products, plans, and more.
      100
      27 npm
      1
      MIT

    • TechStart CRM MCP Server

      voyagi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language queries, CRUD operations, and analytics on a PostgreSQL database (Neon) via Claude, supporting customers, tickets, products, and analytics.
      MIT

    • Twenty CRM MCP Server

      mhenry3164
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Twenty CRM with AI assistants like Claude, enabling natural language interactions with customer data. Supports CRUD operations for people, companies, tasks, notes, and advanced search.
      19 npm
      105
      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.3/5.0

    Scored across 60 tools

    Disambiguation5/5

    Each tool operates on a unique entity type (asset, company, contact, conversation, invoice, issue, license, note, opportunity, task, ticket, user) with a specific action (create, delete, get, list, update), ensuring no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a strict and predictable verb_noun pattern using snake_case (e.g., create_asset, delete_company, list_tickets), with no deviations or mixed conventions.

    Tool Count4/5

    60 tools is high but directly corresponds to 12 entities × 5 operations (CRUD+L), which is justified for a full-featured CRM tool. Slightly above the typical 3-15 range but appropriately scoped.

    Completeness5/5

    Each entity has complete lifecycle coverage with create, read (get/list), update, and delete operations. Additional filtering capabilities in list functions further enhance coverage without gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources