mcp-hevo-service
Read-only MCP server for Hevo Data API, enabling monitoring of pipelines, objects, destinations, models, and workflows with secure self-hosted credentials.
README
mcp-hevo-service
A read-only MCP server for the Hevo Data public API (v2.0).
Self-hosted: your API credentials stay on your machine and never reach a third party.
Exposes monitoring/inspection tools over pipelines, objects, destinations, models and
workflows. Every tool maps to a GET endpoint, so the server cannot mutate Hevo state.
Quick start
git clone <this-repo>
cd mcp-hevo-service
pip install -r requirements.txt
cp .env.template .env # then fill in your credentials
Configuration
Generate an API Key + Secret in Hevo (Account Settings > API) and set them in .env:
| Variable | Description |
|---|---|
HEVO_API_KEY |
API key (used as the Basic-auth username). |
HEVO_API_SECRET |
API secret (used as the Basic-auth password). |
HEVO_REGION |
One of us, eu, au, in. Selects the base URL https://<region>.hevodata.com/api/public/v2.0. |
Verify
python test_connection.py
Confirms the credentials authenticate against GET /pipelines. No MCP client needed.
Register in an MCP client
{
"mcpServers": {
"hevo": {
"command": "/path/to/python3",
"args": ["/path/to/mcp-hevo-service/server.py"]
}
}
}
Tools
All tools are read-only (GET).
| Tool | Hevo endpoint |
|---|---|
list_pipelines |
GET /pipelines |
get_pipeline |
GET /pipelines/{id} |
get_pipeline_schedule |
GET /pipelines/{id}/schedule |
list_pipeline_objects |
GET /pipelines/{id}/objects |
get_pipeline_object_stats |
GET /pipelines/{id}/objects/{object_name}/stats |
list_destinations |
GET /destinations |
get_destination |
GET /destinations/{id} |
get_destination_table_stats |
GET /destinations/{id}/tables/{table_name}/stats |
list_models |
GET /models |
get_model |
GET /models/{id} |
list_workflows |
GET /workflows |
get_workflow |
GET /workflows/{id} |
Security
- Read-only by construction: the client only issues
GETrequests and no write tool is registered. There is no way to start/pause/edit a pipeline through this server. - Credentials are read from
.env(gitignored) and sent as HTTP Basic auth directly to Hevo. They are not logged and never leave your host.
Notes
Auth and endpoints follow the official Hevo API docs.
Pagination uses limit + starting_after where supported (see per-tool descriptions).
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.