Skip to main content
Glama
chrisliebaer

claude-subagent-mcp

by chrisliebaer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to claude-subagent-mcp

No user-submitted related servers found.

    Related Servers

    • Log MCP Server

      thhart
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to automatically inspect and analyze application runtime log files for debugging and troubleshooting. Supports monitoring multiple log directories simultaneously with tools for listing, reading, searching, and paginating through log files.
      8
      MIT

    • mcp-session-insight

      ArtLjn
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query and analyze past Claude Code sessions, providing structured insights like file changes, decisions, errors, and git history across projects.
      11
      9 npm
      1
      MIT

    • chronicle-mcp

      loerei
      A
      license
      Not graded
      quality
      B
      maintenance
      Indexes and searches agent conversation logs from Antigravity and Cursor workspaces, enabling semantic search, token analysis, and benchmarking over local SQLite storage.
      11 npm
      MIT

    • agent-activity

      patrickdaj
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that exposes local coding-agent session logs as three tools for introspection of recent work, debugging tool failures, and tracking token usage and estimated cost without parsing log files.
      3
      MIT

    • reqlog

      ankitksr
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding agents with tools to query, search, and analyze persisted HTTP request logs, enabling efficient debugging without terminal noise.
      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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one retrieves text/status messages, the other retrieves tool call details. There is no overlap in purpose or output.

    Naming Consistency5/5

    Both tool names follow a consistent `get_last_<entity>` pattern, making it easy for an agent to predict the naming convention.

    Tool Count3/5

    With only 2 tools, the server feels thin for a general subagent monitoring use case. However, it may be appropriately minimal if the server's scope is intentionally limited to just observing agent output.

    Completeness3/5

    The tools cover reading status and tool calls, which are core observation needs. However, there are no tools for filtering by type, searching, or managing the agent's state, leaving notable gaps for a monitoring server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources