Skip to main content
Glama

Was Sie erhalten

Typ

Verwendungszweck

MCP-URI / Tool-ID

Ressourcen

Blueprints, Hierarchien und Benutzerinfos schreibgeschützt durchsuchen

lynxprompt://blueprintslynxprompt://blueprint/{id}lynxprompt://hierarchieslynxprompt://hierarchy/{id}lynxprompt://user

Tools

Blueprints erstellen, aktualisieren, löschen und Hierarchien verwalten

search_blueprintscreate_blueprintupdate_blueprintdelete_blueprintcreate_hierarchydelete_hierarchy

Alles wird über einen einzigen JSON-RPC-Endpunkt (/mcp) bereitgestellt. LLMs / Agenten können: initialize -> readResource -> listTools -> callTool ... und so weiter.


Related MCP server: mcp-openapi-schema

Schnellstart (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

Sicherheitshinweis: Der HTTP-Transport lauscht standardmäßig auf 127.0.0.1:8080. Wenn Sie ihn in einem Netzwerk freigeben müssen, platzieren Sie ihn hinter einem Reverse-Proxy mit Authentifizierung.

Installation via npm (stdio-Transport)

npx lynxprompt-mcp

Oder global installieren:

npm install -g lynxprompt-mcp
lynxprompt-mcp

Dies lädt das vorkompilierte Go-Binary von GitHub Releases für Ihre Plattform herunter und führt es mit stdio-Transport aus. Erfordert mindestens ein veröffentlichtes Release.

Lokaler Build

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

Konfiguration

Variable

Standardwert

Beschreibung

LYNXPROMPT_URL

https://lynxprompt.com

URL der LynxPrompt-Instanz (ohne abschließenden /)

LYNXPROMPT_TOKEN

(erforderlich)

API-Token im Format lp_xxx

LISTEN_ADDR

127.0.0.1:8080

HTTP-Lauschadresse (Docker setzt 0.0.0.0:8080)

TRANSPORT

(leer = HTTP)

Auf stdio für stdio-Transport setzen

Fügen Sie diese in eine .env-Datei ein (aus .env.example) oder setzen Sie sie in der Umgebung.

Testen

Getestet mit dem Inspector und es funktioniert derzeit einwandfrei. Bevor Sie einen PR erstellen, stellen Sie sicher, dass sich dieser MCP-Server über dieses Medium korrekt verhält.

Beispielkonfiguration für Client-LLMs

{
  "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"
}

Credits

LynxPrompt -- Verwaltung von KI-Konfigurations-Blueprints

MCP-GO -- moderne MCP-Implementierung

GoReleaser -- einfache Multi-Architektur-Releases

Betreuer

@GeiserX.

Mitwirken

Fühlen Sie sich eingeladen, mitzumachen! Eröffnen Sie ein Issue oder senden Sie PRs.

LynxPrompt-MCP folgt dem Contributor Covenant Verhaltenskodex.

Andere MCP-Server von GeiserX

Verwandte Projekte

Projekt

Beschreibung

LynxPrompt

Selbstgehostete Plattform für KI-IDE/Tool-Regeln und Befehle via WebUI und CLI

lynxprompt-vscode

VS Code-Erweiterung für die Verwaltung von LynxPrompt KI-Konfigurationsdateien

lynxprompt-action

GitHub Action zum Synchronisieren und Validieren von KI-IDE-Konfigurationsdateien mit LynxPrompt

n8n-nodes-lynxprompt

n8n-Community-Node für LynxPrompt KI-Konfigurations-Blueprints

homebrew-lynxprompt

Homebrew-Tap für LynxPrompt CLI

Available Tools

10 tools
create_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 hierarchyA
Idempotent

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 blueprintA
DestructiveIdempotent

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 hierarchyA
DestructiveIdempotent

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 blueprintA
Read-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 hierarchyA
Read-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 blueprintsA
Read-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 hierarchiesA
Read-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 blueprintsA
Read-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 blueprintA
DestructiveIdempotent

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

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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 context
      50
      MIT