@verdaccio/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERDACCIO_URL | No | Base URL of your Verdaccio instance | http://localhost:4873 |
| VERDACCIO_TOKEN | No | Bearer token for authenticated registries |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_registryA | Start the Verdaccio registry (if not already running) and return its URL. When no VERDACCIO_URL is configured, an embedded registry is started automatically on a random local port. |
| find_packageB | Search for a private package in the Verdaccio registry by name or keyword |
| get_packageB | Get detailed metadata for a specific package (and optionally a specific version) from Verdaccio |
| add_userB | Register a new user in the Verdaccio registry. Returns a Bearer token on success. |
| loginB | Authenticate with the Verdaccio registry using username and password. Returns a Bearer token. |
| get_profileA | Get the profile of the currently authenticated user in Verdaccio |
| list_tokensA | List all API tokens for the currently authenticated user in Verdaccio |
| create_tokenC | Create a new API token for the currently authenticated user in Verdaccio |
| delete_tokenC | Delete an API token by its key from Verdaccio |
| publish_packageC | Publish a package to the Verdaccio registry by name and version. Generates the required package metadata automatically. |
| unpublish_packageB | Unpublish a specific version of a package from the Verdaccio registry. Removes the version from metadata and deletes its tarball. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a clearly distinct resource+action: package lifecycle (publish/unpublish/get/find), registry lifecycle (start_registry), user auth (add_user/login/get_profile), and token management (list/create/delete). The only near-neighbors, add_user vs login and find_package vs get_package, are differentiated by register-vs-authenticate and search-vs-detail respectively.
Nearly all tools follow a clean snake_case verb_noun pattern (publish_package, create_token, get_profile). The single-verb 'login' is a minor deviation from the verb_noun convention but is still readable and unambiguous.
11 tools sit comfortably in the well-scoped 3-15 range and each maps to a needed registry operation. No redundant or filler tools are present.
Covers the main registry workflows: publish/unpublish, discovery, authentication, and full token CRUD. Minor gaps exist (no whole-package removal or metadata update beyond publish, no logout), but these are workable rather than blocking.