gamepad-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --host | No | Host address to bind for HTTP transport. Use a private address, never a public interface. | |
| --http | No | Use the streamable HTTP transport instead of stdio. | false |
| --port | No | Port to bind for HTTP transport. | |
| --token | No | Authentication token for HTTP transport. Required when using --http. | |
| --backend | No | Event backend. Use 'null' for dry-run mode that records events instead of posting them. | |
| GAMEPAD_PUBLIC | No | Set to 1 to enable public mode, masking IPv4 addresses in log output. Can also be enabled with --public. | 0 |
| GAMEPAD_PROFILE | No | Keymap profile to use, e.g. chiaki-ng. | |
| GAMEPAD_MAX_HOLD_MS | No | Maximum hold duration in milliseconds. Defaults to 10000 with a hard cap of 30000. | 10000 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusB | Backend, permission state, active keymap profile, held keys. |
| pressA | Press a DualSense button: cross, circle, square, triangle, dpad_up/down/left/right, l1, r1, l2, r2, l3, r3, options, share, touchpad, ps. hold_ms is how long the button stays down. |
| hold_stickB | Hold an analog stick direction. stick: 'left' or 'right'. direction: up, down, left, right, or a diagonal like 'up-left'. This is how a character walks/runs and how the camera turns. |
| key_tapC | Tap a raw keyboard key by name (e.g. 'return', 'w', 'esc'). |
| key_downB | Hold a raw key down until key_up or the hard cap releases it. |
| key_upC | Release a raw key held by key_down. |
| comboB | Press several raw keys together (e.g. ['cmd', 'tab']). |
| release_allA | Panic button: release every held key immediately. |
| mouse_moveC | Move the mouse pointer to absolute screen coordinates. |
| mouse_clickC | Click the mouse ('left' or 'right'). |
| profilesB | List available keymap profiles. |
| set_profileC | Switch the active keymap profile. |
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 12 tools
Most tools target clearly distinct device+action pairs (mouse_move vs mouse_click vs press vs key_tap). The only mild overlaps are press vs key_tap (gamepad button vs raw key) and hold_stick vs key_down, but descriptions make the distinction reasonably clear.
Consistent snake_case with verb_* prefixes for action tools (key_tap, key_down, key_up, mouse_move, mouse_click, hold_stick, set_profile). A few bare-noun tools (status, profiles, combo) deviate slightly from the verb_noun pattern but remain readable.
12 tools is well within the sweet spot and each tool covers a distinct input primitive (buttons, sticks, keys, mouse, profiles, panic release). Nothing feels redundant or missing at the count level.
Covers gamepad buttons/sticks, raw keyboard tap/hold/combo, panic release, mouse move/click, and profile management—solid lifecycle coverage. Minor gaps: no mouse scroll or button-down/up for drags, and no explicit stick release beyond the global release_all.