Hevo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEVO_REGION | Yes | Your Hevo region (us, eu, in, or asia) | |
| HEVO_API_KEY | Yes | Your Hevo API key | |
| HEVO_API_SECRET | Yes | Your Hevo 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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pipelinesA | List all data pipelines in the Hevo account (id, name, source/destination type, status). |
| get_pipelineA | Get full configuration and status of a single pipeline. |
| create_pipelineA | Create a new Hevo pipeline. The shape of |
| enable_pipelineA | Enable (resume) a paused pipeline. |
| disable_pipelineC | Disable (pause) a running pipeline. |
| resync_pipelineA | Resync a pipeline by restarting its historical load. If drop_and_load=true, destination tables are dropped and recreated (destructive). If false (default), tables are kept and only differences are updated. |
| update_pipeline_configA | Modify pipeline-level config (name, schedule, query mode, auto-mapping). Send only fields to change. |
| update_source_configA | Modify the SOURCE configuration of an existing pipeline (host, port, database, credentials, etc.). |
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 8 tools
Each tool targets a distinct action and object (list, get, create, enable, disable, resync, update pipeline config, update source config). The two update tools are clearly separated by scope (pipeline-level vs source-level) with descriptions that prevent confusion.
All tool names follow a consistent verb_noun pattern in snake_case: list_pipelines, get_pipeline, create_pipeline, enable_pipeline, disable_pipeline, resync_pipeline, update_pipeline_config, update_source_config. The naming style and verb choice are uniform.
With 8 tools, the server covers the essential pipeline management operations without bloat. Each tool serves a distinct, necessary purpose for managing Hevo pipelines.
The surface covers list, get, create, enable/disable, resync, and update operations, which are core to pipeline management. The only notable gap is the absence of a delete_pipeline tool, which is a minor lifecycle gap that agents can work around by disabling pipelines.