create_blueprint
Create a new blueprint in LynxPrompt
LABSCO SUMMARY
A thin store-management surface over one product, plus the marketplace search.
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.
What it is
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.
What you get
- 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.
Requirements
A LynxPrompt account and an API token in lp_ format, set as LYNXPROMPT_TOKEN; LYNXPROMPT_URL points at your instance and defaults to https://lynxprompt.com. 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.
Setup effort
One command plus a key — npx lynxprompt-mcp, then supply credentials
USE CASES
01
Publishing a prompt you keep rewriting
Check whether the marketplace already has something close, write your own version with a visibility you choose, and revise it in place as it changes.
02
Grouping blueprints around one repository
Create the hierarchy against the repository path, file the blueprints that belong to it, and remove the whole grouping when the project ends.
03
Retiring blueprints that no longer apply
Search for the ones matching the category or tag you are clearing out, then delete them by id.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_hierarchy
Create a new hierarchy in LynxPrompt
delete_blueprint
Delete a blueprint from LynxPrompt
delete_hierarchy
Delete a hierarchy from LynxPrompt
search_blueprints
Search the public LynxPrompt blueprint marketplace
update_blueprint
Update an existing blueprint in LynxPrompt
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. Reading happens through five lynxprompt:// resources, so the tools are mostly writes plus one search. It needs a LynxPrompt instance and an lp_ token.
Requires
- npx on PATH
- LYNXPROMPT_TOKEN in your environment
- LYNXPROMPT_URL in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"lynxprompt-mcp": {
"command": "npx",
"args": [
"-y",
"lynxprompt-mcp"
],
"env": {
"LYNXPROMPT_URL": "https://lynxprompt.com",
"LYNXPROMPT_TOKEN": "<YOUR_LYNXPROMPT_TOKEN>"
}
}
}
}npx
TERMINAL
npx lynxprompt-mcp
