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

    • 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

    • trustflow-companyx

      SakJaeLim
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language queries to be converted into policy-verified SQL, vector search, and knowledge graph plans, with evidence-backed answers and an audit log.
      1
      Apache 2.0
    • Atlas MCP by AtlasDevHQ

      Atlas MCPofficial

      AtlasDevHQ
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language querying of SQL databases and REST APIs through the MCP protocol, grounded in a semantic layer.
      1,395
      1
      AGPL 3.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.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