Happy Server MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HAPPY_SERVER_URL | No | Override the Happy server URL | https://happy.engineering |
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 |
|---|---|
| happy_list_sessionsB | List all Happy AI sessions. Returns session IDs, titles, paths, machines, and activity status. |
| happy_list_machinesA | List all machines registered with Happy. Returns machine IDs, hostnames, platforms, and activity status. |
| happy_list_recent_pathsB | List recently used folder paths for a machine. Useful for starting sessions in familiar locations. |
| happy_list_environment_setsA | List available environment variable presets. These can be used when starting new sessions with happy_start_session. |
| happy_read_messagesB | Read recent messages from a Happy AI session. Use this to see the conversation history. |
| happy_send_messageB | Send a message to a Happy AI session to trigger it to work. The message will be sent with bypass permissions mode. |
| happy_start_sessionA | Start a new Happy AI session on a machine. Use happy_list_machines to find available machines first. Use happy_list_environment_sets to see available environment presets. Optionally create a Git worktree for isolated development. |
| happy_archive_sessionA | Archive (stop) a Happy AI session. The session will be terminated and marked as inactive. |
| happy_wait_for_idleA | Wait for a Happy AI session to become idle (finish processing). Useful after sending a message to wait for AI to complete its work. |
| happy_zen_list_todosB | List Zen (todo) items with titles, descriptions, and completion status. |
| happy_zen_create_todoC | Create a new Zen (todo) item with a title and optional description. |
| happy_zen_update_todoC | Update a Zen (todo) item title and/or description. |
| happy_zen_set_todo_doneC | Set or toggle a Zen (todo) item completion status. |
| happy_zen_delete_todoC | Delete a Zen (todo) item. |
| happy_zen_link_sessionC | Link a Zen (todo) item to a Happy session with a display title. |
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 15 tools
Each tool has a clearly distinct purpose with no ambiguity. Tools are grouped into session management (e.g., start, archive, list sessions), session interaction (e.g., send message, read messages, wait for idle), and Zen todo management (e.g., create, delete, update, list todos), with no overlap in functionality. The descriptions reinforce these distinct roles, making misselection unlikely.
All tool names follow a consistent 'happy_verb_noun' pattern with snake_case throughout. The naming is predictable and readable, with verbs like list, start, send, read, wait, create, delete, link, set, and update applied consistently to their respective nouns (e.g., sessions, messages, todos). There are no deviations in style or convention.
With 15 tools, the count is well-scoped for the server's purpose of managing Happy AI sessions and Zen todos. Each tool earns its place by covering essential operations such as session lifecycle, interaction, and todo CRUD, without being excessive or sparse. This number supports comprehensive functionality while remaining manageable.
The tool surface provides complete coverage for the domain of Happy AI session and Zen todo management. For sessions, it includes start, archive, list, send messages, read messages, and wait for idle, plus supporting tools for machines and environment sets. For Zen todos, it offers full CRUD operations (create, read, update, delete) and linking to sessions, with no obvious gaps or dead ends in the workflow.