lynxprompt-mcp
제공 기능
유형 | 용도 | MCP URI / 도구 ID |
리소스 | 청사진, 계층 구조 및 사용자 정보 읽기 전용 탐색 |
|
도구 | 청사진 생성, 업데이트, 삭제 및 계층 구조 관리 |
|
모든 기능은 단일 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 릴리스에서 플랫폼에 맞는 사전 빌드된 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) | stdio 전송을 사용하려면 |
.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 -- 간편한 멀티 아키텍처 릴리스
관리자
기여
언제든 참여해 주세요! 이슈를 열거나 PR을 제출해 주십시오.
LynxPrompt-MCP는 Contributor Covenant 행동 강령을 따릅니다.
GeiserX의 다른 MCP 서버
cashpilot-mcp — 수동 소득 모니터링
duplicacy-mcp — 백업 상태 모니터링
genieacs-mcp — TR-069 장치 관리
pumperly-mcp — 연료 및 EV 충전 가격
telegram-archive-mcp — 텔레그램 메시지 아카이브
관련 프로젝트
프로젝트 | 설명 |
WebUI 및 CLI를 통한 AI IDE/도구 규칙 및 명령을 위한 자체 호스팅 플랫폼 | |
LynxPrompt AI 구성 파일 관리를 위한 VS Code 확장 프로그램 | |
AI IDE 구성 파일을 LynxPrompt와 동기화하고 검증하기 위한 GitHub Action | |
LynxPrompt AI 구성 청사진을 위한 n8n 커뮤니티 노드 | |
LynxPrompt CLI용 Homebrew 탭 |
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-