Skip to main content
Glama
pedromfs

segment-mcp

by pedromfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to segment-mcp

No user-submitted related servers found.

    Related Servers

    • segment-mcp

      katekruger
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only querying of Twilio Segment workspaces to audit which destinations receive which events, trace event routing and governance, identify stale or ungoverned sources, and check destination delivery health, with permanent safeguards against data deletion.
      25 PyPI
      MIT

    • Google Ads MCP

      zelentsov-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only inspection of Google Ads accounts through MCP, including account inventory, reporting, metadata, change history, and safe GAQL queries.
      Apache 2.0

    • Juror Cloud MCP

      marilynnovikov953
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to inspect workspace-scoped findings and hosted runs, list workspaces, and prepare or, after explicit confirmation, start or rerun existing hosted reviews without exposing raw diffs, full reports, artifacts, screenshots, credentials, or prompt text.
      2 npm
      -

    • remote-workspace-mcp

      HANA225-HUB
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to private filesystem workspaces through MCP, allowing clients to list, inspect, read, and search files without uploading the workspace or opening inbound firewall ports.
      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 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: list/get pairs for sources, destinations, functions, and tracking plans are cleanly separated, and api_get is clearly scoped as a read-only escape hatch. There is no meaningful overlap between any tools.

    Naming Consistency4/5

    The verb_noun pattern (list_sources, get_function, list_tracking_plans) is applied consistently across eight tools. The only deviation is api_get, which inverts the convention, but it is a distinct escape-hatch concept and remains readable.

    Tool Count5/5

    Nine tools is well within the sweet spot and each earns its place with a clear resource-verb pairing. Nothing feels redundant or padded.

    Completeness4/5

    The server is explicitly read-only, and for that scope it offers list+get coverage for the four main resource families plus a generic GET escape hatch for unmodeled paths. No write operations exist, but that is by design rather than an oversight.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources