Heimdall is a lightweight service that manages local Model Context Protocol (MCP) Servers on your device. It allows you to authorize specific MCP server tools for your clients and makes the same configuration accessible to all MCP clients on your system, all with a simple installation process.
Before installing Heimdall, it's recommended to back up your existing MCP server configuration to prevent any accidental loss of credentials.
Run the setup script with an optional path to your current configuration:
npx @shinzolabs/heimdall setup <optional: path/to/current/config.json>
The setup will:
mcpServers
config to ~/.heimdall/config.json
~/.heimdall/controls.json
to authorize all methods on current serversIf you prefer installing locally:
git clone https://github.com/shinzo-labs/heimdall.git
cd heimdall && pnpm i && pnpm build
pnpm run setup <optional: path/to/current/config.json> <optional: path to index.js>
To add or update available servers, edit the configuration file at ~/.heimdall/config.json
using the standard mcpServers
JSON format. Remember that new servers must also be added to the controls file to appear through Heimdall.
To authorize tools for servers, edit ~/.heimdall/controls.json
. Heimdall will detect changes within seconds, and MCP clients with dynamic tool caching will update automatically. Other clients may require a restart.
Here's the schema for the controls file:
{
"authorizedMcpServers": {
"server1": {
"authorizedTools": [
"tool1",
"tool2"
]
},
"server2": {
"authorizedTools": [
"tool1",
"tool2"
]
}
}
}
To use the same authorized tools across multiple MCP clients, set up each new client with this configuration:
{
"mcpServers": {
"heimdall": {
"command": "npx",
"args": [
"@shinzolabs/heimdall"
]
}
}
}
Some MCP clients have limits on the number of available tools. For example, Cursor supports up to 40 tools across all servers, so your total authorized tools cannot exceed this number.
Logs for Heimdall instances and child servers are stored in ~/.heimdall/logs
, organized in directories with random UUIDs for each MCP client.
If your MCP client closes unexpectedly, Heimdall processes might remain running. You can clean these up with:
pkill -aif node
Note: Only use this command if you don't have other important Node.js processes running.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "heimdall" '{"command":"npx","args":["@shinzolabs/heimdall"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"heimdall": {
"command": "npx",
"args": [
"@shinzolabs/heimdall"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"heimdall": {
"command": "npx",
"args": [
"@shinzolabs/heimdall"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect