Skip to main content
Glama
GleidsonFerSanP

MCP AI Prompts Management

by GleidsonFerSanP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP AI Prompts Management

No user-submitted related servers found.

    Related Servers

    • Prompt Store MCP

      mhoshdev
      A
      license
      Not graded
      quality
      D
      maintenance
      A local-only MCP server that uses SQLite to store, search, and manage a personal library of AI prompts. It enables developers to organize and reuse prompts across multiple AI clients like Claude and Cursor while keeping all data on their local machine.
      10 npm
      1
      MIT

    • PromptingBox MCP Server

      promptingbox
      A
      license
      A
      quality
      D
      maintenance
      Allows users to save, organize, and manage AI prompts, folders, and tags directly within MCP-compatible tools like Claude and Cursor. It supports version history tracking, prompt searching, and the ability to save public templates to a personal collection.
      20
      13 npm
      MIT

    • promptflow-mcp

      RozuniFix72
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server for prompt template management, enabling storage, versioning, search, and rendering of prompt templates via MCP tools.
      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

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but three retrieval tools (list_prompts, get_prompt_summary, get_prompt) overlap in returning prompt metadata versus content. The descriptions explicitly differentiate their use cases, which reduces confusion.

    Naming Consistency5/5

    All tool names follow a consistent snake_case convention with verb_noun or get_noun patterns. There is no mixing of styles or ambiguous prefixes.

    Tool Count5/5

    Twelve tools are well-scoped for a prompt management server that includes CRUD, metadata, context stats, and storage configuration. Each tool earns its place without redundancy.

    Completeness4/5

    Core CRUD operations for prompts are fully covered, along with category/tag listing and storage configuration. Minor gaps exist, such as no explicit sync operation for storage or bulk prompt operations, but these are workaroundable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources