5dive MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIVEDIVE_BIN | No | Path to the 5dive binary. | 5dive |
| FIVEDIVE_SUDO | No | Set to '1' to prefix calls with sudo. | |
| FIVEDIVE_TIMEOUT_MS | No | Per-call timeout in milliseconds. | 30000 |
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 |
|---|---|
| task_createA | Create a task in the shared 5dive task queue. Returns the new task's id (e.g. DIVE-N). Use for filing work for an agent or human on the fleet. |
| task_showA | Fetch full detail for one task by id (numeric or DIVE-N): status, priority, body, result, subtasks, and blockers. |
| task_listA | List tasks in the shared queue. Defaults to open tasks in priority order; filter by status or assignee. |
| agent_sendA | Send a message to another agent on the fleet by name (inter-agent comms). The recipient receives it in-session. |
| agent_listA | List every agent on the box: name, type, channels, model, and live state. |
| digest_getA | Get the fleet's daily standup digest (activity, token burn, health). Pass window=7d for the weekly view. |
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 6 tools
Each tool targets a distinct action and resource: agent listing, agent messaging, digest retrieval, and task CRUD operations (create, list, show). There is no overlap in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent noun_verb pattern (e.g., agent_list, digest_get, task_create). The naming is predictable and uniform across the entire set.
Six tools is an appropriate count for a fleet management server covering agent communication and task management. The number is neither too small nor too large, and each tool serves a clear purpose.
The tool set covers basic operations for agents (list, send) and tasks (create, list, show), but lacks update and delete for tasks, and agent management beyond listing. These gaps could cause agent failures when full lifecycle control is needed.