Every MCP server sits between your AI platform and your automation infrastructure. Every node query, every workflow operation, every template search passes through it. If that server transmits usage data — even anonymised analytics — your operational patterns are no longer private.
For builders who chose self-hosted n8n specifically to keep their automation data off third-party servers, the MCP layer introduces a new surface that most implementations handle poorly. ag8n was built to handle it properly.
Why MCP Privacy Matters More Than You Think
Consider what an MCP server can observe. Which nodes you query most frequently. Which workflow patterns you build. Which templates you search for. How often you deploy. When you deploy. The error patterns in your configurations. The scale and complexity of your automation infrastructure. None of this is your n8n data in the traditional sense. All of it is operationally sensitive.
A compliance provider querying VAT-related nodes and EU marketplace templates reveals their business focus. A financial services firm building webhook-triggered data processing pipelines reveals their operational architecture. The metadata is the intelligence.
The Telemetry Problem in Open-Source MCP
The czlonkowski/n8n-mcp project is the most widely adopted MCP implementation for n8n, with over 2,200 users and support for 1,084 nodes. It is well-engineered, actively maintained, and genuinely useful. It also ships with telemetry subsystems that collect usage data.
The telemetry can be disabled via configuration. For many users, this is sufficient. For users who require verifiable privacy — regulated industries, compliance-sensitive operations — a configuration toggle is not sufficient. Verifiable privacy requires the telemetry code to not exist in the codebase at all.
How ag8n Handles Privacy
ag8n is forked from czlonkowski/n8n-mcp with a specific architectural decision: all telemetry subsystems are removed at the fork level. Not disabled. Not toggled off. Removed from the source code before compilation.
This means there is no telemetry code in the compiled JavaScript that runs on your infrastructure. No analytics endpoints. No usage tracking functions. No data transmission logic. The codebase can be audited to verify this.
The fork also removes Docker dependencies. ag8n compiles to clean JavaScript that runs wherever Node.js runs. No containers. No orchestration overhead. No additional attack surface.
The Self-Hosted Privacy Chain
Infrastructure layer. Your server, your network, your data. Self-hosted n8n runs on infrastructure you control.
Application layer. n8n itself. The open-source codebase is auditable.
Integration layer. This is where MCP sits. The server that bridges your AI platform to your n8n instance. ag8n secures this layer.
AI platform layer. Google Antigravity. What ag8n controls is ensuring that no additional data about your n8n environment is transmitted through the MCP layer.
Practical Privacy Architecture
No telemetry in the codebase. Auditable. The compiled JavaScript contains no analytics, tracking, or data transmission code.
No Docker dependencies. The MCP server runs as a Node.js process on your infrastructure.
No cloud dependencies. The server does not require internet access to function.
Local-only operation. Node queries, template searches, workflow operations — all processed locally.
Who Needs This Level of Privacy
Compliance-sensitive operations. Financial services, healthcare data processing, legal document workflows.
Client-facing automation. Agencies and consultants building workflows for clients who require demonstrable privacy controls.
Self-hosted infrastructure by design. Organisations that chose self-hosted n8n as a deliberate architectural decision to maintain data sovereignty.
ag8n takes a position: your n8n instance is your business. The MCP layer should add capability without adding surveillance. Zero telemetry. Zero tracking. Zero data transmitted anywhere.
£9.95. One-time purchase. Privacy that is architectural, not configurable.
Privacy That Is Architectural, Not Configurable
ag8n's MCP server has zero telemetry in the codebase. Not disabled — removed. Your n8n data stays on your infrastructure. £9.95. No subscription.
Get ag8n — £9.95