Skip to main content
mcpSource-backedReview first Safety Privacy
Codacy MCP Server logo

Codacy MCP Server

The official Codacy MCP server (@codacy/codacy-mcp) that gives AI assistants access to the Codacy API for code quality, security, and coverage — listing repository and pull-request issues, retrieving file coverage and duplication, searching security (SRM) findings, inspecting analysis tools and patterns, and running local analysis with the Codacy CLI.

by codacy · submitted by davion-knight·added 2026-07-08·
HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/codacy/codacy-mcp-server/blob/master/README.md, https://github.com/codacy/codacy-mcp-server, https://www.codacy.com/
Brand
Codacy MCP Server
Brand domain
codacy.com
Brand asset source
brandfetch
Safety notes
The `codacy_cli_analyze` tool runs Codacy CLI analysis locally on files or directories, and if the CLI is not installed the server will attempt to download and install it, so it can execute and install software on your machine., The Codacy Account API Token grants API access to the organizations and repositories your account can see, including private ones, so treat it as a secret and scope it to least privilege., Most tools are read-only analysis (issues, coverage, duplication, security findings), but `codacy_setup_repository` adds or follows a repository in Codacy, which is an account-write action., Security (SRM) tools surface real vulnerabilities and findings for your code, so handle that output carefully and avoid leaking it., Prefer a token scoped to the intended organization and a non-sensitive repository when an agent acts autonomously.
Privacy notes
The server calls the Codacy API with your token; repository metadata, code-quality issues, coverage, duplication, security findings, and pull-request data it returns are passed to the LLM/MCP client., Some tools return source-derived content — for example `codacy_get_pull_request_git_diff` returns a PR's Git diff and file-analysis tools return issue context — which can include real source code., Security findings can reveal sensitive vulnerability details about your codebase; review before sharing that output., The account token is provided via the `CODACY_ACCOUNT_TOKEN` environment variable in your MCP client config — keep that config out of version control and restrict access to it.
Author
codacy
Submitted by
davion-knight
Claim status
unclaimed
Last verified
2026-07-08

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Safety notes

  • The `codacy_cli_analyze` tool runs Codacy CLI analysis locally on files or directories, and if the CLI is not installed the server will attempt to download and install it, so it can execute and install software on your machine.
  • The Codacy Account API Token grants API access to the organizations and repositories your account can see, including private ones, so treat it as a secret and scope it to least privilege.
  • Most tools are read-only analysis (issues, coverage, duplication, security findings), but `codacy_setup_repository` adds or follows a repository in Codacy, which is an account-write action.
  • Security (SRM) tools surface real vulnerabilities and findings for your code, so handle that output carefully and avoid leaking it.
  • Prefer a token scoped to the intended organization and a non-sensitive repository when an agent acts autonomously.

Privacy notes

  • The server calls the Codacy API with your token; repository metadata, code-quality issues, coverage, duplication, security findings, and pull-request data it returns are passed to the LLM/MCP client.
  • Some tools return source-derived content — for example `codacy_get_pull_request_git_diff` returns a PR's Git diff and file-analysis tools return issue context — which can include real source code.
  • Security findings can reveal sensitive vulnerability details about your codebase; review before sharing that output.
  • The account token is provided via the `CODACY_ACCOUNT_TOKEN` environment variable in your MCP client config — keep that config out of version control and restrict access to it.

Prerequisites

  • Node.js and npm, with the `npx` command working (the server runs via `npx -y @codacy/codacy-mcp`)
  • A Codacy account and an Account API Token from Codacy Account access management
  • For local analysis, the Codacy CLI v2 (macOS/Linux/Windows via WSL); the server installs it if it is missing
  • An MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.)

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "codacy": {
      "command": "npx",
      "args": ["-y", "@codacy/codacy-mcp"],
      "env": {
        "CODACY_ACCOUNT_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

About this resource

Content

The Codacy MCP Server is the official Model Context Protocol server maintained by Codacy. It exposes the Codacy API to LLMs and agentic clients for code quality, security, and coverage — listing repository and pull-request issues, retrieving file coverage and duplication, searching security (SRM) findings, inspecting analysis tools and patterns, and running local analysis with the Codacy CLI.

It ships as the npm package @codacy/codacy-mcp (v0.6.22, MIT), runs over stdio via npx, and authenticates with a Codacy Account API Token (CODACY_ACCOUNT_TOKEN). For local analysis it uses the Codacy CLI v2, installing it automatically if it is not already present. Setup details live in the repository README.

Source Review

The following real repository and package sources were fetched and reviewed for this entry:

  • README.md — the npx install command, the CODACY_ACCOUNT_TOKEN env var and client config blocks, the Codacy CLI requirement for local analysis, and the full tool catalog (repository, quality, security, coverage, pull-request, and pattern tools).
  • npm: @codacy/codacy-mcp — package name and version (0.6.22), MIT license, and the codacy-mcp-server bin entry.
  • LICENSE — MIT License (Codacy).

Repository facts confirmed at review time: official codacy organization, repository codacy/codacy-mcp-server, default branch master, not archived, actively maintained, and released as @codacy/codacy-mcp v0.6.22 on npm.

Features

  • Repository & organizationcodacy_setup_repository, codacy_list_organizations, codacy_list_organization_repositories, and codacy_get_repository_with_analysis (Grade, Issues, Duplication, Complexity, Coverage).
  • Code-quality issuescodacy_list_repository_issues and codacy_get_issue investigate best-practice, performance, complexity, and style issues.
  • File analysiscodacy_list_files, codacy_get_file_issues, codacy_get_file_coverage, codacy_get_file_clones, and codacy_get_file_with_analysis.
  • Security (SRM)codacy_search_organization_srm_items and codacy_search_repository_srm_items list security findings across SAST, DAST, SCA, secrets, and IaC.
  • Pull requests — list PRs and PR issues, and get PR file coverage and the Git diff (codacy_get_pull_request_files_coverage, codacy_get_pull_request_git_diff).
  • Tools & patternscodacy_list_tools, codacy_list_repository_tools, codacy_get_pattern, and codacy_list_repository_tool_patterns.
  • Local CLI analysiscodacy_cli_analyze runs Codacy CLI analysis on files or directories locally.
  • Account-token auth — authenticates with a single Codacy Account API Token over HTTPS.
  • One-command install — runs via npx -y @codacy/codacy-mcp with no clone or build step.

Installation

Run the published package with npx, providing your Codacy Account API Token:

export CODACY_ACCOUNT_TOKEN="your_codacy_account_token"
npx -y @codacy/codacy-mcp

Add it to an MCP client (e.g. Cursor / Claude Desktop):

{
  "mcpServers": {
    "codacy": {
      "command": "npx",
      "args": ["-y", "@codacy/codacy-mcp"],
      "env": {
        "CODACY_ACCOUNT_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Create an Account API Token in Codacy Account → Access management. For local analysis the server uses the Codacy CLI v2 and installs it automatically if it is not present. Supported IDEs (VS Code, Cursor, Windsurf) can also add the server from the Codacy extension.

Use Cases

  • Code-quality triage — ask an agent to list and explain a repository's or file's quality issues.
  • Security review — surface SAST/DAST/SCA/secrets/IaC findings from Codacy's security dashboard.
  • Coverage inspection — check file and pull-request coverage, including diff coverage on a PR.
  • Duplication analysis — find duplicated code segments (clones) in a file.
  • Local analysis — run Codacy CLI analysis on files or directories during development.

Safety and Privacy

  • Runs and installs software locally. codacy_cli_analyze runs Codacy CLI analysis on your files and will download/install the CLI if it is missing.
  • Token is broad. The Account API Token can read the organizations and repositories your account sees (including private ones); scope it tightly and treat it as a secret.
  • Mostly read, one write. Most tools are read-only analysis, but codacy_setup_repository adds or follows a repository in Codacy.
  • Source and findings flow to the model. PR Git diffs, file analysis, and security findings are returned to the LLM/MCP client and can include real source code and vulnerability details.
  • Credential hygiene. CODACY_ACCOUNT_TOKEN lives in your MCP client config — keep it out of version control and restrict access.

Duplicate Check

No existing entry in the directory matches this server. A search of all directory entries for "codacy" across slugs, titles, repository URLs, and install commands returned no results, and there is no prior entry pointing at github.com/codacy/codacy-mcp-server or the npm package @codacy/codacy-mcp. This is therefore a net-new, non-duplicate entry.

Source citations

Add this badge to your README

Show that Codacy MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/codacy-mcp-server.svg)](https://heyclau.de/entry/mcp/codacy-mcp-server)

How it compares

Codacy MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

The official Codacy MCP server (@codacy/codacy-mcp) that gives AI assistants access to the Codacy API for code quality, security, and coverage — listing repository and pull-request issues, retrieving file coverage and duplication, searching security (SRM) findings, inspecting analysis tools and patterns, and running local analysis with the Codacy CLI.

Open dossier

The official Infisical MCP server (@infisical/mcp) that lets AI assistants work with Infisical's secrets-management API through function calling — reading, creating, updating, and deleting secrets, and managing projects, environments, folders, and project members — authenticating with a Machine Identity (universal auth) or an access token against Infisical Cloud or a self-hosted instance.

Open dossier

The official Mux MCP server (@mux/mcp) that gives AI agents access to the Mux API for video and analytics. It uses a "Code Mode" scheme — exposing a documentation-search tool and a code tool that runs agent-written TypeScript against the Mux SDK in an isolated sandbox — to work with Mux Video (assets, live streams, playback IDs, uploads) and Mux Data (viewer metrics and monitoring).

Open dossier

The official Convex MCP server, built into the Convex CLI, that lets AI agents introspect and query a Convex deployment — listing tables, paginating data, running deployed functions and read-only one-off queries, reading logs and function specs, and managing environment variables — with production deployments blocked by default as a safety measure.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitterdavion-knightdavion-knightdavion-knightdavion-knight
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandCodacy MCP Server logoCodacy MCP ServerInfisical MCP Server logoInfisical MCP ServerMux MCP Server logoMux MCP ServerConvex MCP Server logoConvex MCP Server
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorcodacyInfisicalmuxincget-convex
Added2026-07-082026-07-082026-07-082026-07-08
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesThe `codacy_cli_analyze` tool runs Codacy CLI analysis locally on files or directories, and if the CLI is not installed the server will attempt to download and install it, so it can execute and install software on your machine. The Codacy Account API Token grants API access to the organizations and repositories your account can see, including private ones, so treat it as a secret and scope it to least privilege. Most tools are read-only analysis (issues, coverage, duplication, security findings), but `codacy_setup_repository` adds or follows a repository in Codacy, which is an account-write action. Security (SRM) tools surface real vulnerabilities and findings for your code, so handle that output carefully and avoid leaking it. Prefer a token scoped to the intended organization and a non-sensitive repository when an agent acts autonomously.The server can read, create, update, and delete secrets (`get-secret`, `list-secrets`, `create-secret`, `update-secret`, `delete-secret`) in the projects and environments its identity can access, so deletions and edits affect real secrets. It can also create projects, environments, and folders and invite members to a project (`create-project`, `create-environment`, `create-folder`, `invite-members-to-project`), which change structure and access. Access is bounded by the Machine Identity or access token, not by tool naming; scope that identity to the minimum projects, environments, and permissions needed. Because this manages secrets, prefer a least-privilege identity and a non-production project when an agent acts autonomously. The universal-auth client secret or `INFISICAL_TOKEN` grants access to your secrets and must itself be treated as a secret.This server uses a Code Mode scheme — the agent writes TypeScript against the Mux SDK and the server runs it in an isolated sandbox that has no web or filesystem access, then returns what the code prints or returns. The sandboxed code runs with your Mux access token, so it can create, modify, and delete real Mux resources (assets, live streams, playback IDs, uploads) within that token's permissions. Access is bounded by the Mux token's permissions, not by tool naming — scope the token to least privilege and prefer a non-production environment when an agent acts autonomously. Optional Mux signing and private keys enable signed playback URLs and JWTs; treat `MUX_SIGNING_KEY` and `MUX_PRIVATE_KEY` as secrets. Launching the client with the remote HTTP transport opens a network listener, so secure and authenticate it before exposing it beyond localhost.Production deployments are blocked by default; accessing them requires the explicit `--dangerously-enable-production-deployments` flag, which then allows reading and modifying live production data. The `run` tool executes deployed Convex functions (including mutations) and the env tools (`envSet`, `envRemove`) change deployment configuration, so these can modify a deployment. The `runOneoffQuery` tool runs sandboxed JavaScript that is read-only and cannot modify data, but `data`/`tables` can read arbitrary documents from the deployment. Per the docs, setting `--project-dir` does not stop an agent from passing a custom `projectDir` in the status tool or acting on deployments of other projects; restrict access accordingly. Use `--disable-tools` (e.g. `data,run,envSet`) to narrow what the server can do, and keep it pointed at a development deployment when an agent acts autonomously.
Privacy notesThe server calls the Codacy API with your token; repository metadata, code-quality issues, coverage, duplication, security findings, and pull-request data it returns are passed to the LLM/MCP client. Some tools return source-derived content — for example `codacy_get_pull_request_git_diff` returns a PR's Git diff and file-analysis tools return issue context — which can include real source code. Security findings can reveal sensitive vulnerability details about your codebase; review before sharing that output. The account token is provided via the `CODACY_ACCOUNT_TOKEN` environment variable in your MCP client config — keep that config out of version control and restrict access to it.The `get-secret` and `list-secrets` tools return secret values to the LLM/MCP client, so plaintext secrets can be exposed to the model and its provider — a significant consideration for a secrets manager. Avoid pointing the server at production secrets; use a scoped, non-sensitive project for agent workflows where possible. The identity credentials (client ID/secret or access token) live in your MCP client config env block — keep that config out of version control and restrict access to it. When self-hosting, `INFISICAL_HOST_URL` targets your own instance, and requests plus credentials are sent there.The server calls the Mux API with your credentials; asset metadata, live-stream details, and Mux Data results it returns are passed to the LLM/MCP client. Mux Data covers viewer and playback analytics (video views, errors, quality-of-experience metrics), which can include viewer and session information. Credentials (`MUX_TOKEN_ID`, `MUX_TOKEN_SECRET`, and any signing/webhook secrets) are provided via environment variables in your MCP client config — keep that config out of version control and restrict access to it. Video assets and analytics can reference real customer-facing content and usage, so avoid exposing a production account's data to the model unnecessarily.The server connects to your Convex deployment using your local CLI credentials; table listings, documents, logs, and function specs it returns are passed to the LLM/MCP client. Document data can include sensitive or PII fields stored in your tables, and log output can contain request data. Environment-variable tools (`envGet`, `envList`) can read deployment configuration, which may include secrets; treat that output as sensitive. The server reads your local Convex project directory to resolve deployments; keep credentials and any custom `--env-file` out of version control.
Prerequisites
  • Node.js and npm, with the `npx` command working (the server runs via `npx -y @codacy/codacy-mcp`)
  • A Codacy account and an Account API Token from Codacy Account access management
  • For local analysis, the Codacy CLI v2 (macOS/Linux/Windows via WSL); the server installs it if it is missing
  • An MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.)
  • Node.js and npm (the server runs via `npx -y @infisical/mcp`)
  • An Infisical account on Infisical Cloud or a self-hosted instance
  • Credentials — a Machine Identity universal-auth client ID and secret, or an access token (`INFISICAL_TOKEN`)
  • Optionally `INFISICAL_HOST_URL` for a self-hosted or dedicated instance (defaults to `https://app.infisical.com`)
  • Node.js and npm (the server runs via `npx -y @mux/mcp@latest`)
  • A Mux account and an access token (token ID and secret) from the Mux dashboard
  • Optional Mux signing/private keys or webhook secret if you use signed playback or webhook features
  • An MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.)
  • Node.js and npm (the server runs via `npx -y convex@latest mcp start`)
  • A Convex project and account; the CLI uses your existing Convex login for deployment access
  • A Convex deployment to target (the dev deployment is used by default; production is opt-in)
  • An MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.)
Install
npx -y @codacy/codacy-mcp
npx -y @infisical/mcp
npx -y @mux/mcp@latest
npx -y convex@latest mcp start
Config
{
  "mcpServers": {
    "codacy": {
      "command": "npx",
      "args": ["-y", "@codacy/codacy-mcp"],
      "env": {
        "CODACY_ACCOUNT_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
{
  "mcpServers": {
    "infisical": {
      "command": "npx",
      "args": ["-y", "@infisical/mcp"],
      "env": {
        "INFISICAL_HOST_URL": "https://app.infisical.com",
        "INFISICAL_AUTH_METHOD": "access-token",
        "INFISICAL_TOKEN": "your_access_token"
      }
    }
  }
}
{
  "mcpServers": {
    "mux": {
      "command": "npx",
      "args": ["-y", "@mux/mcp"],
      "env": {
        "MUX_TOKEN_ID": "your_token_id",
        "MUX_TOKEN_SECRET": "your_token_secret"
      }
    }
  }
}
{
  "mcpServers": {
    "convex": {
      "command": "npx",
      "args": ["-y", "convex@latest", "mcp", "start"]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.