Skip to main content
Glama
Miyamura80

agent-prompt-capture

by Miyamura80
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-prompt-capture

No user-submitted related servers found.

    Related Servers

    • flameox

      morluto
      A
      license
      C
      quality
      C
      maintenance
      Enables coding agents to query, compare, and audit local profiler traces, benchmarks, memory captures, and execution evidence without uploading code or data, using CLI and MCP interfaces.
      111
      132 PyPI
      220
      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

    • Langfuse MCP Server

      pablokrylov766
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and developers to query traces, observations, sessions, and exceptions, plus prompts, datasets, annotation queues, scores, and aggregated metrics, for local debugging and observability from any MCP client. Supports selective tool-group loading to cut token overhead and a read-only mode that disables all write operations.
      -

    • Tailpipe

      HarmoniqOS
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query your complete local conversation history and knowledge graph over MCP, including full-fidelity transcripts, search, and typed, dated entity relationships.
      AGPL 3.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: list_prompts/search_prompts/get_prompt for raw access, list_sources/list_sessions for metadata, and the four analytics tools each target a different slice (timeline buckets, counts, time-use groups, single-day digest). Even the overlapping time-related tools have explicitly differentiated use cases.

    Naming Consistency4/5

    The retrieval tools follow a consistent verb_noun pattern (list_prompts, list_sources, list_sessions, search_prompts, get_prompt), but the analytics tools use plain noun names (activity_timeline, prompt_stats, time_summary, daily_digest). This is predictable and readable, but not a fully uniform convention across the set.

    Tool Count5/5

    Nine tools is well-scoped for a prompt-capture and analysis server, covering enumeration, search, single-record fetch, metadata discovery, and multiple analytic views without redundancy or bloat.

    Completeness5/5

    The surface covers the full read-side lifecycle: discover sources/sessions, browse/search/fetch prompts, and analyze activity over time at both aggregate and per-day granularity. For a read-only capture server, there are no obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources