Skip to main content
Glama

Related Servers

Alternatives to DemoDesk MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude to answer questions about a small business's own data by providing predefined sales, customer, refund, and inventory tools, plus a guarded read-only SQL query tool with audit logging.
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude Desktop and Claude Code to inspect a Postgres schema and run read-only SQL queries against a demo database through the tools describe_schema and query_readonly. Every proposed query passes the same deterministic guardrails — SELECT-only, allow-listed tables, enforced row limits, statement timeouts and a read-only role — before execution.
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables querying MRR, churn, and revenue from Stripe, Gumroad, and Lemon Squeezy directly inside Claude, allowing natural language questions about business metrics.
      5
      61 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude to answer business questions against a company's retail database — sales summaries, top customers, inventory alerts, customer profiles, and plain-English queries — through read-only SQL tools plus a schema resource and reporting prompt. Access is governed by OAuth 2.1 roles and scopes, column-level PII masking, a SQL guard, rate limits, and audit logging.
      5
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes simulated Salesforce CRM data as MCP tools for Claude Desktop, enabling customer success managers to prioritize at-risk accounts, review opportunities, cases, and Gong notes via natural language.
      -
    • F
      license
      A
      quality
      C
      maintenance
      Enables Claude to manage customers and support tickets through database-backed CRUD tools, contextual customer and knowledge resources, and a reusable ticket-triage prompt.
      13
      -

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly distinct question: recent signups, single-customer lookup by email, and aggregate revenue by plan. There is no realistic way to confuse these three operations, and the descriptions reinforce the separation.

    Naming Consistency3/5

    Only one tool follows a verb_noun pattern (find_customer), while signups_this_week and revenue_summary are noun phrases describing reports. All are snake_case and readable, but the verb convention is not applied uniformly.

    Tool Count3/5

    Three tools is on the thin side for a customer/revenue desk, though it covers the three core read questions. It feels like a minimal dashboard slice rather than a full tool surface.

    Completeness2/5

    The surface is read-only and missing obvious lifecycle operations: no listing or searching all customers, no arbitrary date ranges, no create/update of customer or plan data, and no churn or payment detail. Agents hitting anything beyond the three canned queries will dead-end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues