lampa-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAMPA_REPO_PATH | Yes | The absolute path to the local Lampa source repository checkout |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| summarize_repoA | Summarize the Lampa snapshot — commit metadata, top-level folders, plugins, entrypoints, and npm scripts — for first-session orientation. Do not use it to read bytes ( |
| search_codeA | Search Lampa source contents for a literal or regex and return path:line plus a preview. Use this when you know a symbol or pattern; do not use it to list files by name ( |
| find_filesA | Locate repo-relative paths by filename, Lampa feature, UI component, stylesheet, or spec — a path finder, not content grep. Unlike |
| read_sourceA | Read bytes from one known path: a repo file, a src/core module, or a src/templates template. Unlike |
| resolve_edit_pathA | Map a change kind (lang, sass, template, component, plugin, core, interaction, settings) to the authoritative src/ or plugins/ path and list generated public/build copies to avoid. Call this before |
| list_catalogA | Dump one static catalog from the Lampa snapshot per call. Not a query ( |
| analyze_pluginA | Single-call report for one |
| trace_symbolA | Follow one event, component, file, or provider through the snapshot graph — not a full catalog ( |
| plan_changeA | Generate a step-by-step implementation plan with inferred targets, a reverse-ref sample, and coupling risks for a Lampa change. Call this before |
| draft_patchA | Returns TODO unified diffs as text only — does not write the repository.
Best with |
| scaffold_pluginA | Returns markdown only; does not write the repository — not a patch against existing files ( |
| validate_codeA | Run checks and hints, not catalogs ( |
| explain_docsA | Read written Lampa guides: official plugin chapters ( |
| guide_cubA | Document how Lampa talks to CUB from source — this makes no network calls of its own (pure snapshot read), and is not a substitute for cub.rip/developer. Unlike |
| guide_external_apiA | Document the real-world content/ratings/torrent-indexer/media-server APIs that Lampa plugins call — TMDB, KinoPoisk (PoiskKino + Unofficial), Alloha, MDBList, Jackett/Prowlarr/JacRed, TorrServer, Jellyfin, TheIntroDB, and the CORS-proxy pattern that fronts them. This is curated from the separate lampa-plugins repository, not the Lampa app source — unlike |
| guide_plugin_catalogA | Document how the separate lampa-plugins repository turns plugin source files into the live catalog agents install into Lampa: the extension.json/plugin-manifest.json schema, the obfuscation presets, Cloudflare Pages Functions routing, and a step-by-step publishing checklist. Curated from that repo's scripts/ and functions/, not from the Lampa app source — unlike |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| repo-overview | High-level repo structure and entrypoints. |
| repo-scripts | NPM scripts from package.json. |
| docs-index | Official Lampa plugin-guide table of contents (docs/en). Falls back to generated JSDoc if plugin docs are missing. |
| settings-catalog | All settings registrations found in the repo. |
| api-integrations | All external API call sites found in the repo. |
| cub-lampa-api | CUB API endpoints catalog extracted from Lampa source. |
| lampa-landmarks | Ordered landmark files agents should read first when working on Lampa (roles included). |
| lampa-edit-rules | What to edit vs avoid (src/plugins vs public/build). Prevents agents from changing generated copies. |
| lampa-api-surface | Keys exported on window.Lampa from src/app.js initClass (plugin-visible API). |
| lampa-plugin-guide | Official Lampa plugin development guide TOC, bootstrap snippet, and window.Lampa cheatsheet (docs/en). |
| lampa-pitfalls | Official plugin pitfalls (docs/en/11-pitfalls.md) — anti-patterns not to emit. |
| lampa-events | Condensed plugin event catalog (Listener, Player, PlayerVideo, Storage, Favorite, Keypad). |
TDQS
Scored across 16 tools
Every tool has a clearly distinct role: overview, content search, path lookup, file read, edit-path resolution, catalog dump, plugin analysis, symbol tracing, planning, patching, scaffolding, validation, or a specific documentation guide. The descriptions actively cross-reference what each tool should not be used for, making misselection unlikely.
All tool names follow a consistent snake_case verb_noun pattern, such as summarize_repo, search_code, find_files, draft_patch, and validate_code. The guide_* and explain_* prefixes create recognizable subfamilies without breaking the overall naming convention.
At 16 tools, the surface is slightly above the ideal 3–15 range, but each tool contributes to the snapshot-inspection and plugin-development workflow. The documentation guides could theoretically be consolidated, but their distinct topics make the count acceptable.
The tool set covers the full inspection-to-planning lifecycle: orient, search, read, locate, trace, catalog, plan, patch, scaffold, validate, and consult documentation. Write and execute operations are intentionally excluded as snapshot-only behavior, so the surface has no dead ends for its stated purpose.