Skip to main content
Glama
SaaS_A MCP Server

SaaS_A MCP Server

by nori1173-ops

Related Servers

Alternatives to SaaS_A MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only lookup and analysis of SaaS applications, transactions, invoices, spend, renewals, and people, including spend summaries, upcoming renewals, and missing-invoice checks, through an MCP client.
      7
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Microsoft Intune through the Microsoft Graph API, enabling MCP clients to query managed devices, apps, compliance policies, and configuration profiles.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for the Action1 RMM REST API, enabling access to endpoints, missing updates, vulnerabilities, installed software, policies, automations, and reports.
      21
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server that allows AI assistants to query and monitor KVM Fleet devices, audit logs, and console sessions through the official REST API.
      5
      8 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to read facilities, devices, live values, history, and alarms from a Cloud Studio Gear IoT account, filtered to the user's permissions and strictly read-only.
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to a Mailfact tenant, letting users list domains, sending sources, and aggregate reports, and query DMARC alignment, reporter coverage, and record-level data through MCP tools. It returns counts and rows only, without recommending policies or scoring domains.
      9
      36 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource: users, tenants, groups, devices, formats, three dashboard scopes, and observation data export. There is no overlap or ambiguity between any of the nine tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: eight are list_<resource> and the sole exception is export_observation_data, which still uses the same verb_noun structure. No mixed conventions.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range. Each tool covers a distinct aspect of the SaaS domain, so none feel redundant or unnecessary.

    Completeness4/5

    The tool set provides comprehensive read/list operations for all core entities (tenants, users, devices, groups, formats, dashboards) plus a data export function. It lacks single-item detail retrieval and any create/update/delete operations, but this appears to be an intentional read-only server design.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues