edgedelta-mcp-server
Official first-party Edge Delta MCP server. Self-hosted (Docker container or stdio transport) — no vendor-hosted remote URL is published. Exposes Edge Delta pipeline management, live-capture, and processor dry-run tooling to MCP clients (Claude, Cursor, etc.).
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport stdio
Tools
get_pipelines— Discover pipelines in the organization.get_pipeline_config— Read a pipeline's current configuration.get_pipeline_history— Read a pipeline configuration's version history.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 pipeline 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 live before/after capture task on a pipeline.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.test_pipeline_node— Dry-run a full processor node against sample logs, offline.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.