lynxprompt-mcp
by GeiserX
README.md
<p align="center">
<img src="https://raw.githubusercontent.com/GeiserX/lynxprompt-mcp/main/docs/images/banner.svg" alt="lynxprompt-mcp" width="900"/>
</p>
<h1 align="center">lynxprompt-mcp</h1>
<p align="center">
<a href="https://www.npmjs.com/package/lynxprompt-mcp"><img src="https://img.shields.io/npm/v/lynxprompt-mcp?style=flat-square&logo=npm" alt="npm"/></a>
<a href="https://github.com/GeiserX/lynxprompt-mcp/actions/workflows/ci.yml"><img src="https://github.com/GeiserX/lynxprompt-mcp/actions/workflows/ci.yml/badge.svg" alt="CI"/></a>
<a href="https://codecov.io/gh/GeiserX/lynxprompt-mcp"><img src="https://codecov.io/gh/GeiserX/lynxprompt-mcp/graph/badge.svg" alt="codecov"/></a>
<a href="https://hub.docker.com/r/drumsergio/lynxprompt-mcp"><img src="https://img.shields.io/docker/pulls/drumsergio/lynxprompt-mcp?style=flat-square&logo=docker" alt="Docker Pulls"/></a>
<a href="https://github.com/GeiserX/lynxprompt-mcp/blob/main/LICENSE"><img src="https://img.shields.io/github/license/GeiserX/lynxprompt-mcp?style=flat-square" alt="License"/></a>
</p>
<p align="center"><strong>An MCP server for any LynxPrompt instance. LLMs use it to browse, search and manage AI configuration blueprints.</strong></p>
It works with [lynxprompt.com](https://lynxprompt.com) or your own self-hosted LynxPrompt, over HTTP or stdio.
## Features
- Read-only resources for blueprints, hierarchies and the current user (`lynxprompt://blueprints`, `lynxprompt://hierarchies`, `lynxprompt://user`).
- Tools to search, create, update and delete blueprints, and to create and delete hierarchies.
- One JSON-RPC endpoint (`/mcp`) over HTTP, or stdio with `TRANSPORT=stdio`.
- Listens on loopback by default; `MCP_AUTH_TOKEN` adds bearer auth when you expose it.
- Ships as a Docker image, an npm package (`npx lynxprompt-mcp`) and multi-arch Go binaries.
## Quick start
Register the npm package in your MCP client (Claude Desktop, Claude Code, Cursor); `npx` runs it over stdio:
```json
{
"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](https://github.com/GeiserX/lynxprompt-mcp/blob/main/docs/getting-started.md).
## Documentation
- [Getting started](https://github.com/GeiserX/lynxprompt-mcp/blob/main/docs/getting-started.md): Docker Compose, npm, local build
- [Configuration](https://github.com/GeiserX/lynxprompt-mcp/blob/main/docs/configuration.md): environment variables and MCP client configuration
- [Usage](https://github.com/GeiserX/lynxprompt-mcp/blob/main/docs/usage.md): resources and tools
- [Development](https://github.com/GeiserX/lynxprompt-mcp/blob/main/docs/development.md): testing, contributing, credits
- [Related projects](https://github.com/GeiserX/lynxprompt-mcp/blob/main/docs/related.md): the family and registry listings
## Related projects
[LynxPrompt](https://github.com/GeiserX/LynxPrompt), the self-hosted platform this server talks to.
## License
[GPL-3.0-or-later](https://github.com/GeiserX/lynxprompt-mcp/blob/main/LICENSE)
TDQS
B3.4/5.0
Scored across 6 tools
Disambiguation5/5
Every tool targets a distinct action on either blueprints or hierarchies, with no overlap in purpose. The operations are clearly separated by resource type.
Naming Consistency5/5
All tool names follow the verb_noun pattern using snake_case consistently. The pattern is predictable across all six tools.
Tool Count5/5
Six tools is well-scoped for managing two resources (blueprints and hierarchies). Each tool serves a clear purpose without unnecessary duplication.
Completeness3/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues