Skip to main content
Glama
OktoLabsAI

okto-nexus

by OktoLabsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to okto-nexus

No user-submitted related servers found.

    Related Servers

    • Nexus Memory

      Neboy72
      A
      license
      A
      quality
      A
      maintenance
      Nexus Memory gives every MCP-compatible agent one persistent, self-hosted shared memory with hybrid retrieval, drift detection, and anti-poisoning features.
      21
      3
      MIT
    • Memory Nexus by MemoryNexus

      Memory Nexusofficial

      MemoryNexus
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory and handoff intelligence layer for MCP agents. Most memory servers retrieve text — Memory Nexus compounds operational context, learning from usage and progressively synthesizing observations into higher-order intelligence across sessions and tools.
      MIT

    • model-context-stream

      thejavapirate
      A
      license
      Not graded
      quality
      A
      maintenance
      An event-driven MCP server that enables agents to share context streams, publish and subscribe to events, manage tasks, and follow protocols, keeping a fleet of agents mutually context-aware in real time.
      1
      MIT

    • agent-comms-mcp

      redesignhealth
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for permissioned, structured agent-to-agent communications, enabling agents to coordinate and negotiate through scoped, typed messages with authentication and audit logging.
      111 PyPI
      MIT

    • mcp-switchboard

      Jemplayer82
      A
      license
      Not graded
      quality
      A
      maintenance
      A real-time inter-agent switchboard, delivered as one centralized streamable-HTTP MCP server. Any MCP-capable agent can message, coordinate, and stay ambiently aware of others.
      1
      AGPL 3.0

    • nexus-mcp

      DTG404
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that wraps the nexus CLI, giving AI agents cross-session memory, semantic search, preference learning, and smart context injection.
      137 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 43 tools

    Disambiguation4/5

    The tool set covers many distinct sub-domains (handoffs, inbox, events, sessions, etc.), and most tools have clearly differentiated purposes. However, some read-oriented tools overlap (event_get/event_wait, inbox_pull/inbox_peek) and three legacy message_* tools are deprecated but still present, which could momentarily confuse an agent.

    Naming Consistency5/5

    All 43 tools use consistent snake_case with a domain_action pattern (e.g., handoff_create, inbox_pull, poll_token_issue). The only variation is minor compound forms like handoff_list_available, but the convention is predictable and uniform.

    Tool Count2/5

    43 tools is well above the typical 3–15 range and even excluding the 3 deprecated message tools leaves 40. This heavy surface likely burdens agents and exceeds what the server’s purpose requires.

    Completeness4/5

    The surface covers CRUD-like lifecycle for handoffs, inbox, sessions, events, artifacts, agents, workspaces, and poll tokens, with no dead ends in core workflows. Minor gaps exist (no artifact list/delete, no agent/channel delete), but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources