
Connects Claude to any LynxPrompt instance for managing AI configuration blueprints. You get read-only resources for browsing blueprints and hierarchies, plus tools for search, create, update, and delete operations. Runs as either a local stdio server (via npx) or HTTP service (Docker). The HTTP mode requires bearer auth if exposed beyond localhost. Useful when you're maintaining prompt libraries or AI IDE configs across projects and want Claude to search, retrieve, or modify them without context-switching to a web UI. Built with mcp-go and includes Inspector-tested JSON-RPC endpoints.
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.
LYNXPROMPT_URL*LynxPrompt instance URL (e.g. https://lynxprompt.com)
LYNXPROMPT_TOKEN*secretLynxPrompt API token (lp_xxx format)