Skip to main content
Glama
pratnayake-alphasights

Transcript MCP spike

by pratnayake-alphasights
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Transcript MCP spike

No user-submitted related servers found.

    Related Servers

    • meetings-mcp

      aminafara123
      A
      license
      A
      quality
      C
      maintenance
      Exposes meeting transcripts to any MCP-capable AI client so it can list meetings, page through a single transcript, and search across all of them for a topic with exact timestamps. Speaker labels, emails, phone numbers, and paths are pseudonymized or redacted before anything crosses the protocol, and transcripts are read-only.
      3
      63 PyPI
      MIT

    • gilbert-mcp

      HugoF1234
      A
      license
      A
      quality
      D
      maintenance
      Read-only access to your Gilbert meetings, transcripts and summaries over MCP — list, search, and fetch transcripts and summaries.
      5
      47 npm
      1
      MIT

    • AskElephant MCP

      meticulosity
      F
      license
      Not graded
      quality
      B
      maintenance
      Hosted MCP server that lets staff search and retrieve AskElephant call transcripts from claude.ai, with tools for listing meetings, searching transcript excerpts, and fetching full transcripts.
      -

    • transcripts

      NisargKadam
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to list, read, and search local meeting transcript files, returning structured transcript information and search hits. The server enforces read-only access confined to a transcripts directory with .txt and .md files only.
      -
    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 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing metadata, retrieving a single transcript by ID, and searching across transcript content. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_transcripts, get_transcript, search_transcripts), with minor singular/plural variation that does not undermine the pattern.

    Tool Count5/5

    Three tools is a well-scoped set for a transcript retrieval service, covering the essential read operations without unnecessary bloat.

    Completeness4/5

    The read side is well covered (list, get, search), but write operations like create, update, or delete are absent. For a 'spike' server, this is a minor gap.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources