Heimdall MCP Server

Transparent MCP proxy with OpenTelemetry tracing and configurable storage

Local serverstdioTypeScript

What is the Heimdall MCP MCP server?

Connect Heimdall MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Transparent MCP proxy with OpenTelemetry tracing and configurable storage. The heimdall mcp mcp server is what makes that connection.

What the server does

Transparent proxy for any MCP server. Intercepts all JSON-RPC messages, measures latency, stores traces in a configurable database, and enforces per-server allow/deny policies — without touching the original server.

Installation

The server ships on npm as @cardor/heimdall-mcp, 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.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Scope — Path
  • Local — {project-root}/heimdall.config.{ts,js,mjs,cjs,json}
  • Global — ~/.config/heimdall/heimdall.config.{ts,js,mjs,cjs,json}
  • Rule — Behavior
  • Field — Type
  • isPath — boolean
  • allow_pattern — string \
  • deny_pattern — string \
  • array_mode — 'all' \
  • case_sensitive — boolean
  • warn_only — boolean
  • Pattern — Meaning

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Heimdall MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Heimdall MCP's toolset — Scope, Local, Global and 11 more — is a fair guide to whether it matches your workflow. It is maintained by enmanuelmag; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Heimdall MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
ScopePath
Local{project-root}/heimdall.config.{ts,js,mjs,cjs,json}
Global~/.config/heimdall/heimdall.config.{ts,js,mjs,cjs,json}
RuleBehavior
FieldType
isPathboolean
allow_patternstring \
deny_patternstring \
array_mode'all' \
case_sensitiveboolean
warn_onlyboolean
PatternMeaning
resourcestring
ttlnumber

How to install the Heimdall MCP MCP server

{
  "mcpServers": {
    "heimdall": {
      "command": "npx",
      "args": ["-y", "@cardor/heimdall-mcp"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Heimdall MCP to Scope.
  • Use Heimdall MCP to Local.
  • Use Heimdall MCP to Global.

Frequently asked questions

It connects Heimdall MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Scope, Local, Global, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Heimdall MCP directly.