Skip to main content
Glama
Sign In
@lpm-registry/mcp-server

@lpm-registry/mcp-server

Official
by lpm-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

@lpm-registry/mcp-server

This package is retired and gets no more updates. The LPM CLI serves MCP itself from version 0.86.0, as lpm mcp serve. It has the current LPM.dev Registry tools and tools that install, add, and audit packages in your projects.

Move to lpm mcp serve

Upgrade the LPM CLI to 0.86.0 or later, for example with lpm self-update. Then point your editors at its server:

lpm mcp setup

Restart your editors. lpm mcp setup writes the server entry named lpm-registry, the name earlier setups and this README used, so it replaces that entry. Remove an entry you named differently with lpm mcp remove <name>, and edit project files such as .vscode/mcp.json by hand. See MCP servers in the LPM CLI documentation.

To use the registry tools without the LPM CLI, connect your MCP client to https://lpm.dev/mcp. It signs you in through LPM.dev in your browser. See the LPM.dev MCP server.

Related MCP server: MCPfinder

What this last version does

Editors may still start this package, for example through npx -y @lpm-registry/mcp-server@latest.

  • If it finds LPM CLI 0.86.0 or later, it starts lpm mcp serve in its place, and the editor gets the LPM CLI's server. It looks for the CLI at LPM_CLI_PATH, or as lpm on PATH outside the current project.

  • Otherwise it serves the tools of earlier versions, and tells the editor's agent that it is retired. lpm mcp serve in LPM CLI releases before 0.86.0 runs this package, so those releases keep working until you upgrade.

Renamed tools

The LPM CLI's server combines some tools:

Earlier tools

Now

lpm_package_info, lpm_quality_report, lpm_marketplace_info, lpm_api_docs, lpm_llm_context, lpm_package_context

lpm_package

lpm_search_owners, lpm_packages_by_owner

lpm_owner

lpm_user_info, lpm_pool_stats

lpm_account

lpm_search, lpm_package_skills, lpm_browse_source, lpm_docs, lpm_install, lpm_add, and lpm_audit keep their names. lpm_install, lpm_add, and lpm_audit now take projectPath, the absolute path of the project's directory.

License

ISC

Available Tools

17 tools
lpm_addA

Add an LPM package to the project by extracting source files for customization. Use for UI components, blocks, templates, and MCP servers. Requires LPM CLI installed.

Inputs: name (required), version, path, alias, +4 more.

lpm_api_docsA

Get structured API documentation for an LPM package — functions, classes, interfaces, type aliases, enums, and variables with signatures, params, return types, and descriptions. Use this to understand how to use a package before installing it.

Inputs: name (required), version.

lpm_auditA

Run a security audit on the project's LPM dependencies. Returns behavioral tags (eval, childProcess, shell, dynamicRequire), AI security findings, quality scores, and lifecycle scripts. Requires LPM CLI installed and authentication.

Inputs: path.

lpm_browse_sourceA

LAST RESORT: Browse source code of an LPM package remotely. Only use this when you cannot install the package (e.g., evaluating before purchase, checking capabilities without access). If you can install the package, prefer lpm_add or lpm_install first, then read the local files directly — it is faster.

Requires authentication. Pool packages require Pool subscription, marketplace packages require a license.

If you must use this tool: fetch directory paths (e.g., "src") to get multiple files in one request rather than individual files.

Inputs: name (required), version, path.

lpm_docsA

Search or read LPM documentation. Use this when the user asks how to use LPM itself — setup, CLI commands, publishing, CI/CD, Swift registry, organizations, billing, etc. Without parameters: returns the docs index. With page: returns that specific page. With query: searches page titles and returns matching content.

Inputs: page, query.

lpm_installB

Install an LPM package as a managed dependency. JS packages go to node_modules (like npm install), Swift packages edit Package.swift via SE-0292. Use for libraries, utilities, and SDKs. Requires LPM CLI installed.

Inputs: name (required), version.

lpm_llm_contextA

Get an LLM-optimized usage guide for an LPM package — purpose, quickStart code, key exports with signatures, common usage patterns, gotchas, and when to use it. Use this to quickly understand how to use a package correctly.

Inputs: name (required), version.

lpm_marketplace_infoA

Get marketplace information for an LPM package — pricing, licensing model, seat management, and purchase status. Use this before recommending a paid package to check cost and access.

Inputs: name (required).

lpm_package_contextA

Get complete context for an LPM package in a single call — combines condensed package metadata (name, version, description, install method, dependencies), structured API docs (functions, classes, types), and LLM usage guide (quickStart, patterns, gotchas). Use this BEFORE installing to evaluate and understand a package. If the package is already installed locally, prefer reading local files directly and use lpm_package_skills for usage patterns instead.

Inputs: name (required), version.

lpm_package_infoA

Get metadata for an LPM package including versions, description, downloads, AI analysis, compatibility, and readme

Inputs: name (required).

lpm_packages_by_ownerB

List packages published by a specific user or organization on the LPM registry. Shows public packages with distribution mode.

Inputs: owner (required), limit.

lpm_package_skillsA

Get author-written Agent Skills for an LPM package — usage patterns, anti-patterns, gotchas, and best practices for code generation. Use this when BUILDING with an already-installed package. Skills are version-specific and automatically resolve from local package.json if no version is specified.

Inputs: name (required), version.

lpm_pool_statsA

Get your Pool revenue sharing earnings estimate for the current month. Shows per-package breakdown with installs, share %, and estimated earnings. Requires authentication.

Inputs: no named parameters.

lpm_quality_reportB

Get the quality score and detailed check breakdown for an LPM package (27 checks across documentation, code, testing, health)

Inputs: name (required).

lpm_searchB

Search LPM packages using natural language or structured filters. Uses hybrid semantic search for natural language queries. Supports filtering by category, distribution mode, package type, ecosystem, license, and more.

Inputs: query, category, ecosystem, distribution, +7 more.

lpm_search_ownersB

Search for users or organizations on the LPM registry by name or username.

Inputs: query (required), limit.

lpm_user_infoA

Get information about the authenticated LPM user including organizations, plan tier, pool access, and usage limits. Requires authentication.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: package management, information retrieval, search, user/owner operations, etc. Overlapping tools like lpm_api_docs, lpm_llm_context, and lpm_package_context are well-differentiated by the specific type of information they provide, and descriptions clearly state when to use each.

    Naming Consistency5/5

    All tools follow a consistent 'lpm_verb_noun' pattern using lowercase snake_case (e.g., lpm_add, lpm_api_docs, lpm_search_owners). Naming is predictable and makes it easy to infer a tool's function from its name.

    Tool Count5/5

    17 tools is well-scoped for a package registry server, covering the full workflow: discovery (search, info, docs), installation (add, install, audit), usage (browse_source, package_skills), and administrative actions (user_info, pool_stats). Each tool earns its place.

    Completeness5/5

    The tool surface is comprehensive for LPM registry operations, including search, package metadata, installation methods, source browsing, auditing, documentation, user/owner info, marketplace info, and pool earnings. No obvious gaps for common tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers