The six tools map one-to-one onto create, update, delete and search, which means what you gain is keeping blueprints where LynxPrompt keeps them without switching windows — there is no tool that renders, applies or even reads back a blueprint, only ones that manage the record. This one is GPL-3.0, which matters if you intend to ship a product built around the server rather than run it for yourself.
A client for LynxPrompt with 6 tools: create, update and delete for blueprints, create and delete for hierarchies anchored to a repository_root, and a search over the public LynxPrompt blueprint marketplace.
- Blueprints written from the assistant rather than pasted into a web form: create_blueprint takes a name, a description and a content body under a type and a visibility setting, and update_blueprint revises any of those against an existing id.
- A marketplace you can read before you write: search_blueprints queries the public LynxPrompt blueprint marketplace by free-text query, category, tags and type.
- Blueprints anchored to real code: create_hierarchy takes a name, a description and a repository_root, so a group of blueprints is tied to the repository path it belongs to.
- Clean-up in the same place as creation: delete_blueprint and delete_hierarchy each remove an item by the id it was created with.
No account and no key. create_hierarchy takes a repository_root path, and update_blueprint, delete_blueprint and delete_hierarchy all work from the id returned when the item was created, so nothing here is addressable by name alone.
One command plus a key — npx lynxprompt-mcp, then supply credentials