lynxprompt-mcp
你将获得
类型 | 用途 | MCP URI / 工具 ID |
资源 (Resources) | 只读浏览蓝图、层级和用户信息 |
|
工具 (Tools) | 创建、更新、删除蓝图并管理层级 |
|
所有功能均通过单一 JSON-RPC 端点 (/mcp) 暴露。
LLM / 智能体可以执行:initialize -> readResource -> listTools -> callTool 等操作。
Related MCP server: mcp-openapi-schema
快速开始 (Docker Compose)
services:
lynxprompt-mcp:
image: drumsergio/lynxprompt-mcp:latest
ports:
- "127.0.0.1:8080:8080"
environment:
- LYNXPROMPT_URL=https://lynxprompt.com
- LYNXPROMPT_TOKEN=lp_xxx安全提示: HTTP 传输默认监听
127.0.0.1:8080。如果需要将其暴露在网络上,请将其置于带有身份验证的反向代理之后。
通过 npm 安装 (stdio 传输)
npx lynxprompt-mcp或者全局安装:
npm install -g lynxprompt-mcp
lynxprompt-mcp这将从 GitHub Releases 为您的平台下载预构建的 Go 二进制文件,并使用 stdio 传输运行它。需要至少有一个 已发布的版本。
本地构建
git clone https://github.com/GeiserX/lynxprompt-mcp
cd lynxprompt-mcp
# (optional) create .env from the sample
cp .env.example .env && $EDITOR .env
go run ./cmd/server配置
变量 | 默认值 | 描述 |
|
| LynxPrompt 实例 URL(末尾不带 /) |
| (必填) |
|
|
| HTTP 监听地址(Docker 设置为 |
| (空 = HTTP) | 设置为 |
将它们放入 .env 文件(参考 .env.example)或在环境变量中设置。
测试
已使用 Inspector 进行测试,目前完全可用。在提交 PR 之前,请确保此 MCP 服务器通过该媒介表现良好。
客户端 LLM 的配置示例
{
"schema_version": "v1",
"name_for_human": "LynxPrompt-MCP",
"name_for_model": "lynxprompt_mcp",
"description_for_human": "Browse, search, and manage AI configuration blueprints from LynxPrompt.",
"description_for_model": "Interact with a LynxPrompt instance that stores AI configuration blueprints. First call initialize, then reuse the returned session id in header \"Mcp-Session-Id\" for every other call. Use readResource to fetch URIs that begin with lynxprompt://. Use listTools to discover available actions and callTool to execute them.",
"auth": { "type": "none" },
"api": {
"type": "jsonrpc-mcp",
"url": "http://localhost:8080/mcp",
"init_method": "initialize",
"session_header": "Mcp-Session-Id"
},
"logo_url": "https://lynxprompt.com/logo.png",
"contact_email": "acsdesk@protonmail.com",
"legal_info_url": "https://github.com/GeiserX/lynxprompt-mcp/blob/main/LICENSE"
}致谢
LynxPrompt -- AI 配置蓝图管理
MCP-GO -- 现代 MCP 实现
GoReleaser -- 轻松实现多架构发布
维护者
贡献
欢迎参与!提交 Issue 或提交 PR。
LynxPrompt-MCP 遵循 Contributor Covenant 行为准则。
GeiserX 的其他 MCP 服务器
cashpilot-mcp — 被动收入监控
duplicacy-mcp — 备份健康监控
genieacs-mcp — TR-069 设备管理
pumperly-mcp — 燃油和电动汽车充电价格
telegram-archive-mcp — Telegram 消息归档
相关项目
项目 | 描述 |
通过 WebUI 和 CLI 管理 AI IDE/工具规则和命令的自托管平台 | |
用于 LynxPrompt AI 配置文件管理的 VS Code 扩展 | |
用于同步和验证 AI IDE 配置文件与 LynxPrompt 的 GitHub Action | |
用于 LynxPrompt AI 配置蓝图的 n8n 社区节点 | |
LynxPrompt CLI 的 Homebrew tap |
Available Tools
10 toolscreate_blueprintCreate blueprintA
Save a new blueprint (an AI agent instruction file such as AGENTS.md or CLAUDE.md) to the token user's LynxPrompt account. Each call creates a new blueprint, even with the same name; to change an existing one use update_blueprint. Private by default; visibility PUBLIC publishes it to the public marketplace. To place it in a monorepo hierarchy pass hierarchy_id and repository_path. Returns the new blueprint with its bp_ id.
Inputs: name (required), content (required), tags, type, +7 more. Returns: success, blueprint
create_hierarchyCreate hierarchyAIdempotent
Create a hierarchy: a group that ties the blueprints of one repository together, for example every AGENTS.md of a monorepo. repository_root identifies the repository; if you already have a hierarchy with that repository_root, it is returned unchanged instead of a duplicate. Add blueprints to it with create_blueprint (hierarchy_id plus repository_path). Returns the hierarchy with its ha_ id.
Inputs: name (required), repository_root (required), description. Returns: tree, message, success, hierarchy, +2 more
delete_blueprintDelete blueprintADestructiveIdempotent
Permanently delete one of your blueprints. It cannot be restored. Confirm the id with get_blueprint or list_blueprints first.
Inputs: id (required). Returns: message, success
delete_hierarchyDelete hierarchyADestructiveIdempotent
Permanently delete one of your hierarchies. The blueprints in it are not deleted: they stay in your account, unlinked from any hierarchy.
Inputs: id (required). Returns: message, success
get_blueprintGet blueprintARead-onlyIdempotent
Read one blueprint the token can see, including its full content and its content_checksum: your own, your team's, or a public one found with search_blueprints. Call it before update_blueprint and pass content_checksum as expected_checksum, so an edit made elsewhere in the meantime is not overwritten. Only the owner can update or delete a blueprint. For a public blueprint of someone outside your team, repository_path is only the file name.
Inputs: id (required). Returns: success, blueprint
get_hierarchyGet my hierarchyARead-onlyIdempotent
Read one of your hierarchies with every blueprint in it, both as a flat list (blueprints[], with repository_path and content_checksum) and as a tree nested by parent_id. Blueprint content is not included; use get_blueprint for that.
Inputs: id (required). Returns: tree, message, success, hierarchy, +2 more
list_blueprintsList my blueprintsARead-onlyIdempotent
List the blueprints owned by the user of LYNXPROMPT_TOKEN, newest change first, without their content. Use it to find a blueprint id (bp_...) for get_blueprint, update_blueprint or delete_blueprint. Paged: when has_more is true, call again with offset increased by limit.
Inputs: limit, offset, visibility. Returns: limit, total, offset, has_more, +1 more
list_hierarchiesList my hierarchiesARead-onlyIdempotent
List your hierarchies. A hierarchy groups the blueprints of one repository (for example the AGENTS.md files of a monorepo) under one repository_root. Returns ids (ha_...) for get_hierarchy and delete_hierarchy. Paged like list_blueprints.
Inputs: limit, offset. Returns: limit, total, offset, has_more, +1 more
search_blueprintsSearch marketplace blueprintsARead-onlyIdempotent
Search the public LynxPrompt marketplace of AI agent instruction files (AGENTS.md, CLAUDE.md, Cursor rules, slash commands and so on). Use it to find blueprints other people published; get_blueprint reads a result's content. To find your own blueprints use list_blueprints instead. Needs no token. Returns one page of results (templates[] with id, name, description, author, type, tags) plus total and hasMore.
Inputs: page, sort, tags, type, +3 more. Returns: total, hasMore, templates, popularTags
update_blueprintUpdate blueprintADestructiveIdempotent
Change one of your blueprints. Only the fields you pass change; content replaces the whole text and the old text is not kept. Read the blueprint with get_blueprint first and pass its content_checksum as expected_checksum: if someone edited it since (web UI, CLI, another agent) the call fails with 409 instead of overwriting their change. Setting visibility PUBLIC publishes it to the marketplace.
Inputs: id (required), name, tags, type, +6 more. Returns: success, blueprint
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Every tool maps to a distinct resource (blueprint vs hierarchy) plus a distinct action, and the descriptions explicitly resolve the two potentially confusable pairs: list_blueprints (own) vs search_blueprints (public marketplace), and create_blueprint (always new) vs update_blueprint (modify existing). An agent can pick the right tool without guessing.
Perfect verb_noun snake_case pattern throughout: create_/get_/list_/update_/delete_/search_ combined with _blueprint or _hierarchy. The two nouns mirror the two resources, so the naming itself reinforces the mental model.
10 tools for a two-resource domain (blueprints and hierarchies) with full lifecycle plus marketplace search is well-scoped; each tool earns its place and none is redundant.
Blueprints have full coverage: create, get, list, search, update, delete, with optimistic-concurrency via content_checksum. Hierarchies cover create/get/list/delete but have no update operation (no rename, and create_hierarchy returns the existing one unchanged on duplicate repository_root), and there is no explicit way to unlink a blueprint from a hierarchy without deleting it.
Maintenance
Related MCP Connectors
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
MCP server for generating rough-draft project plans from natural-language prompts.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that provides LLMs access to other LLMs456 npm83MIT
- AlicenseNot gradedqualityDmaintenanceA MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context50MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for PromptHub. Enables publishing, fetching, listing, updating, and searching prompt repositories from Claude Code or Codex.-
- FlicenseAqualityDmaintenanceAn MCP server that provides AI clients with access to developer documentation via llms.txt files. Exposes tools, resources, and prompts.31-