karabiner-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_rulesA | List Karabiner-Elements complex modification rules for a profile. Returns each rule's description, enabled/disabled status, whether it's installed in karabiner.json, and its source asset file. Rules are listed in priority order (first match wins in Karabiner). |
| add_ruleA | Create and install a new Karabiner-Elements rule. Writes the rule to an asset file AND installs it in karabiner.json for immediate effect. Karabiner-Elements auto-reloads on file change. For simple remaps, use to_key_code. For tap-vs-hold, combine to_key_code (held behavior) with to_if_alone_key_code (tap behavior). Examples:
|
| toggle_ruleA | Enable or disable an installed rule. The rule stays in karabiner.json either way — disabling adds 'enabled: false', enabling removes that flag. |
| remove_ruleA | Remove a rule from karabiner.json (all profiles). By default the asset file is preserved so the rule can be re-added later via the Karabiner Settings UI or add_rule. |
| edit_ruleA | Edit an existing rule. Updates both the asset file and karabiner.json. Only pass the parameters you want to change. To see a rule's current configuration, use list_rules first. |
| list_profilesA | List all Karabiner-Elements profiles with their rule counts. Shows which profile is currently selected. Use select_profile to switch the active profile. |
| select_profileA | Switch the active Karabiner-Elements profile. Takes effect immediately. Use list_profiles first to see available profiles and their indices. |
| search_key_codesA | Search valid Karabiner-Elements key codes and modifiers. Call this before add_rule or edit_rule to find the correct key_code string. Key codes are Karabiner-specific identifiers (e.g. 'return_or_enter' not 'enter', 'delete_or_backspace' not 'backspace', 'grave_accent_and_tilde' not '`'). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct operation: rule lifecycle (add, list, toggle, remove, edit), profile management (list, select), and key code lookup (search). No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern in lowercase snake_case (list_rules, add_rule, toggle_rule, remove_rule, edit_rule, list_profiles, select_profile, search_key_codes). No deviations.
8 tools is well-scoped for managing Karabiner rules and profiles, covering CRUD and auxiliary operations without bloat or thinness.
Rule CRUD and profile selection are covered, but there is no tool to reorder rules, which is important given Karabiner's priority-based matching. Minor gap that agents can work around by editing the underlying file.