MCP server for LynxPrompt — browse, search, and manage AI configuration blueprints
Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y lynxprompt-mcp
MCP client config
{
"mcpServers": {
"lynxprompt": {
"command": "npx",
"args": [
"-y",
"lynxprompt-mcp"
]
}
}
}Run
docker run -i --rm drumsergio/lynxprompt-mcp:v0.1.2
MCP client config
{
"mcpServers": {
"lynxprompt": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"drumsergio/lynxprompt-mcp:v0.1.2"
]
}
}
}
An MCP server for any LynxPrompt instance. LLMs use it to browse, search and manage AI configuration blueprints.
It works with lynxprompt.com or your own self-hosted LynxPrompt, over HTTP or stdio.
lynxprompt://blueprints, lynxprompt://hierarchies, lynxprompt://user)./mcp) over HTTP, or stdio with TRANSPORT=stdio.MCP_AUTH_TOKEN adds bearer auth when you expose it.npx lynxprompt-mcp) and multi-arch Go binaries.Register the npm package in your MCP client (Claude Desktop, Claude Code, Cursor); npx runs it over stdio:
{
"mcpServers": {
"lynxprompt": {
"command": "npx",
"args": ["-y", "lynxprompt-mcp"],
"env": { "LYNXPROMPT_TOKEN": "lp_..." }
}
}
}
For a self-hosted instance add LYNXPROMPT_URL to env. Docker Compose, the HTTP server and local builds are in Getting started.
LynxPrompt, the self-hosted platform this server talks to.