Analyze Powerdrill Data with Natural Language
An MCP server letting Claude analyze and query Powerdrill datasets using natural-language questions.
1.0.0Add to Favorites
Why it matters
Interact with Powerdrill datasets using natural language queries. Analyze data and execute complex operations without writing code.
Outcomes
What it gets done
List and manage Powerdrill datasets and data sources.
Create and execute jobs for data analysis via natural language.
Upload local files as new data sources to Powerdrill datasets.
Group related analysis jobs into sessions.
Source
Get it from source
Spark does not host a copy of it.
Open sourceReports
Agent outcome reports
No reports yet
Capabilities
Tools your agent gets
Lists available datasets from your Powerdrill account
Retrieves detailed information about a specific dataset
Creates a job for analyzing data using natural language questions
Creates a new session for grouping related jobs
Lists data sources in a specific dataset
Lists sessions from your Powerdrill account
Creates a new dataset in your Powerdrill account
Creates a new data source by uploading a local file to a dataset
Overview
An MCP server for Powerdrill that lets Claude list, create, and query datasets using natural-language analysis jobs. Use it when Claude needs to analyze or manage Powerdrill datasets with an active Powerdrill Team account.
What it does
An MCP server for Powerdrill datasets that lets Claude analyze data and execute queries using natural-language questions, including listing datasets and data sources, creating new datasets, uploading local files as data sources, and running natural-language analysis jobs grouped into sessions.
When to use - and when NOT to
Use this when Claude needs to list or query Powerdrill datasets, create a new dataset or upload a file as a data source, or run a natural-language analysis job against existing data - for example "What datasets are available in my Powerdrill account?" or "Create a new dataset called 'Sales Analytics'." It requires an active Powerdrill Team account with a User ID and Project API Key - it is not usable without a Powerdrill subscription.
Capabilities
mcp_powerdrill_list_datasets: lists available datasets from your Powerdrill account.mcp_powerdrill_get_dataset_overview: retrieves detailed information about a specific dataset.mcp_powerdrill_create_job: creates a job to analyze data using natural-language questions.mcp_powerdrill_create_session: creates a new session for grouping related jobs.mcp_powerdrill_list_data_sources: lists data sources within a specific dataset.mcp_powerdrill_list_sessions: lists sessions from your Powerdrill account.mcp_powerdrill_create_dataset: creates a new dataset in your Powerdrill account.mcp_powerdrill_create_data_source_from_local_file: uploads a local file to a specified dataset as a new data source.
How to install
Via Smithery:
npx -y @smithery/cli install @powerdrillai/powerdrill-mcp --client claude
Or install globally (npm install -g @powerdrillai/powerdrill-mcp), run directly with npx @powerdrillai/powerdrill-mcp, or build from source and run the provided setup.sh. Configure Claude Desktop or Cursor with:
{
"powerdrill": {
"command": "npx",
"args": [
"-y",
"@powerdrillai/powerdrill-mcp@latest"
],
"env": {
"POWERDRILL_USER_ID": "your_actual_user_id",
"POWERDRILL_PROJECT_API_KEY": "your_actual_project_api_key"
}
}
}
Both POWERDRILL_USER_ID and POWERDRILL_PROJECT_API_KEY are required for authentication, and video tutorials are provided for setting up a Powerdrill Team account and its API keys.
Who it's for
Data teams already on a Powerdrill Team plan who want Claude or another MCP client to list, create, and query Powerdrill datasets using natural language instead of the Powerdrill web UI. Typical prompts include "Show me all my datasets", "Upload the file /Users/your_name/Downloads/sales_data.csv to dataset {dataset_id}", and "Tell me more about this dataset: {dataset_id}", and the server integrates directly with both Claude Desktop and other MCP-compatible clients such as Cursor, using the same NPX-based configuration in each case. Beyond the Node-based MCP server itself, the wider Powerdrill ecosystem also offers separate Node.js and Python client options, and the project notes require an active Powerdrill Team account rather than a free-tier account, since the underlying dataset and job APIs are gated behind that plan.
Source README
Powerdrill MCP Server
A Model Context Protocol (MCP) server that provides tools to interact with Powerdrill datasets, authenticated with Powerdrill User ID and Project API Key.
Please go to https://chat.powerdrill.ai/ for AI data analysis individually or use with your Team.
If you have the Powerdrill User ID and Project API Key of your Team, you can manipulate the data via Powerdrill open sourced web clients:
- Node.js edtion: https://flow.powerdrill.ai/, or play with the open source web client https://github.com/powerdrillai/powerdrill-flow.
- Python edtion: https://powerdrill-flow.streamlit.app/, or play with the open source web client https://github.com/powerdrillai/powerdrill-flow-streamlit.
Features
- Authenticate with Powerdrill using User ID and Project API Key
- List available datasets in your Powerdrill account
- Get detailed information about specific datasets
- Create and run jobs on datasets with natural language questions
- Integration with Claude Desktop and other MCP-compatible clients
Installation
Installing via Smithery
To install powerdrill-mcp for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @powerdrillai/powerdrill-mcp --client claude
From npm
# Install globally
npm install -g @powerdrillai/powerdrill-mcp
# Or run directly with npx
npx @powerdrillai/powerdrill-mcp
From Source
Clone this repository and install dependencies:
git clone https://github.com/yourusername/powerdrill-mcp.git
cd powerdrill-mcp
npm install
CLI Usage
If installed globally:
# Start the MCP server
powerdrill-mcp
If using npx:
# Run the latest version
npx -y @powerdrillai/powerdrill-mcp@latest
You'll need to configure environment variables with your Powerdrill credentials before running:
# Set environment variables
export POWERDRILL_USER_ID="your_user_id"
export POWERDRILL_PROJECT_API_KEY="your_project_api_key"
Or create a .env file with these values.
Prerequisites
To use this MCP server, you'll need a Powerdrill account with valid API credentials (User ID and API Key). Here's how to obtain them:
- Sign up for a Powerdrill Team account if you haven't already
- Navigate to your account settings
- Look for the API section where you'll find your:
- User ID: A unique identifier for your account
- API Key: Your authentication token for API access
First, watch this video tutorial on how to create your Powerdrill Team:
Then, follow this video tutorial for setting up your API credentials:
Quick Setup
The easiest way to set up the server is using the provided setup script:
# Make the script executable
chmod +x setup.sh
# Run the setup script
./setup.sh
This will:
- Install dependencies
- Build the TypeScript code
- Create a
.envfile if it doesn't exist - Generate configuration files for Claude Desktop and Cursor with the npx-based configuration (recommended)
Then edit your .env file with your actual credentials:
POWERDRILL_USER_ID=your_actual_user_id
POWERDRILL_PROJECT_API_KEY=your_actual_project_api_key
Also update the credentials in the generated configuration files before using them.
Manual Installation
If you prefer to set up manually:
# Install dependencies
npm install
# Build the TypeScript code
npm run build
# Copy the environment example file
cp .env.example .env
# Edit the .env file with your credentials
Usage
Running the server
npm start
Integrating with Claude Desktop
- Open Claude Desktop
- Go to Settings > Server Settings
- Add a new server with one of the following configurations:
Option 1: Using npx (Recommended)
{
"powerdrill": {
"command": "npx",
"args": [
"-y",
"@powerdrillai/powerdrill-mcp@latest"
],
"env": {
"POWERDRILL_USER_ID": "your_actual_user_id",
"POWERDRILL_PROJECT_API_KEY": "your_actual_project_api_key"
}
}
}
Option 2: Using node with local installation
{
"powerdrill": {
"command": "node",
"args": ["/path/to/powerdrill-mcp/dist/index.js"],
"env": {
"POWERDRILL_USER_ID": "your_actual_user_id",
"POWERDRILL_PROJECT_API_KEY": "your_actual_project_api_key"
}
}
}
- Save the configuration
- Restart Claude Desktop
Integrating with Cursor
- Open Cursor
- Go to Settings > MCP Tools
- Add a new MCP tool with one of the following configurations:
Option 1: Using npx (Recommended)
{
"powerdrill": {
"command": "npx",
"args": [
"-y",
"@powerdrillai/powerdrill-mcp@latest"
],
"env": {
"POWERDRILL_USER_ID": "your_actual_user_id",
"POWERDRILL_PROJECT_API_KEY": "your_actual_project_api_key"
}
}
}
Option 2: Using node with local installation
{
"powerdrill": {
"command": "node",
"args": ["/path/to/powerdrill-mcp/dist/index.js"],
"env": {
"POWERDRILL_USER_ID": "your_actual_user_id",
"POWERDRILL_PROJECT_API_KEY": "your_actual_project_api_key"
}
}
}
- Save the configuration
- Restart Cursor if needed
Using the tools
Once connected, you can use the Powerdrill tools in your conversations with Claude Desktop, Cursor, Cline, Windsurf, etc.:
- List datasets:
What datasets are available in my Powerdrill account?orShow me all my datasets - Create dataset:
Create a new dataset called "Sales Analytics"orMake a new dataset named "Customer Data" with description "Customer information for 2024 analysis" - Create data source from local file:
Upload the file /Users/your_name/Downloads/sales_data.csv to dataset {dataset_id}orAdd my local file /path/to/customer_data.xlsx to my {dataset_id} dataset - Get dataset overview:
Tell me more about this dataset: {dataset_id}orDescribe the structure of dataset {dataset_id} - Create a job:
Analyze dataset {dataset_id} with this question: "How has the trend changed over time?"orRun a query on {dataset_id} asking "What are the top 10 customers by revenue?" - Create a session:
Create a new session named "Sales Analysis 2024" for my data analysisorStart a session called "Customer Segmentation" for analyzing market data - List data sources:
What data sources are available in dataset {dataset_id}?orShow me all files in the {dataset_id} dataset - List sessions:
Show me all my current analysis sessionsorList my recent data analysis sessions
Available Tools
mcp_powerdrill_list_datasets
Lists available datasets from your Powerdrill account.
Parameters:
limit(optional): Maximum number of datasets to return
Example response:
{
"datasets": [
{
"id": "dataset-dasfadsgadsgas",
"name": "mydata",
"description": "my dataset"
}
]
}
mcp_powerdrill_get_dataset_overview
Gets detailed overview information about a specific dataset.
Parameters:
datasetId(required): The ID of the dataset to get overview information for
Example response:
{
"id": "dset-cm5axptyyxxx298",
"name": "sales_indicators_2024",
"description": "A dataset comprising 373 travel bookings with 15 attributes...",
"summary": "This dataset contains 373 travel bookings with 15 attributes...",
"exploration_questions": [
"How does the booking price trend over time based on the BookingTimestamp?",
"How does the average booking price change with respect to the TravelDate?"
],
"keywords": [
"Travel Bookings",
"Booking Trends",
"Travel Agencies"
]
}
mcp_powerdrill_create_job
Creates a job to analyze data with natural language questions.
Parameters:
question(required): The natural language question or prompt to analyze the datadataset_id(required): The ID of the dataset to analyzedatasource_ids(optional): Array of specific data source IDs within the dataset to analyzesession_id(optional): Session ID to group related jobsstream(optional, default: false): Whether to stream the resultsoutput_language(optional, default: "AUTO"): The language for the outputjob_mode(optional, default: "AUTO"): The job mode
Example response:
{
"job_id": "job-cm3ikdeuj02zk01l1yeuirt77",
"blocks": [
{
"type": "CODE",
"content": "```python\nimport pandas as pd\n\ndef invoke(input_0: pd.DataFrame) -> pd.DataFrame:\n...",
"stage": "Analyze"
},
{
"type": "TABLE",
"url": "https://static.powerdrill.ai/tmp_datasource_cache/code_result/...",
"name": "trend_data.csv",
"expires_at": "2024-11-21T09:56:34.290544Z"
},
{
"type": "IMAGE",
"url": "https://static.powerdrill.ai/tmp_datasource_cache/code_result/...",
"name": "Trend of Deaths from Natural Disasters Over the Century",
"expires_at": "2024-11-21T09:56:34.290544Z"
},
{
"type": "MESSAGE",
"content": "Analysis of Trends in the Number of Deaths from Natural Disasters...",
"stage": "Respond"
}
]
}
mcp_powerdrill_create_session
Creates a new session to group related jobs together.
Parameters:
name(required): The session name, which can be up to 128 characters in lengthoutput_language(optional, default: "AUTO"): The language in which the output is generated. Options include: "AUTO", "EN", "ES", "AR", "PT", "ID", "JA", "RU", "HI", "FR", "DE", "VI", "TR", "PL", "IT", "KO", "ZH-CN", "ZH-TW"job_mode(optional, default: "AUTO"): Job mode for the session. Options include: "AUTO", "DATA_ANALYTICS"max_contextual_job_history(optional, default: 10): The maximum number of recent jobs retained as context for the next job (0-10)agent_id(optional, default: "DATA_ANALYSIS_AGENT"): The ID of the agent
Example response:
{
"session_id": "session-abcdefghijklmnopqrstuvwxyz"
}
mcp_powerdrill_list_data_sources
Lists data sources in a specific dataset.
Parameters:
datasetId(required): The ID of the dataset to list data sources frompageNumber(optional, default: 1): The page number to start listingpageSize(optional, default: 10): The number of items on a single pagestatus(optional): Filter data sources by status: synching, invalid, synched (comma-separated for multiple)
Example response:
{
"count": 3,
"total": 5,
"page": 1,
"page_size": 10,
"data_sources": [
{
"id": "dsource-a1b2c3d4e5f6g7h8i9j0",
"name": "sales_data.csv",
"type": "CSV",
"status": "synched",
"size": 1048576,
"dataset_id": "dset-cm5axptyyxxx298"
},
{
"id": "dsource-b2c3d4e5f6g7h8i9j0k1",
"name": "customer_info.xlsx",
"type": "EXCEL",
"status": "synched",
"size": 2097152,
"dataset_id": "dset-cm5axptyyxxx298"
},
{
"id": "dsource-c3d4e5f6g7h8i9j0k1l2",
"name": "market_research.pdf",
"type": "PDF",
"status": "synched",
"size": 3145728,
"dataset_id": "dset-cm5axptyyxxx298"
}
]
}
mcp_powerdrill_list_sessions
Lists sessions from your Powerdrill account.
Parameters:
pageNumber(optional): The page number to start listing (default: 1)pageSize(optional): The number of items on a single page (default: 10)search(optional): Search for sessions by name
Example response:
{
"count": 2,
"total": 2,
"sessions": [
{
"id": "session-123abc",
"name": "Product Analysis",
"job_count": 3,
"created_at": "2024-03-15T10:30:00Z",
"updated_at": "2024-03-15T11:45:00Z"
},
{
"id": "session-456def",
"name": "Financial Forecasting",
"job_count": 5,
"created_at": "2024-03-10T14:20:00Z",
"updated_at": "2024-03-12T09:15:00Z"
}
]
}
mcp_powerdrill_create_dataset
Creates a new dataset in your Powerdrill account.
Parameters:
name(required): The dataset name, which can be up to 128 characters in lengthdescription(optional): The dataset description, which can be up to 128 characters in length
Example response:
{
"id": "dataset-adsdfasafdsfasdgasd",
"message": "Dataset created successfully"
}
mcp_powerdrill_create_data_source_from_local_file
Creates a new data source by uploading a local file to a specified dataset.
Parameters:
dataset_id(required): The ID of the dataset to create the data source infile_path(required): The local path to the file to uploadfile_name(optional): Custom name for the file, defaults to the original filenamechunk_size(optional, default: 5MB): Size of each chunk in bytes for multipart upload
Example response:
{
"dataset_id": "dset-cm5axptyyxxx298",
"data_source": {
"id": "dsource-a1b2c3d4e5f6g7h8i9j0",
"name": "sales_data_2024.csv",
"type": "FILE",
"status": "synched",
"size": 2097152
},
"file": {
"name": "sales_data_2024.csv",
"size": 2097152,
"object_key": "uploads/user_123/sales_data_2024.csv"
}
}
Troubleshooting
If you encounter issues:
- Make sure your environment variables are set correctly in
.env - Check that the server starts successfully with
npm start - Verify your Claude Desktop configuration points to the correct file paths
- Check the console output for any error messages
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.

