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
      11 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.
      10 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
      86 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 follows a resource+action pattern (list/get/create/update/delete per entity, plus explicit state transitions like accept/start/complete/archive for maintenance and checkin/checkout for reservations and visitors). Boundaries between tools are clear: CRUD vs. lifecycle transitions are named distinctly. An agent can reliably pick the right tool for a given intent.

    Naming Consistency4/5

    The overwhelming majority use a consistent io_<verb>_<noun> snake_case pattern (io_list_buildings, io_create_space, io_update_reservation), which is highly predictable. The only deviation is io_healthcheck, which lacks a verb and drops the noun_verb grammar, but it is a single outlier.

    Tool Count3/5

    53 tools is heavy, well above the 25-tool comfort threshold, but the breadth is largely justified by nine distinct facility resources each receiving full CRUD plus workflow transitions. It is borderline: the surface is defensible but large enough to strain context and discovery.

    Completeness4/5

    Core lifecycle coverage is strong across buildings, floors, spaces, users, reservations, visitors, maintenance, mail, and moves, including state transitions and a diagnostic healthcheck. Minor gaps exist: no delete tools for visitors, mail, or moves, and mail/move workflows lack full update coverage, but these are workable around.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources