Skip to main content
Glama
chrischall

iOffice MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to iOffice MCP

No user-submitted related servers found.

    Related Servers

    • airflow-mcp-server

      ssasuoirafen
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude to inspect and operate Apache Airflow over its REST API, providing read tools and safe write operations (gated by read-only mode) for managing DAGs, runs, tasks, and pools.
      14
      MIT

    • Rentvine MCP

      Rentor-CA
      A
      license
      A
      quality
      B
      maintenance
      Provides Claude and any MCP client with live access to property management data, enabling operations on properties, units, leases, tenants, work orders, vendors, accounting, and file attachments through natural language.
      25
      MIT

    • OpenAPI REST MCP Server

      vp2437
      A
      license
      B
      quality
      C
      maintenance
      Enables Claude Desktop to interact with enterprise REST APIs such as Jira, Zoho CRM, Salesforce, SharePoint, Procore, HxGN EAM, and Primavera P6 using OpenAPI/Swagger definitions, with support for various authentication workflows.
      12
      196 npm
      MIT

    • Atlas MCP

      GabrielGB1999
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to interact with Atlas CMMS work orders through its REST API, including listing, creating, updating, changing status, assigning, and generating weekly reports.
      19 npm
      Apache 2.0

    • jira-mcp-server

      hieutv-dng
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude AI and other MCP clients to interact with Jira Server/Data Center through tools like listing issues, logging work, and updating issues, requiring user confirmation for write operations.
      8
      76 npm
      1
      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.6/5.0

    Scored across 53 tools

    Disambiguation5/5

    Each tool maps to a distinct resource plus action (building/floor/space/user/reservation/visitor/maintenance/mail/move), and lifecycle verbs like checkin/checkout, accept/start/complete/archive, and approve/cancel are clearly differentiated. There is minimal risk of misselection even across the many tools.

    Naming Consistency5/5

    Every tool follows the same io_<verb>_<noun> snake_case pattern (io_list_buildings, io_create_floor, io_checkin_visitor, etc.), including a consistent io_healthcheck. No convention mixing is present.

    Tool Count2/5

    53 tools is heavy for effective agent selection, and the count is inflated because each resource repeats the same confirm-token boilerplate across list/get/create/update/delete plus lifecycle transitions. While the breadth is domain-driven, this is well above a comfortable scope.

    Completeness4/5

    Coverage is broad: full CRUD for buildings, floors, spaces, users, reservations, and most lifecycle transitions for maintenance, mail, and moves. Some minor gaps exist (e.g. no delete for visitors/mail/moves and no get for moves by some paths), but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources