state-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATE_BRIDGE_PORT | No | The port for the WebSocket server (can also be set via --port argument) | 8098 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connection_statusB | Check if a client app is connected via WebSocket |
| list_storesA | List all Zustand stores and their top-level state keys |
| get_stateA | Read state from a Zustand store. Optionally provide a dot-path to read a specific slice. |
| set_stateA | Write a value to a Zustand store at the given path |
| call_actionB | Invoke a store action function by name (e.g. "clearHistory", "setActiveTab") |
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 5 tools
Each tool addresses a distinct concern: actions, connections, reading state, listing stores, and writing state. No overlap or ambiguity between tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_state, list_stores), making them predictable and easy to understand.
With 5 tools, the set is well-scoped for a state management bridge, covering all essential operations without unnecessary bloat.
The tools cover core state operations (list, get, set, actions) and a connection check. Missing subscription or store creation, but these are minor gaps for the intended purpose.