Skip to content

Claude Code Plugin

Overview

The LCP Claude Code plugin integrates the Library Context Protocol into the Claude Code agent environment. Once installed, Claude Code automatically starts lcp serve-all as an MCP server, making any pip-installed Python library available on demand without pre-built manifests. The plugin is distributed through the Claude Code marketplace, which is the recommended installation path.

Key Features

  • Marketplace distribution — installable from zazza123/lcp via the Claude Code plugin marketplace in a single command
  • Automatic MCP server startup when Claude Code opens a session
  • On-demand library resolution via resolve_library("package") — any pip-installed package, no setup per library
  • Two guided skills (lcp-universal, lcp-usage) that instruct the agent when and how to use LCP tools
  • Quick command shortcuts (/lcp:resolve, /lcp:scan) for explicit library operations
  • Dedicated library-explorer subagent for deep read-only API research
  • SessionStart hook that warns if lcp is not found on PATH
  • userConfig.registries field for configuring private or team registry URLs

Documents

  • Architecture - Plugin structure, marketplace layout, MCP server startup flow, skills and hooks design

Plugin Components

Component Location Purpose
Marketplace catalog .claude-plugin/marketplace.json Registers the repository as a Claude Code marketplace; lists available plugins and their source paths
Plugin manifest plugin/lcp/.claude-plugin/plugin.json Plugin metadata, keywords, userConfig schema; read by Claude Code during plugin install
MCP config plugin/lcp/.mcp.json Declares the MCP server entry pointing to the wrapper script
Wrapper script plugin/lcp/bin/serve.sh Validates lcp on PATH; injects --registry from userConfig; starts lcp serve-all
Hooks plugin/lcp/hooks/hooks.json SessionStart check for missing lcp installation
lcp-universal skill plugin/lcp/skills/lcp-universal/SKILL.md Teaches the agent to proactively call resolve_library before writing library code
lcp-usage skill plugin/lcp/skills/lcp-usage/SKILL.md General LCP usage guidance for development workflows
Resolve command plugin/lcp/commands/resolve.md /lcp:resolve <package> shortcut
Scan command plugin/lcp/commands/scan.md /lcp:scan <package> — scans and summarises a library
Library explorer agent plugin/lcp/agents/library-explorer.md Read-only subagent (haiku model) for deep API research

Installation

The plugin is published to the Claude Code marketplace under the zazza123/lcp namespace. After adding the marketplace, installing the plugin registers the MCP server, skills, commands, hooks, and the library-explorer subagent in one step.

/plugin marketplace add zazza123/lcp
/plugin install lcp@lcp

Local plugin directory (development)

When working on the plugin itself, the local directory can be loaded directly without going through the marketplace:

claude --plugin-dir /path/to/lcp/plugin/lcp

MCP-only (other clients)

If only the MCP server is needed without skills, hooks, or commands (e.g. Cursor, Claude Desktop), the server can be wired directly via the client's MCP configuration pointing to lcp serve-all.

  • MCP Server — The underlying MCP server that powers the plugin
  • Registry Publish — Publishing manifests to a registry used as plugin fallback

Last Updated: May 2026 Status: Implemented