Skip to main content
Glama
seenbefore

mcp-dev-record

by seenbefore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-dev-record

No user-submitted related servers found.

    Related Servers

    • recap

      eric8810
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for conversation recording and review management, supporting recording, querying, and statistical analysis of conversation history with dual transport mode.
      19 npm
      MIT

    • MCP Session Saver

      oscar-wang-xin
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables users to save, search, and manage AI conversation records as organized Markdown files across various IDEs. It automatically categorizes sessions by IDE name, date, and description for efficient storage and easy retrieval.
      5
      6 npm
      5
      MIT

    • context-the-ripper

      M4NT
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that manages your conversation context automatically, pruning dead branches and keeping an audit trail of every cut.
      2 npm
      1
      MIT

    • video-summarizer

      yangmiao3
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that converts videos, audio, and meeting recordings into structured transcripts and summaries with multi-backend ASR and automatic fallback.
      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

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_template_list retrieves a list of available templates with metadata, while get_template_detail fetches the detailed content of a specific template. There is no overlap or ambiguity between them, as one is for discovery and the other for content retrieval.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (get_template_list and get_template_detail), using the same verb 'get' and a clear noun structure. This makes the naming predictable and easy to understand across the tool set.

    Tool Count3/5

    With only 2 tools, the server feels thin for a development record domain, as it lacks operations like creating, updating, or deleting templates or records. While the tools cover basic retrieval, the scope seems limited, potentially requiring agents to work around missing functionality.

    Completeness2/5

    The tool surface is significantly incomplete for a development record system. It only provides read operations (list and detail retrieval) with no ability to create, update, or delete templates or records. This leaves obvious gaps that could cause agent failures when trying to perform full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources