Skip to main content
Glama
managed-agent-control-mcp

managed-agent-control-mcp

by modus-agendi

Related Servers

Alternatives to managed-agent-control-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Wraps the Claude Agent SDK as MCP servers, letting you spawn multiple specialized Claude Code agents — each with its own model, tools, system prompt, and personality — from any MCP client.
      5
      111 npm
      22
      ISC
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely discover, execute, and observe tools with role-based access control and audit logging. Serves tools over MCP stdio and HTTP for integration with Claude Desktop, Cursor, and other clients.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Desktop, Claude Code and Cursor to hand tasks and questions to a self-hosted agent that answers using its own local model, memory, document library and tools. It also lets those clients search long-term memory, save facts, and search, list or add documents, while shell commands and file writes are refused.
      40 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes multi-provider AI routing with verifiable routing receipts, Policy-as-Code enforcement (budgets, PII redaction, model/tool allowlists, rate limits, audit logs), and MCP-native agent tools to any MCP host over stdio. It lets clients run routed completions, gated agent workflows, and policy checks through a single governed interface.
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.
      8
      60 npm
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource (agent, environment, vault, memory store, session) and action (list, get, start, etc.). No two tools serve overlapping purposes; even session_archive and session_delete are clearly differentiated by their effects.

    Naming Consistency5/5

    Tool names follow a consistent noun_verb pattern (e.g., agent_get, session_start), all lowercase with underscores. There is no mixing of conventions across the tool set.

    Tool Count5/5

    17 tools cover the domain of managed-agent control without being excessive. Each tool serves a needed function, and there are no redundant or trivial tools.

    Completeness4/5

    The tool set covers the full session lifecycle (start, message, observe, interrupt, respond, archive, delete). While resource management (e.g., create/update for agents, environments) is missing, it is likely out of scope, making the surface complete for its control purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues