
Sonatype Nexus
io.github.oomchillerPublished by GitHub account oomchillerv0.2.1Updated Nov 4, 2026
Read-only-first Sonatype Nexus Repository 3 inspection, audit and documentation.
The publisher's own server: Dependency Management Mcp Server
Overview
Sonatype Nexus's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Sonatype Nexus in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Sonatype Nexus MCP Server
A Model Context Protocol server that lets AI assistants inspect, audit and document a Sonatype Nexus Repository Manager 3.x instance. It is read-only by default; administrative tools are not even listed unless you enable them.
Features
- Inventory of repositories, blob stores, tasks, cleanup policies, routing rules, content selectors, users, roles and privileges, as far as the configured account can see them.
- A relationship graph (repository → blob store, group → members, repository → cleanup policy, role → privilege) behind architecture explanations, risk checks and generated Markdown documentation.
- Bounded full-content audit of one repository, with completion evidence.
- Drift check of repositories against a declared state.
- OpenAPI discovery of the instance's REST operations.
- Every tool declares
readOnlyHint,destructiveHint,idempotentHintandopenWorldHint; outputs and logs redact the configured password and secret-looking keys. - Starts without configuration, so clients and registries can list its tools; calls then report what is missing.
Used in production in read-only mode on Nexus Pro 3.96.1-01; partially verified on OSS 3.70. See docs/COMPATIBILITY.md.
Quick start
The server is listed in the MCP Registry
as io.github.oomchiller/nexus-mcp-server; registry-aware clients can install
it from there. Manual setup:
Container
Images are published for linux/amd64 and linux/arm64, run as an
unprivileged user over stdio, and are configured through the environment
only. Release digests are listed on the
releases page.
Local process
More client examples (Claude Desktop, Codex CLI, Gemini CLI) are in examples/.
Configuration
Settings come from the environment or a .env file in the working directory.
Token authentication is not implemented.
The server does not read SSL_CERT_FILE or the system trust store. For a
Nexus behind a private CA, set NEXUS_CA_BUNDLE rather than disabling
verification. An unreadable bundle, or a bundle with verification disabled,
stops the server at startup.
Gateways that run several instances side by side and prefix only tool names
(Docker MCP Gateway) should set NEXUS_MCP_ENABLE_PROMPTS=false and
NEXUS_MCP_ENABLE_RESOURCES=false.
Command line
Keep NEXUS_PASSWORD in the environment, not on the command line.
Tools
Listed only when enabled:
Resources: nexus://instance/summary, nexus://repositories,
nexus://blobstores, nexus://tasks, nexus://cleanup-policies,
nexus://security/summary, nexus://architecture, nexus://knowledge_graph.
Prompts: nexus_audit_prompt, nexus_iac_drift_prompt.
Limits worth knowing: drift compares repository name, format and type only; risk checks cover a small set of graph rules; findings are only as complete as the REST APIs visible to the account. Optional endpoints that are missing for version, edition or permission reasons appear as limitations, not failures.
Safety
- Read-only by default. Write tools and the raw API are not listed unless enabled, and every write is still checked against the mode at call time.
- The client contacts only
NEXUS_ALLOWED_HOSTSand only paths relative toNEXUS_URL. - Redaction is defence in depth, not a substitute for a least-privilege Nexus account. See SECURITY.md.
Development
See CONTRIBUTING.md, ARCHITECTURE.md, DECISIONS.md and ROADMAP.md.
License
MIT; see LICENSE.
Source: README.md at commit 1c6f8ef
Tools
0Version history
1- v0.2.1LatestNov 4, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
