Skip to main content
Glama
yuyao1999

RT-Prompt-MCP

by yuyao1999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to RT-Prompt-MCP

No user-submitted related servers found.

    Related Servers

    • MCP Dev Standards

      han0420
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides development standards and best practices context to AI coding assistants, ensuring generated code adheres to team/project conventions.
      3
      8 npm
      1
      MIT

    • mcp-for-programmer

      zaizaizhao
      F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that helps programmers understand code by providing explanations, tech stack analysis, and best practice suggestions through prompt templates.
      3
      6 npm
      1
      -

    • MCP Prompt Server

      gdli6177
      A
      license
      D
      quality
      D
      maintenance
      A server based on Model Context Protocol that provides predefined prompt templates for tasks like code review and API documentation generation, enabling more efficient workflows in Cursor/Windsurf editors.
      10
      13 npm
      247
      MIT

    • Git Prompts MCP Server

      ceshine
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that generates prompts based on Git repository content, including a command to generate PR descriptions from diffs.
      3
      2
      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

    D1.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools are clearly distinguished by their target domains (backend, frontend, general, RT-CRUD, UI design, Feishu), making misselection unlikely. However, the lack of descriptions means the exact boundaries between 'general' and domain-specific suggestions are unclear, which could cause minor confusion.

    Naming Consistency5/5

    All tools follow a perfect 'get_[domain]_suggestions' pattern, with consistent snake_case and verb-noun structure. This predictability makes it easy for agents to understand and use the toolset without naming-related errors.

    Tool Count4/5

    Six tools is a reasonable number for a prompt suggestion server, covering multiple domains without being overwhelming. It could be slightly thin if more granular domains are needed, but the scope appears well-defined for common development areas.

    Completeness2/5

    The toolset is severely incomplete as it only provides 'get' operations with no ability to create, update, delete, or manage prompts. For a prompt management server, this represents significant gaps that will limit agent workflows and cause dead ends in multi-step tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources