Mavis MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mavis_session_listB | List Mavis sessions. Returns session IDs, titles, and last-updated timestamps. |
| mavis_session_infoB | Get detailed info about a specific session (status, workspace, model, etc.) |
| mavis_session_messagesB | Get the message history (conversation transcript) of a session. |
| mavis_session_newA | Create a new standalone Mavis session (use --from root for isolated, independent session). For child sessions linked to a parent, use mavis_spawn_worker instead. |
| mavis_session_abortB | Abort a running session. |
| mavis_session_rotateA | Rotate the current session — archives the old session and creates a fresh one with a handoff prompt. |
| mavis_session_diffA | Show file changes (git diff) made by a session. |
| mavis_comm_sendC | Send a message or command to a running session (prompt/abort/kill/summarize/fork/spawn). |
| mavis_comm_peersB | List all reachable (active) sessions in the Mavis network. |
| mavis_team_planA | List team plans or get status of a specific plan. Use |
| mavis_agent_listA | List all available Mavis agents (built-in and custom). |
| mavis_agent_infoB | Get detailed info about a specific agent (skills, system prompt, etc.) |
| mavis_memory_appendB | Append a new entry to Mavis memory (user, agent, or project level). |
| mavis_memory_searchC | Search Mavis memory for entries matching a query. |
| mavis_cron_createB | Create a scheduled cron job (self-reminder, recurring task, etc.) |
| mavis_cron_listB | List all scheduled cron jobs for an agent. |
| mavis_cron_deleteB | Delete a cron job. |
| mavis_skill_listA | List all installed Mavis skills (global and agent-specific). |
| mavis_skill_infoB | Get detailed info about a specific skill (description, triggers, commands). |
| mavis_hook_listA | List all registered Mavis hooks (pre/post execution triggers). |
| mavis_config_showA | Show current Mavis daemon configuration (models, provider, nexus settings). |
| mavis_mcp_listA | List all registered MCP servers and their available tools. |
| mavis_mcp_callB | Call a specific tool on an MCP server. Useful for delegating to Playwright, Matrix, or other MCP tools from within Mavis. |
| mavis_statusA | Check Mavis daemon status (running, port, version). |
| mavis_spawn_workerA | Spawn a single-shot worker/verifier agent as a child session. Use for code review, test, verify tasks. The agent runs independently and reports back. For complex multi-agent tasks, use mavis_team_plan instead. |
| mavis_usageC | Inspect token usage by session, agent, or globally. |
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 26 tools
Each tool targets a distinct resource and action, with clear domain prefixes like session, agent, memory. Even the session tools (new, list, info, messages, abort, rotate, diff) have well-defined purposes, and potential overlaps like session_new vs spawn_worker are clarified in descriptions.
All tools follow a consistent 'mavis_<domain>_<verb>_<noun>' pattern, using snake_case throughout. Verbs like list, info, create, delete, search, append are uniformly applied across domains.
26 tools is somewhat high but justified by the comprehensive scope covering agents, sessions, memory, skills, communication, MCP, cron, hooks, and team plans. Each tool serves a distinct purpose, and no obvious redundancy exists.
The tool surface covers most lifecycle operations for agents, sessions, memory, and skills. Notable gaps include lack of agent creation/deletion and team plan creation (only status/list), but core workflows are well-supported.