Codacy
Pull Codacy code quality, security findings, and coverage signals into agent-driven reviews before you merge or release.
Overview
com.mcparmory/codacy is a MCP server for the Ship phase that analyzes code quality, security issues, and coverage across repositories via Codacy.
What is this MCP server?
- stdio MCP server com.mcparmory/codacy version 1.0.3
- Install via uvx mcparmory-codacy or ghcr.io/mcparmory/codacy:1.0.3
- Analyze code quality issues across connected repositories
- Surface security findings for agent-assisted triage
- Report coverage context to support ship-time review decisions
- Server version 1.0.3
- 2 distribution identifiers: mcparmory-codacy (uvx) and ghcr.io/mcparmory/codacy:1.0.3
- stdio MCP transport per server.schema.json 2025-12-11
Community signal: 25 GitHub stars.
What problem does it solve?
Reviewing quality and security in Codacy separately from your fix loop slows solo shippers who need one place to decide merge readiness.
Who is it for?
Indie teams already on Codacy who want MCP-backed review context in Claude Code or Cursor before release.
Skip if: Repos with no Codacy project setup or builders who only need local ESLint without cloud dashboards.
What do I get? / Deliverables
After install, your agent can incorporate Codacy quality, security, and coverage data into ship-phase review and fixes.
- MCP access to Codacy quality, security, and coverage signals
- Agent-ready repository health context for ship-phase review
- Faster triage without leaving the coding session
Recommended MCP Servers
Journey fit
Codacy fits Ship because quality, security, and coverage gates belong in pre-release review, not only in passive monitoring. Review is the shelf for analyzing repository health and issues across codebases—the core value described in the server manifest.
How it compares
Codacy API MCP bridge, not a replacement for writing custom security pentest skills.
Common Questions / FAQ
Who is com.mcparmory/codacy for?
Solo builders and small teams using Codacy for repo analysis who want agents to read quality, security, and coverage during review.
When should I use com.mcparmory/codacy?
Use it in Ship before merging or releasing when you need Codacy findings summarized and acted on from the IDE.
How do I add com.mcparmory/codacy to my agent?
Register stdio MCP with uvx mcparmory-codacy or ghcr.io/mcparmory/codacy:1.0.3, add Codacy API credentials, and sync repositories in Codacy first.