Developer · Local MCP server
Maven Decoder
Lets AI agents read the real source of any Maven dependency, decompiled from ~/.m2 or Central.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.salitaba/maven-decoder-mcp- Version
- 1.3.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm, PyPI
- Published
- 2026-09-09
- Updated
- 2026-09-09
- Publisher
- salitaba (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/salitaba) · how
- Website
- github.com/salitaba/maven-decoder-mcp
- Repository
- github.com/salitaba/maven-decoder-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | maven-decoder-mcp | 1.3.2 | stdio |
| PyPIruntime: uvx | maven-decoder-mcp | 1.3.2 | stdio |
How to connect Maven Decoder
Maven Decoder runs locally from a Node.js package published to the npm registry: maven-decoder-mcp version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y maven-decoder-mcp@1.3.2. It reads these environment variables: MAVEN_REPOSITORY, MAVEN_REMOTE_REPOS, MAVEN_REMOTE_USERNAME, MAVEN_REMOTE_PASSWORD (secret), MAVEN_OFFLINE, MAVEN_AUTO_DOWNLOAD and MAVEN_DECODER_CACHE_DIR; set them in the client's configuration for this server.
Maven Decoder runs locally from a Python package published to PyPI: maven-decoder-mcp version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx maven-decoder-mcp. It reads these environment variables: MAVEN_REPOSITORY, MAVEN_REMOTE_REPOS, MAVEN_REMOTE_USERNAME, MAVEN_REMOTE_PASSWORD (secret), MAVEN_OFFLINE, MAVEN_AUTO_DOWNLOAD and MAVEN_DECODER_CACHE_DIR; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"maven-decoder-mcp": {
"command": "npx",
"args": [
"-y",
"maven-decoder-mcp@1.3.2"
],
"env": {
"MAVEN_REPOSITORY": "<value>",
"MAVEN_REMOTE_REPOS": "<value>",
"MAVEN_REMOTE_USERNAME": "<value>",
"MAVEN_REMOTE_PASSWORD": "<secret>",
"MAVEN_OFFLINE": "<value>",
"MAVEN_AUTO_DOWNLOAD": "<value>",
"MAVEN_DECODER_CACHE_DIR": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| matetools MCP-SERVER35 utility tools for AI agents - mate.tools API. Hash, regex, SEO, random, DNS, SSL, JWT. | Local · stdio |
| MathlasAirtight math for AI agents: 3.68M-doc theorem search + numeric/Lean verification. No LLM, no key. | Local · stdio |
| matih.aiThe grounded data layer for any LLM: governed SQL, metrics, lineage and catalog over your data. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MATLAB MCP ServerConnect AI coding agents to MATLAB. Run code, tests, and analysis via MCP. | Local · stdio |
| MaxAEO AI Visibility MCPLocal-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits. | Local · stdio |
| MaxoperfLoad & browser performance testing - drive MaxoPerf from your AI agent with your API key. | Remote · HTTPLive check: sign-in required |
| MaxStat MCPSearch 408K+ MAX channels and 86M+ posts; metrics, reactions, forwards, webhooks and usage. | Remote · HTTPLive check: sign-in required |
| McacpMCP-to-ACP bridge - let any MCP client drive ACP coding agents. | Local · stdio |