PromStack MCP Server
Related Servers
Alternatives to PromStack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables users to list, retrieve, and compile their Langfuse prompts—including text and chat prompts with variable substitution—directly from MCP-compatible clients such as Claude Desktop and Cursor. It also exposes equivalent tools for clients that lack prompt capability support, with cursor-based pagination for browsing.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop and Cursor to discover, list, and retrieve prompts stored in Langfuse, compiling them with supplied variables on demand. It exposes both prompt capabilities and equivalent tools so clients without prompt support can still fetch prompts (limited to those labeled production).-
- AlicenseNot gradedqualityBmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityCmaintenanceConnects MCP clients (Claude Desktop, Cursor, Cline, Zed) to llmsproxy.ai, exposing chat, coding, and retrieval capabilities as MCP tools, resources, and prompts.6 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables users to list, retrieve, and compile Langfuse prompts, including text and chat prompts, through MCP-compatible clients. Supports prompt discovery, variable substitution, and paginated access via prompts and tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI applications to access and manage your saved Prompt Petal prompts, allowing you to list, use, add, and improve them from any MCP client.MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.