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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_blueprintC | Create a new blueprint in LynxPrompt |
| create_hierarchyC | Create a new hierarchy in LynxPrompt |
| delete_blueprintB | Delete a blueprint from LynxPrompt |
| delete_hierarchyB | Delete a hierarchy from LynxPrompt |
| search_blueprintsB | Search the public LynxPrompt blueprint marketplace |
| update_blueprintC | Update an existing blueprint in LynxPrompt |
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 | All blueprints for the authenticated user |
| Hierarchy list | All hierarchies for the authenticated user |
TDQS
Scored across 6 tools
Every tool targets a distinct action on either blueprints or hierarchies, with no overlap in purpose. The operations are clearly separated by resource type.
All tool names follow the verb_noun pattern using snake_case consistently. The pattern is predictable across all six tools.
Six tools is well-scoped for managing two resources (blueprints and hierarchies). Each tool serves a clear purpose without unnecessary duplication.
Blueprints have create, delete, update, and search, but no individual get/read tool. Hierarchies have create and delete but lack update and search. These are notable gaps that could cause agent failures.