Skip to main content
Glama

Related Servers

Alternatives to OfficeRnD MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for programmatic read-only access to RiseUp cashflow data, allowing AI assistants to retrieve budget information via natural language.
      2
      107 npm
      25
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that lets AI assistants query the WebHotelier REST API for live hotel data, including property info, room availability, rates, calendars, and offers via natural language tools.
      8
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that enables AI assistants to access Slack workspace data, including channels, messages, threads, and user information.
      21,724 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets AI assistants query your Halaxy practice-management data—appointments, invoices, referrals, and practitioners—via natural language, exposing read-only tools for daily schedules, billing status, and session limits.
      GPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that enables AI assistants to query ServiceNow instances—incidents, changes, users, CMDB—with malformed query linting and injection protection.
      7
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation3/5

    While the five tools map to distinct business domains (billing, collaboration, community, settings, space), there is conceptual overlap—e.g., 'credits' appear in both billing and space tools, and member-related data is scattered across community, billing, and space. The broad 'mega-tool' approach requires agents to infer which domain bucket contains specific entities.

    Naming Consistency4/5

    All tool names follow a consistent pattern of single lowercase nouns representing functional domains (billing, collaboration, community, settings, space). Although they lack action verbs (e.g., 'get_billing'), the naming convention is uniform and predictable.

    Tool Count4/5

    Five tools is a reasonable count for the OfficeRnD domain, falling within the ideal 3-15 range. However, each tool is a heavy aggregate covering multiple entities (e.g., community covers 9+ entity types), suggesting the surface could benefit from finer granularity despite the appropriate total count.

    Completeness2/5

    The tool set is strictly read-only (limited to list, get, status, and coin_stats actions) for a management platform that fundamentally requires write operations. Critical gaps include inability to create/update bookings, members, or invoices, which will prevent agents from completing core coworking management workflows like checking in visitors or reserving rooms.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues