Skip to main content
Glama
nelsonjordanme

@useclypt/mcp-server

by nelsonjordanme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @useclypt/mcp-server

No user-submitted related servers found.

    Related Servers

    • Clypt MCP Server

      Bonsai-Tech-LLC
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to the Clypt Link Intelligence platform to shorten URLs, manage tags, and generate QR codes. It enables users to view link analytics and perform bulk link operations through natural language commands.
      30 npm
      MIT

    • Podcast Index MCP

      thenavidm
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search millions of podcasts, read and search episode transcripts with timestamps and speakers, and access chapters, soundbites, Podcasting 2.0 tags, value-for-value data, feed health, and index statistics through 36 tools.
      36
      39 npm
      1
      MIT

    • zoom-editor

      IslePrince
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to turn a meeting recording and transcript into captioned clips, trailers, longform best-ofs, and 1:1/9:16/16:9 social videos. Agents can create projects, inspect transcripts, render jobs, check status, and retrieve output files.
      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.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: submit creates a job, get retrieves a specific job, and list enumerates jobs. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: submit_job, get_job, list_jobs. The slight pluralization in list_jobs is a minor and natural deviation.

    Tool Count5/5

    Three tools is well-scoped for the server's purpose of managing asynchronous podcast processing jobs. Each tool earns its place with no redundancy.

    Completeness4/5

    The surface covers the core lifecycle: submit, poll, and list jobs. Missing cancel/delete is a minor gap but not essential for the stated async-processing workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources