Skip to main content
Glama
nmattox

mParticle MCP Server

by nmattox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MPARTICLE_API_KEYYesYour mParticle API key
MPARTICLE_API_SECRETYesYour mParticle API secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_all_data_plansA
Get all data plans for a workspace.

This tool retrieves all data plans from mParticle's Data Planning API.
Data plans define the expected structure and validation rules for your events.

Args:
    workspace_id: The mParticle workspace ID (required)
    
Returns:
    JSON string containing all data plans and their metadata
    
Raises:
    Exception: If API credentials are missing or API request fails
get_data_plan_by_idA
Get a specific data plan by ID.

This tool retrieves detailed information about a specific data plan from mParticle's Data Planning API.
Data plans define the expected structure and validation rules for your events.

Args:
    workspace_id: The mParticle workspace ID (required)
    data_plan_id: The data plan ID to retrieve (required)
    
Returns:
    JSON string containing the data plan details and metadata
    
Raises:
    Exception: If API credentials are missing or API request fails
get_api_statusA
Check the status of mParticle API configuration.

Returns:
    Status message indicating if API credentials are configured

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_mparticle_configGet mParticle API configuration status.
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