Skip to main content
Glama
nmattox

mParticle MCP Server

by nmattox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mParticle MCP Server

No user-submitted related servers found.

    Related Servers

    • Data 360 MCP Server

      pradipsksk
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural-language-driven exploration, querying, and full configuration management of Salesforce Data Cloud / Data 360 via MCP.
      Apache 2.0

    • Alma Atlas

      velum-labs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query live schema, lineage, and query-context across data warehouses, dbt projects, orchestration systems, and BI tools via MCP tools.
      Apache 2.0

    • data-analyst

      AHMED-DEEBB
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to ask bilingual data questions, inspect database tables and schemas, and execute validated read-only SQL through exposed tools.
      MIT

    • Planhat MCP

      da-troll
      A
      license
      B
      quality
      A
      maintenance
      Enables interacting with Planhat customer data via natural language, supporting CRUD operations on companies, contacts, opportunities, notes, conversations, users, assets, issues, tickets, tasks, licenses, and invoices.
      60
      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.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: retrieving all data plans, retrieving a single data plan by ID, and checking API status. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent get_* verb pattern, with clear resource targets (data plans, data plan by id, api status). The naming is predictable and uniform.

    Tool Count4/5

    Three tools is a reasonable count for a narrowly scoped read-only data plan server, though it feels slightly thin when considering the broader mParticle API surface. Each tool is useful and non-redundant.

    Completeness2/5

    The server only supports reading data plans and checking API status, with no create, update, or delete operations. This is a significant gap for managing data plans and leaves the surface incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources