Powerdrill MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POWERDRILL_USER_ID | Yes | A unique identifier for your Powerdrill account | |
| POWERDRILL_PROJECT_API_KEY | Yes | Your authentication token for Powerdrill API access |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose with no overlap: create/delete/list operations target specific resources (datasets, data sources, jobs, sessions) and get_dataset_overview provides unique insight. The resource-action combinations are unambiguous, making tool selection straightforward for an agent.
All tools follow a perfect verb_noun pattern with consistent snake_case: mcp_powerdrill_<verb>_<noun> or mcp_powerdrill_<verb>_<noun>_<modifier>. The naming is highly predictable, using verbs like create, delete, get, list consistently across resources.
With 9 tools, the count is well-scoped for a data processing server. It covers core operations for datasets, data sources, jobs, and sessions without being overwhelming. Each tool appears to earn its place in managing these resources.
The toolset provides strong CRUD coverage for datasets (create, delete, list, get overview) and listing for data sources and sessions, with create operations for jobs and sessions. Minor gaps include no update operations for datasets or data sources, and no delete/get for jobs or sessions, but agents can likely work around these for basic workflows.