Skip to main content
Glama
PromStack-1

PromStack MCP Server

by PromStack-1

Related Servers

Alternatives to PromStack MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables dynamic discovery, search, and on-demand retrieval of local Claude Skills, making them accessible as a composable skill registry across MCP-compatible hosts without manual configuration.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP clients (Claude Desktop, Cursor, Cline, Zed) to llmsproxy.ai, exposing chat, coding, and retrieval capabilities as MCP tools, resources, and prompts.
      6 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to connect to example tools, resources, and prompts over MCP, demonstrating integration with IDEs, chatbots, and agent frameworks.
      -
    • A
      license
      C
      quality
      D
      maintenance
      Integrates AI safety analysis, red-teaming, and prompt auditing directly into MCP-compatible clients like Claude Desktop and Cursor IDE, allowing real-time analysis of prompts and detection of jailbreak attempts.
      28
      3
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP gateway that lets you write Python functions and register them as skills to be used as tools by any MCP-compatible client like Claude Desktop or Claude API.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables running Claude Skills locally on your Mac with sandboxed execution, supporting document processing and integration with MCP-compatible AI tools while ensuring data privacy.
      451
      Apache 2.0

    TDQS

    D1.8/5.0

    Scored across 5 tools

    Disambiguation3/5

    The tools have distinct names but their purposes are unclear due to missing descriptions, making it hard to assess true overlap. 'list_prompts' and 'select_prompt' might overlap in functionality, while 'query_context' and 'get_prompt' could be ambiguous without context. The lack of descriptions forces reliance on naming alone, which introduces uncertainty.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as 'export_skill', 'get_prompt', and 'list_prompts'. There are no deviations in naming conventions, making the set predictable and easy to parse for an agent.

    Tool Count4/5

    With 5 tools, the count is reasonable for a server focused on prompts and skills, as inferred from the names. It's slightly lean but not overly sparse, suggesting a well-scoped set that could cover core operations without being overwhelming.

    Completeness2/5

    Inferred domain involves managing prompts and skills, but the tool set lacks clear CRUD coverage—there's no 'create_prompt', 'update_prompt', or 'delete_prompt', and 'export_skill' stands alone without complementary tools. The missing descriptions exacerbate gaps, making it likely agents will encounter dead ends in workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues