Skip to main content
Glama
Sign In
@clipy/mcp

@clipy/mcp

by clipy-recorder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @clipy/mcp

No user-submitted related servers found.

    Related Servers

    • memgrep

      gitwork-oss
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and retrieve past chat transcripts from Cursor, Claude Code, and Kiro, providing a global, local memory for context-aware assistance.
      27 npm
      2
      MIT

    • AgentClip MCP Server

      0xkaz
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to store, search (keyword and semantic), retrieve, update, and delete personal browser clips from a Cloudflare-backed store, authenticated via per-user token.
      1
      -

    • zoom-mcp

      aronroyca
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with structured access to Zoom recorded meetings, enabling search, summarization, and action item extraction.
      2 npm
      BSD 2-Clause "Simplified"

    • Rustle

      vibeslop
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read videos from YouTube links, web pages, media URLs, or local files by returning timestamped transcripts, labelled frame contact sheets, and lossless audio or spectrograms. Also searches YouTube, channels, pages, and folders to find videos worth reading.
      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 34 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (edit_recording vs replace_transcript vs get_transcript, search_memory vs search_recordings vs list_context_documents) and descriptions carefully flag the distinctions. There is still a cluster of look-alike read paths (get_recording, get_agent_context, wait_for_artifacts, get_key_moments) and two recording-start tools (record vs start_recording) that an agent must reason about, so some overlap survives.

    Naming Consistency4/5

    Predominantly snake_case verb_noun (get_transcript, create_folder, list_comments, delete_recording) with clear symmetry across resources. A few deviations—bare verbs like `record` and noun-ish `add_marker`/`add_chapter`—are minor but break the pattern slightly.

    Tool Count3/5

    34 tools is heavy and pushes past the comfortable range; the surface spans ingestion, editing, comments, folders, analytics, and two libraries, so many tools are justified. Still, the read/inspect layer feels dense and a few helpers (get_agent_context vs get_recording + get_transcript + get_key_moments) could be consolidated.

    Completeness4/5

    The lifecycle is well covered—record/start/stop/abort, upload, edit, replace transcript, privacy, folders, comments, analytics, search, read, and permanent delete—leaving few dead ends. Minor gaps like folder deletion/listing of folders' contents and comment resolution are not fully exposed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources