nexus-mcp-server
Provides read-only inspection, auditing, and documentation of a Sonatype Nexus Repository Manager 3.x instance via its REST API, including repository and security inventories, relationship graphs, content audits, drift checks, OpenAPI discovery, and optional enabled admin/write operations.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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.
flowchart LR
AI[MCP client] <-->|stdio / Streamable HTTP| Server[nexus-mcp-server]
Server <-->|REST API| Nexus[Nexus Repository 3.x]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.
Related MCP server: project-surface
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
docker run --rm -i \
-e NEXUS_URL=https://nexus.example.com \
-e NEXUS_USERNAME=readonly-user \
-e NEXUS_PASSWORD \
ghcr.io/oomchiller/nexus-mcp-server:0.2.0Images 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
{
"mcpServers": {
"nexus": {
"command": "uvx",
"args": ["--from", "git+https://github.com/oomchiller/nexus-mcp-server@v0.2.0", "nexus-mcp-server"],
"env": {
"NEXUS_URL": "https://nexus.example.com",
"NEXUS_USERNAME": "readonly-user",
"NEXUS_PASSWORD": "change-me"
}
}
}
}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.
Variable | Default | Meaning |
| unset | Nexus base URL. Without it the server starts, and calls report that Nexus is not configured. |
| unset | Basic authentication. Use a read-only Nexus account. |
|
| Verify the Nexus TLS certificate. |
| unset | PEM file of CA certificates to trust instead of the public roots; needs |
|
| HTTP timeout. |
| host of | Comma-separated hosts the client may contact. |
|
| Log level (stderr). |
|
|
|
|
| With |
|
| Lists |
|
| Restrict |
|
| Largest Nexus response accepted. |
|
| How long graph tools reuse one Knowledge Graph build; |
|
| Register prompts. |
|
| Register resources. |
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
--transport {stdio,sse,streamable-http} default stdio
--host HOST / --port PORT HTTP bind, default 127.0.0.1:8000, no authentication
--nexus-url URL overrides NEXUS_URL
--nexus-username USERNAME overrides NEXUS_USERNAME
--verify-ssl / --no-verify-ssl overrides NEXUS_VERIFY_TLS
--ca-bundle PATH overrides NEXUS_CA_BUNDLEKeep NEXUS_PASSWORD in the environment, not on the command line.
Tools
Group | Tools |
Explanation |
|
Inventory and documentation |
|
Audit |
|
Drift |
|
OpenAPI |
|
Listed only when enabled:
Tool | Requires |
|
|
|
|
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
uv sync --locked
uv run pytest
uv run ruff check . && uv run ruff format --check .
uv run mypy src testsSee CONTRIBUTING.md, ARCHITECTURE.md, DECISIONS.md and ROADMAP.md.
License
MIT; see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Read-only tools over the Safer Agentic AI framework: 239 patterns + 15 heuristics.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to deeply introspect Jira Data Center configurations — including workflows, schemes, automation, and Assets — through 76 read-only tools, without any modification capability.5MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query a repository's verified semantic model, including capabilities, ownership, contracts, constraints, impact, health, and verification status, without re-deriving project facts. It exposes read-only tools for inspecting, reasoning about, and verifying the provenance-tracked surface.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read managed Microsoft 365 client tenants, baselines, alignment scores, policies, Secure Score, Entra users/groups/roles, and audit activity, and on explicit request run assessments and queue reports. Access is read-only apart from those two run tools, which never modify tenant policies.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose deployments, releases, runbooks, tasks, tenants, and infrastructure inside an Octopus instance through its APIs. Supports read-only and write-gated modes, toolset selection, and structured REST access for both interactive use and automation.430 npmMIT