lynxprompt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LYNXPROMPT_URL | Yes | LynxPrompt instance URL | |
| LYNXPROMPT_TOKEN | Yes | LynxPrompt API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
LynxPrompt stores AI agent instruction files ("blueprints": AGENTS.md, CLAUDE.md, Cursor rules, slash commands).
Blueprints have bp_ ids. list_blueprints lists your own; search_blueprints searches the public marketplace of other people's.
get_blueprint reads any blueprint you can see (yours, your team's, public ones) with its content and content_checksum. Only the owner can update or delete one.
Before update_blueprint, call get_blueprint and pass its content_checksum as expected_checksum; a 409 means someone else changed it, so re-read and merge.
visibility PUBLIC publishes a blueprint to everyone. delete_blueprint is permanent.
A hierarchy (ha_ id) groups the blueprints of one repository; delete_hierarchy only unlinks its blueprints.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_blueprintA | Save a new blueprint (an AI agent instruction file such as AGENTS.md or CLAUDE.md) to the token user's LynxPrompt account. Each call creates a new blueprint, even with the same name; to change an existing one use update_blueprint. Private by default; visibility PUBLIC publishes it to the public marketplace. To place it in a monorepo hierarchy pass hierarchy_id and repository_path. Returns the new blueprint with its bp_ id. |
| create_hierarchyA | Create a hierarchy: a group that ties the blueprints of one repository together, for example every AGENTS.md of a monorepo. repository_root identifies the repository; if you already have a hierarchy with that repository_root, it is returned unchanged instead of a duplicate. Add blueprints to it with create_blueprint (hierarchy_id plus repository_path). Returns the hierarchy with its ha_ id. |
| delete_blueprintA | Permanently delete one of your blueprints. It cannot be restored. Confirm the id with get_blueprint or list_blueprints first. |
| delete_hierarchyA | Permanently delete one of your hierarchies. The blueprints in it are not deleted: they stay in your account, unlinked from any hierarchy. |
| get_blueprintA | Read one blueprint the token can see, including its full content and its content_checksum: your own, your team's, or a public one found with search_blueprints. Call it before update_blueprint and pass content_checksum as expected_checksum, so an edit made elsewhere in the meantime is not overwritten. Only the owner can update or delete a blueprint. For a public blueprint of someone outside your team, repository_path is only the file name. |
| get_hierarchyA | Read one of your hierarchies with every blueprint in it, both as a flat list (blueprints[], with repository_path and content_checksum) and as a tree nested by parent_id. Blueprint content is not included; use get_blueprint for that. |
| list_blueprintsA | List the blueprints owned by the user of LYNXPROMPT_TOKEN, newest change first, without their content. Use it to find a blueprint id (bp_...) for get_blueprint, update_blueprint or delete_blueprint. Paged: when has_more is true, call again with offset increased by limit. |
| list_hierarchiesA | List your hierarchies. A hierarchy groups the blueprints of one repository (for example the AGENTS.md files of a monorepo) under one repository_root. Returns ids (ha_...) for get_hierarchy and delete_hierarchy. Paged like list_blueprints. |
| search_blueprintsA | Search the public LynxPrompt marketplace of AI agent instruction files (AGENTS.md, CLAUDE.md, Cursor rules, slash commands and so on). Use it to find blueprints other people published; get_blueprint reads a result's content. To find your own blueprints use list_blueprints instead. Needs no token. Returns one page of results (templates[] with id, name, description, author, type, tags) plus total and hasMore. |
| update_blueprintA | Change one of your blueprints. Only the fields you pass change; content replaces the whole text and the old text is not kept. Read the blueprint with get_blueprint first and pass its content_checksum as expected_checksum: if someone edited it since (web UI, CLI, another agent) the call fails with 409 instead of overwriting their change. Setting visibility PUBLIC publishes it to the marketplace. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Authenticated user info | Profile of the currently authenticated LynxPrompt user |
| Blueprint list | Up to 100 most recently changed blueprints of the authenticated user (the list_blueprints tool pages past that) |
| Hierarchy list | Up to 100 hierarchies of the authenticated user (the list_hierarchies tool pages past that) |
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.