@lpm-registry/mcp-server

MCP (Model Context Protocol) server for the LPM package registry. Gives AI tools like Claude Code, Cursor, and other MCP-compatible agents access to search, browse source code, install packages, check quality, and more.

Quick Setup

If you have the LPM CLI installed, one command configures all your editors:

lpm mcp setup

This auto-detects Claude Code, Cursor, VS Code, Claude Desktop, and Windsurf, then writes the correct config to each. Authentication is handled via lpm login (stored in your OS keychain) — no tokens in config files.

The generated command is npx -y @lpm-registry/mcp-server@latest. The latest dist-tag is resolved when the editor starts, so editor restarts pick up the current published MCP server release.

For a custom registry, set LPM_REGISTRY_URL in the environment inherited by your editor or add it to the editor's MCP server environment configuration.

Related MCP server: MCPfinder

Manual Setup

If you prefer manual configuration, add to your editor's MCP config:

Claude Code

{
  "mcpServers": {
    "lpm-registry": {
      "command": "npx",
      "args": ["-y", "@lpm-registry/mcp-server@latest"]
    }
  }
}

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "lpm-registry": {
      "command": "npx",
      "args": ["-y", "@lpm-registry/mcp-server@latest"]
    }
  }
}

VS Code (.vscode/mcp.json)

{
  "servers": {
    "lpm-registry": {
      "command": "npx",
      "args": ["-y", "@lpm-registry/mcp-server@latest"]
    }
  }
}

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "lpm-registry": {
      "command": "npx",
      "args": ["-y", "@lpm-registry/mcp-server@latest"]
    }
  }
}

Authentication

LPM_TOKEN has highest priority. When it is unset, the server reads the OS keychain entry created by lpm login for the effective registry URL. Credentials are registry-scoped, so hosted, local, and custom registries do not reuse one another's tokens.

Set LPM_TOKEN explicitly for environments without keychain access:

export LPM_TOKEN=lpm_your_token_here

Registry URL

Defaults to https://lpm.dev. Override with:

export LPM_REGISTRY_URL=https://your-registry.dev

For local development, copy .env.example to .env.local and set your local registry URL. These files are gitignored.

Available Tools

Access Control

• Pool packages require a Pool subscription ($12/mo). Without one, lpm_browse_source, lpm_add, and lpm_install return an error with subscription info.

• Marketplace packages require a license purchase. Errors include a link to the package page.

• Public metadata (lpm_package_info, lpm_search, lpm_quality_report) works without auth for public packages.

Troubleshooting

"No LPM token found" Set the LPM_TOKEN environment variable in your MCP client configuration, or run lpm login first.

"Authentication required" Some tools (lpm_browse_source, lpm_add, lpm_install) require authentication. Run lpm login or set LPM_TOKEN.

"Authentication failed" Your token may be expired or revoked. Generate a new token at https://lpm.dev/dashboard/tokens or run lpm login.

"Cannot reach lpm.dev" Check your internet connection. If you're behind a proxy, ensure it allows HTTPS connections to lpm.dev.

"Package not found" Verify the package name format: owner.package-name (e.g., alice.ui-kit).

"Rate limit exceeded" Source browsing is rate limited to 30 requests per minute. Wait and retry.

"Source browsing is currently disabled" The registry has temporarily disabled source browsing. Try again later.

"Response was truncated" Use the path parameter with lpm_browse_source to request specific files or directories instead of the entire package.