Skip to main content
Glama
5dive-ai

5dive MCP server

Official
by 5dive-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to 5dive MCP server

No user-submitted related servers found.

    Related Servers

    • TypeSafe MCP

      Renwang-Huang
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP-compatible agent hosts to interact with TypeSafe AI's Jev System One API through dependency-free STDIO tools for classification, scoring, verification, gating, routing, review, and health checks.
      9
      MIT

    • t2a mcp

      isnotry
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a local-first task board over stdio JSON-RPC so MCP-capable agents can list and create projects and tasks, atomically claim the next ready task with a lease, heartbeat, log progress, manage dependency graphs, and mark tasks done or failed with results. All state lives in a single local SQLite file, so no shell command assembly or external services are needed.
      MIT

    • Terminal Session Manager

      danieldoalto
      F
      license
      B
      quality
      B
      maintenance
      Enables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.
      15
      -
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources