Skip to main content
Glama
WYRE-AI

Cork MCP Server

Official
by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Cork MCP Server

No user-submitted related servers found.

    Related Servers

    • gorelo-mcp

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Provides read-only visibility into Gorelo PSA data, enabling AI assistants to query tickets, clients, contacts, contracts, assets, and time entries through MCP tools.
      24
      -

    • Telivy MCP Server

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and the WYRE Conduit gateway to access Telivy's security assessment data for MSPs, including external scans, deep-scan risk assessments, device inventory, M365/Google Workspace user exposure, PII summaries, and finding-level details.
      16
      -

    • Autotask MCP Server

      ddurko1950
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to directly query and manage Autotask PSA data through natural language, including ticket triage, time entry creation, company lookups, project management, billing review, and more.
      Apache 2.0
    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.7/5.0

    Scored across 23 tools

    Disambiguation4/5

    Each tool maps to a distinct resource or sub-resource, and descriptions consistently call out the required parent UUIDs (client, integration, invoice) that scope related queries. The only real near-overlap is cork_get_client_devices vs. cork_get_integration_devices, but their client-scoped vs. integration-scoped purposes are clearly explained.

    Naming Consistency4/5

    22 of 23 tools follow the same cork_get_<resource> snake_case pattern, making the naming highly predictable. cork_who_am_i is the single outlier and breaks the verb_noun convention, but it is still recognizable and not confusing.

    Tool Count3/5

    With 23 tools, this server sits at the heavy end of what an agent can comfortably scan. The breadth is defensible because the domain covers clients, compliance, vulnerabilities, integrations, billing, and installers, but several of these areas could have been consolidated.

    Completeness4/5

    The read-only surface is well connected: client UUIDs feed devices, inboxes, domains, and compliance; integration UUIDs feed integration subresources; and invoice UUIDs feed line items. Minor gaps exist, such as no claims endpoint despite the score history referencing claims, and no action-oriented tools like software install dispatch, but core query workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources