mParticle MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mParticle MCP Server list all data plans in workspace 12345"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mParticle MCP Server
A Model Context Protocol (MCP) server that provides integration with mParticle's Data Planning API. This server allows Claude Desktop and other MCP-compatible clients to interact with your mParticle data plans, retrieve schemas, and manage data governance workflows.
š Features
Data Plan Management: Retrieve all data plans or specific data plans by plan ID from your mParticle workspace
Authentication: Secure authentication with mParticle's API using client credentials stored as environment variables
Automatic Token Management: Handles bearer token refresh and expiration automatically
MCP Standard: Built using FastMCP framework for integration with Claude Desktop or other MCP clients.
Related MCP server: Alma Atlas
š Available Tools
get_all_data_plans
Retrieves all data plans for a specified workspace, including metadata like creation dates, descriptions, and plan status.
Parameters:
workspace_id(string): The mParticle workspace ID (required)
get_data_plan_by_id
Retrieves detailed information about a specific data plan, including version information and data plan elements.
Parameters:
workspace_id(string): The mParticle workspace ID (required)data_plan_id(string): The data plan ID to retrieve (required)
get_api_status
Checks the configuration status of the mParticle API client and credentials.
š ļø Installation
Prerequisites
Python 3.12+: Ensure you have Python 3.12 or higher installed
Claude Desktop: Download and install from the official website
mParticle API Credentials: You'll need an API key and secret from your mParticle account
1. Clone and Setup the Project
git clone <repository-url>
cd mparticle_mcp_server
# Install dependencies using uv (recommended)
uv sync
# Or install using pip
pip install -e .2. Environment Configuration
Create a .env file in the project root or set environment variables:
export MPARTICLE_API_KEY="your_mparticle_api_key"
export MPARTICLE_API_SECRET="your_mparticle_api_secret"Getting mParticle API Credentials:
Log into your mParticle dashboard
Navigate to Settings > Setup > API Keys
Create a new API key with Data Planning permissions
Copy the Key ID (API Key) and Secret
3. Test the Server
Run the server directly to test the configuration:
python mp_data_plan.pyIf configured correctly, you should see:
ā
mParticle API client configured and ready
š Starting MCP server...š§ Claude Desktop Integration
To use this MCP server with Claude Desktop, you need to add it to your Claude Desktop configuration.
Configuration File Location
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Configuration Setup
Locate or create the configuration file at the path above for your operating system.
Add the MCP server configuration:
{
"mcpServers": {
"mparticle": {
"command": "uv",
"args": [
"run",
"python",
"/Users/nmattox/Documents/Apps & Scripts/gen_ai/mparticle_mcp_server/mp_data_plan.py"
],
"env": {
"MPARTICLE_API_KEY": "your_mparticle_api_key",
"MPARTICLE_API_SECRET": "your_mparticle_api_secret"
}
}
}
}Important Notes:
Replace the path in
argswith the absolute path to yourmp_data_plan.pyfileReplace the environment variables with your actual mParticle API credentials
If you don't use
uv, you can replace"command": "uv"with"command": "python"and adjust the args accordingly:
{
"mcpServers": {
"mparticle": {
"command": "python",
"args": [
"/Users/nmattox/Documents/Apps & Scripts/gen_ai/mparticle_mcp_server/mp_data_plan.py"
],
"env": {
"MPARTICLE_API_KEY": "your_mparticle_api_key",
"MPARTICLE_API_SECRET": "your_mparticle_api_secret"
}
}
}
}Restart Claude Desktop after saving the configuration file.
Verify the installation:
Open Claude Desktop
Look for the š plug icon next to the message input
Click it to see available MCP tools - you should see the mParticle tools listed
š” Usage Examples
Once integrated with Claude Desktop, you can use natural language to interact with your mParticle data:
Example Queries:
"Show me all data plans in workspace 12345 - provide summaries for each plan"
Claude will use the
get_all_data_planstool automatically to pull all data plans then create a summary
"Get details for data plan 'mobile-app-schema' in workspace 12345 - share a summary of all data elements and suggest possible mParticle use cases given the plan"
Claude will use the
get_data_plan_by_idtool to pull the specific data plan, create a plan summary, then suggest possible use cases.
"Check if mParticle API is configured properly"
Claude will use the
get_api_statustool
"Given my use case XYZ and data plan xyz-789 for workspace 12345 - what are suggested improvements I can make to the data plan?"
Claude will retrieve the data plan and suggest plan improvements given the use case
šļø Project Structure
mparticle_mcp_server/
āāā mp_data_plan.py # Main MCP server with FastMCP tools
āāā mparticle_api.py # mParticle API client and authentication
āāā main.py # Simple test entry point
āāā pyproject.toml # Project dependencies and metadata
āāā uv.lock # Locked dependencies
āāā README.md # This fileš Related Links
Available Tools
3 toolsget_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
Inputs: workspace_id (required). Returns: result
get_api_statusA
Check the status of mParticle API configuration.
Returns:
Status message indicating if API credentials are configured
Inputs: no named parameters. Returns: result
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
Inputs: data_plan_id (required), workspace_id (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 3 tools
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.
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.
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.
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
Related MCP Connectors
List datasets, schemas, run APL queries, and use prompts for exploration, anomalies, and monitoring.
Query your org's data in natural language ā read-only MCP access to SQL, NoSQL, files & warehouses.
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Query your warehouse or a CSV with Claude/ChatGPT over MCP, governed by table-level ACL + audit.
Related MCP Servers
AlicenseBqualityBmaintenanceEnables AI assistants to interact with Bauplan lakehouse operations, including querying tables, schema inspection, branch management, and pipeline execution.3315MIT- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseBqualityBmaintenanceEnables 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.60MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural-language-driven exploration, querying, and full configuration management of Salesforce Data Cloud / Data 360 via MCP.Apache 2.0