sudo-meow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QA_MAX_STEPS | No | Maximum number of tool-calling steps for the QA agent. | 200 |
| OLLAMA_BASE_URL | No | The base URL for the Ollama API. | http://localhost:11434 |
| QA_OLLAMA_MODEL | No | The Ollama model to use for the QA agent's tool-calling loop. | llama3.1 |
| SUDO_MEOW_DEBUG_URL | No | The base URL of the sudo-meow debug HTTP API (the Tauri app's Vite dev server). | http://localhost:1420 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_stateA | Snapshot of the sudo meow cat's state machine and Pomodoro timer from a running dev instance (requires |
| get_available_transitionsA | What's reachable from the cat's current state: the organic weighted-graph options, every state forceTransition would accept (unconditionally — CatStateMachine has no transition validation of its own, see docs/STATE_MACHINE.md), and which Pomodoro events are valid from the current phase. |
| trigger_eventA | Sends an event to the live state machine. Valid eventNames: "cat.forceTransition" (payload: { state: CatState }), "pomodoro.start" (payload?: { minutes }), "pomodoro.tick" (payload?: { dtSeconds }), "pomodoro.resume", "pomodoro.cancel". Call get_available_transitions first to see what's valid from the current state — invalid states/events are rejected with a clear error. |
| get_state_historyA | Last transitions of both machines, interleaved, oldest first. The debug server itself caps this at 50 entries; |
| read_console_logsA | Last console.log/warn/error calls from the app window since it loaded. The debug server itself caps this at 200 entries; |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alicefarron/sudo-meow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server