LPM.dev Registry MCP Server

The LPM.dev Registry MCP Server gives compatible coding agents current package, publisher, quality, access, and documentation data through the Model Context Protocol.

It runs locally through npm and talks to LPM.dev Registry APIs. A few tools also invoke the installed LPM CLI to change the current project.

Configure a Client

The server is published on npm as @lpm-registry/mcp-server.

Add this entry to an MCP client that uses an mcpServers map:

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

VS Code uses the same command and arguments under its servers map. Restart the client or begin a new agent session after changing its configuration.

@latest picks up new tools automatically. Replace it with an exact published version if your environment requires a fixed executable.

Public package discovery and documentation tools can run without a token. Private package access, account data, Pool earnings, source browsing, and project-changing actions require LPM.dev Registry authentication.

Provide LPM_TOKEN in the MCP server process environment for authenticated tools. Treat it as a secret: do not commit a token in project MCP configuration.

Create and manage Registry tokens from Dashboard Settings > Tokens.

Available Tools

The current server registers 17 tools.

Discovery and Documentation

Tool	Purpose
`lpm_search`	Search packages by intent or structured filters
`lpm_package_info`	Read package metadata, versions, access information, compatibility, and README
`lpm_quality_report`	Read the current Registry quality report
`lpm_search_owners`	Search users and organizations
`lpm_packages_by_owner`	List public packages from one publisher
`lpm_docs`	Search or read lpm.dev documentation

Package Context

Tool	Purpose
`lpm_package_context`	Read condensed metadata, API documentation, usage context, and package skills together
`lpm_api_docs`	Read structured exports, signatures, parameters, and return types
`lpm_llm_context`	Read the generated quick start, common patterns, gotchas, and selection guidance
`lpm_package_skills`	Read author-published Agent Skills for a package version
`lpm_browse_source`	Browse entitled package source before installing it

When a version is omitted, the context, API documentation, usage-context, and package-skill tools first look for a matching dependency in the local package.json, then fall back to the latest available version.

Access and Account Data

Tool	Purpose
`lpm_marketplace_info`	Inspect Marketplace pricing, licensing, seats, and current access
`lpm_pool_stats`	Read the authenticated author's current-period Pool estimate
`lpm_user_info`	Read the authenticated account, organizations, plan, and limits

Project Actions

Tool	Purpose
`lpm_add`	Run source delivery through LPM CLI
`lpm_install`	Install a managed JavaScript or Swift dependency through LPM CLI
`lpm_audit`	Run the LPM CLI dependency audit for a local project

These tools execute commands in the project. Review the proposed tool call and target directory before approving it in your MCP client.

Example Requests

“Find a small TypeScript validation package in the Pool.”
“Show the API and common patterns for @lpm.dev/acme.form-kit.”
“Does this Marketplace package require a purchase for my account?”
“Install this package as a dependency.”
“Audit this project’s dependencies.”

For the server source and current releases, see github.com/lpm-dev/mcp-server.