The **Edge Delta MCP Server** is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server that provides seamless
The Edge Delta MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with Edge Delta APIs, enabling advanced automation and interaction capabilities for. The edgedelta mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
The server ships on a container image as mcp/edgedelta, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Everything the assistant can do here goes through one of these:
validate_pipeline_config — Validate a config YAML without saving it. Returns {valid, reason}save_pipeline_config — Save the full config YAML as a new version (does not deploy)deploy_pipeline — Deploy a saved version to the fleetrevert_pipeline — Roll back to a previously saved versionadd_pipeline_source — Add a data source node to a pipelinestart_pipeline_capture — Start a capture task on a pipeline (duration, optional node list, max items)get_pipeline_capture_status — Poll per-agent status for a capture taskget_pipeline_capture_results — Fetch captured before/after samples per nodeget_pipeline_capture_task — Show the currently active capture task, if anytest_pipeline_ottl — Dry-run OTTL statements against sample OTEL log items; returns the transformed itemstest_pipeline_node — Dry-run a full processor node of any type (log_to_metric, log_to_pattern, extract_metric, parse_json_attributes, grok, mask, …); returns the items itYou will need 4 environment variables: ED_API_TOKEN, ED_ORG_ID, YOUR_TOKEN, YOUR_ORG_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Edgedelta's toolset — validate_pipeline_config, save_pipeline_config, deploy_pipeline and 8 more — is a fair guide to whether it matches your workflow. It is maintained by edgedelta; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Edgedelta's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| validate_pipeline_config | Validate a config YAML without saving it. Returns {valid, reason}. |
| save_pipeline_config | Save the full config YAML as a new version (does **not** deploy). |
| deploy_pipeline | Deploy a saved version to the fleet. |
| revert_pipeline | Roll back to a previously saved version. |
| add_pipeline_source | Add a data source node to a pipeline. |
| start_pipeline_capture | Start a capture task on a pipeline (duration, optional node list, max items). |
| get_pipeline_capture_status | Poll per-agent status for a capture task. |
| get_pipeline_capture_results | Fetch captured before/after samples per node. |
| get_pipeline_capture_task | Show the currently active capture task, if any. |
| test_pipeline_ottl | Dry-run OTTL statements against sample OTEL log items; returns the transformed items. |
| test_pipeline_node | Dry-run a full processor node of any type (log_to_metric, log_to_pattern, extract_metric, parse_json_attributes, grok, mask, …); returns the items it emits per output path. |
{
"mcpServers": {
"edgedelta": {
"command": "docker",
"args": ["run", "-i", "--rm", "mcp/edgedelta"],
"env": {
"ED_API_TOKEN": "your-value",
"ED_ORG_ID": "your-value",
"YOUR_TOKEN": "your-value",
"YOUR_ORG_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ED_API_TOKEN | Credential the server authenticates with. | Yes |
| ED_ORG_ID | Configuration value read at startup. | Optional |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_ORG_ID | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.