S
shinzo-labs/heimdall
Limit which MCP tools an agent is allowed to call
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"shinzo-labs-heimdall": {
"command": "npx",
"args": ["command."]
}
}
}Parsed from the README we fetched on 2026-11-04; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"shinzo-labs-heimdall": {
"command": "npx",
"args": ["command."]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio shinzo-labs-heimdall -- npx command.
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
npx command.
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx command.. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# Heimdall
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Heimdall is a lightweight service to manage local MCP Servers and can be installed with a single npx command. Specific MCP server tools can be authorized for your MCP clients, and the same config is accessible to all MCP clients on your device.
## Installation
⚠️ NOTE: We strongly recommend backing up your MCP server config before installation to protect against unexpected loss of credentials.
The setup script performs a few key actions:
Moves the mcpServers config JSON from the path you specify to ~/.heimdall/config.json
Inserts a single config for heimdall in place of the previous mcpServers config path
Initializes the controls at ~/.heimdall/controls.json to authorize all methods on all current servers
See Configuration for steps to modify ~/.heimdall/controls.json to limit the authorized tools for a given server, and add new servers to ~/.heimdall/config.json.
### Via NPX (Recommended)
1. Run setup script (generates an empty config if no path is given):
npx @shinzolabs/heimdall setup
### Via Local Instance
1. Download the package:
bash
git clone https://github.com/shinzo-labs/heimdall.git
2. Install and build dependencies:
bash
cd heimdall && pnpm i && pnpm build
3. Run setup script (generates an empty config if no path is given):
pnpm run setup
## Configuration
### Edit Server List
To add or update available servers, simply update the configuration at ~/.heimdall/config.json as your regular mcpServers config JSON. Note that you will not see tools for new servers through Heimdall unless you also add the server and authorized tools to ~/.heimdall/controls.json.
### Edit Authorized Tools
To add authorized tools to a new or existing server, add them as needed to ~/.heimdall/controls.json and Heimdall will update its internal config after a few seconds. If your MCP client supports dynamic tool list caching, you should see it update the authorized tools automatically. Other clients (ex. Claude Desktop) may require a restart to see the new tools.
This is the schema for ~/.heimdall/controls.json:
javascript
"authorizedMcpServers": {
"server1": {
"authorizedTools": [
"tool1",
"tool2",
...
},
"server2": {
"authorizedTools": [
"tool1",
"tool2",
...
### Multiple MCP Clients
If you run multiple MCP clients on your device, you can set the following config.json for each new client to enable the same authorized tools across all of them (assuming Heimdall has already been set up on the device):
javascript
"mcpServers": {
"heimdall": {
"command": "npx",
"args": [
"@shinzolabs/heimdall"
## Troubleshooting
### Available Tools
Some MCP Clients have limits on the number of tools available to agents at a given time. For example, Cursor only supports up to 40 tools across all servers, so the sum of authorizedTools in controls.json cannot exceed this number.
## Installation
⚠️ NOTE: We strongly recommend backing up your MCP server config before installation to protect against unexpected loss of credentials.
The setup script performs a few key actions:
Moves the mcpServers config JSON from the path you specify to ~/.heimdall/config.json
Inserts a single config for heimdall in place of the previous mcpServers config path
Initializes the controls at ~/.heimdall/controls.json to authorize all methods on all current servers
See Configuration for steps to modify ~/.heimdall/controls.json to limit the authorized tools for a given server, and add new servers to ~/.heimdall/config.json.
### Via NPX (Recommended)
1. Run setup script (generates an empty config if no path is given):
npx @shinzolabs/heimdall setup
### Via Local Instance
1. Download the package:
bash
git clone https://github.com/shinzo-labs/heimdall.git
2. Install and build dependencies:
bash
cd heimdall && pnpm i && pnpm build
3. Run setup script (generates an empty config if no path is given):
pnpm run setup
## Configuration
### Edit Server List
To add or update available servers, simply update the configuration at ~/.heimdall/config.json as your regular mcpServers config JSON. Note that you will not see tools for new servers through Heimdall unless you also add the server and authorized tools to ~/.heimdall/controls.json.
### Edit Authorized Tools
To add authorized tools to a new or existing server, add them as needed to ~/.heimdall/controls.json and Heimdall will update its internal config after a few seconds. If your MCP client supports dynamic tool list caching, you should see it update the authorized tools automatically. Other clients (ex. Claude Desktop) may require a restart to see the new tools.
This is the schema for ~/.heimdall/controls.json:
javascript
"authorizedMcpServers": {
"server1": {
"authorizedTools": [
"tool1",
"tool2",
...
},
"server2": {
"authorizedTools": [
"tool1",
"tool2",
...
### Multiple MCP Clients
If you run multiple MCP clients on your device, you can set the following config.json for each new client to enable the same authorized tools across all of them (assuming Heimdall has already been set up on the device):
javascript
"mcpServers": {
"heimdall": {
"command": "npx",
"args": [
"@shinzolabs/heimdall"
## Troubleshooting
### Available Tools
Some MCP Clients have limits on the number of tools available to agents at a given time. For example, Cursor only supports up to 40 tools across all servers, so the sum of authorizedTools in controls.json cannot exceed this number.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/shinzo-labs-heimdall/)
- Source
- awesome · https://github.com/shinzo-labs/heimdall
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.