Lynxprompt Mcp

What is Lynxprompt Mcp?

Lynxprompt Mcp is a small bridge that exposes any LynxPrompt instance as an MCP (Model Context Protocol) server. It allows LLMs and AI agents to browse, search, and manage AI configuration blueprints via resources and tools over a JSON-RPC endpoint.

How to use Lynxprompt Mcp?

Deploy with Docker Compose (drumsergio/lynxprompt-mcp:latest) and set LYNXPROMPT_URL and LYNXPROMPT_TOKEN environment variables. Alternatively, install via npm (npx lynxprompt-mcp) or build locally with Go (go run ./cmd/server). The server listens on 127.0.0.1:8080 by default; switch to stdio transport by setting TRANSPORT=stdio.

Key features of Lynxprompt Mcp

• Exposes LynxPrompt blueprints and hierarchies as MCP resources.
• Provides tools to search, create, update, and delete blueprints.
• Supports creation and deletion of hierarchy nodes.
• Runs over HTTP (single endpoint /mcp) or stdio transport.
• Configurable via environment variables or .env file.
• Deployable with Docker, npm, or local Go build.

Use cases of Lynxprompt Mcp

• Allow an LLM to browse available AI configuration blueprints from a LynxPrompt instance.
• Let an agent search for specific blueprints and retrieve their full details.
• Enable programmatic creation, update, or deletion of blueprints via tool calls.
• Manage hierarchy structures (create/delete nodes) from within an LLM workflow.
• Integrate blueprints into AI IDEs or custom tools that support the Model Context Protocol.

FAQ from Lynxprompt Mcp

What exactly does Lynxprompt Mcp do?

It acts as a bridge that translates LynxPrompt's API into the Model Context Protocol, letting LLMs read resources like blueprints and hierarchies, and call tools to manage them.

What are the dependencies or runtime requirements?

You need a running LynxPrompt instance with a valid API token (lp_xxx format). For deployment, you can use Docker, Node.js (via npm), or Go 1.24+.

Where does data live?

All blueprint and hierarchy data resides on the LynxPrompt instance you connect to; Lynxprompt Mcp only proxies requests and does not store any data locally.

What transports and authentication are supported?

The server supports HTTP (JSON-RPC over /mcp) and stdio transports. Authentication uses a Bearer token for HTTP via the MCP_AUTH_TOKEN environment variable; the LynxPrompt API token is required for backend calls.

Are there any known limits?

The README does not mention specific limits. The server has been tested with the MCP Inspector and works fully.