lynxprompt-mcp
Related Servers
Alternatives to lynxprompt-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for PromptHub. Enables publishing, fetching, listing, updating, and searching prompt repositories from Claude Code or Codex.-
- FlicenseCqualityBmaintenanceMCP server that exposes the Lyzr Enterprise API as tools, resources, and prompts, allowing users to bring their own Lyzr API key to access a wide range of agent and RAG capabilities.100-
- FlicenseAqualityDmaintenanceAn MCP server that provides AI clients with access to developer documentation via llms.txt files. Exposes tools, resources, and prompts.31-
- AlicenseBqualityDmaintenanceAn MCP server that provides LLMs access to other LLMs456 npm83MIT
- AlicenseNot gradedqualityDmaintenanceA small, local, network-free MCP server for the RISEN prompt-engineering framework. It gives any MCP client tools to build, validate, save, and reuse structured prompts.8MIT
- AlicenseNot gradedqualityDmaintenanceA MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context50MIT
TDQS
Scored across 10 tools
Every tool maps to a distinct resource (blueprint vs hierarchy) plus a distinct action, and the descriptions explicitly resolve the two potentially confusable pairs: list_blueprints (own) vs search_blueprints (public marketplace), and create_blueprint (always new) vs update_blueprint (modify existing). An agent can pick the right tool without guessing.
Perfect verb_noun snake_case pattern throughout: create_/get_/list_/update_/delete_/search_ combined with _blueprint or _hierarchy. The two nouns mirror the two resources, so the naming itself reinforces the mental model.
10 tools for a two-resource domain (blueprints and hierarchies) with full lifecycle plus marketplace search is well-scoped; each tool earns its place and none is redundant.
Blueprints have full coverage: create, get, list, search, update, delete, with optimistic-concurrency via content_checksum. Hierarchies cover create/get/list/delete but have no update operation (no rename, and create_hierarchy returns the existing one unchanged on duplicate repository_root), and there is no explicit way to unlink a blueprint from a hierarchy without deleting it.