Codacy MCP server

Read from the package source without running it. The installed server may list more.

• add_billing_card

  Adds a payment card to the specified organization's billing profile using a Stripe token. The token must be obtained from the Stripe /v1/tokens API prior to calling this endpoint.

• add_codacy_badgewrite action

  Creates a pull request that adds the Codacy static analysis badge to the repository's README. Only applies to public GitHub repositories that do not already have the badge; the pull request is created asynchronously and may fail after a successful response.

• add_organization_members

  Adds people to an organization on the specified Git provider, assigning them as members or committers based on whether they have a pending join request.

• apply_organization_provider_settings

  Applies the organization's default provider settings to all repositories within the specified Git provider organization. Use this to propagate updated integration settings uniformly across all repositories at once.

• bulk_ignore_repository_issues

  Ignores a batch of issues in a specified repository, suppressing them from analysis results. Accepts up to 50 issue IDs per request, with an optional reason and comment for audit purposes.

• bulk_update_repository_tool_patternswrite action

  Bulk enables or disables code patterns for a specific tool in a repository. Use optional filters to target a subset of patterns by language, category, severity, tags, or search term; omit all filters to apply the change to every pattern for the tool.

• bypass_pull_request_analysis

  Bypasses the analysis status check for a specific pull request, allowing it to proceed regardless of analysis results. Useful when overriding blocking analysis gates in CI/CD workflows.

• change_organization_billing_plan

  Changes the billing plan for a specified organization on a Git provider. Available plan codes can be retrieved using the list_payment_plans operation.

• check_organization_leave_eligibility

  Checks whether the authenticated user is eligible to leave the specified organization, returning either confirmation or the specific reasons preventing them from leaving.

• configure_branch_analysis

  Enable or disable Codacy analysis for a specific repository branch. Use this to control which branches are actively analyzed within a given organization and repository.

• configure_provider_settingswrite action

  Creates or updates Git provider integration settings for an organization, controlling which Codacy features are active such as status checks, pull request annotations, AI-powered reviews, and coverage summaries.

• configure_repository_language_settingswrite action

  Updates the language response settings for a specific repository, controlling which programming languages are recognized and analyzed. Use this to tailor language detection behavior for a given repository within an organization.

• configure_repository_tool

  Enable or disable an analysis tool and its patterns for a specific repository. Changes are applied immediately without checking whether the repository is linked to a coding standard.

• create_post_commit_hookwrite action

  Creates a post-commit hook integration for a repository, enabling Codacy to receive commit notifications and trigger analysis automatically after each push.

• delete_integrationwrite action

  Permanently removes the connected Git provider integration for the authenticated user. Once deleted, the user will need to re-authenticate to restore access for that provider.

• delete_organizationwrite action

  Permanently removes an organization from Codacy by deleting its association with the specified Git provider. This action cannot be undone and will remove all related configuration and data within Codacy.

• delete_repositorywrite action

  Permanently removes the specified repository from the organization on the given Git provider. This action cannot be undone and will remove all associated data from Codacy.

• estimate_organization_billing

  Retrieves a billing cost estimation for an organization based on a specified payment plan and optional promotional code. Useful for previewing pricing before committing to a plan.

• export_organization_people_csv

  Generates and returns a CSV file listing all people in the specified organization, including their name, email, last login date, and last analysis date.

• follow_repository

  Follow a repository that has already been added to Codacy, enabling tracking of its analysis and quality metrics for the authenticated user.

• get_authenticated_user

  Retrieves the profile and account details of the currently authenticated user. Useful for confirming identity, accessing user metadata, or personalizing responses based on the active session.

• get_build_server_analysis_setting

  Retrieves the current status of the 'Run analysis on your build server' setting for a specific repository. Use this to check whether build server analysis is enabled or disabled.

• get_commit_analysis

  Retrieves the analysis results for a specific commit in a repository, including code quality metrics and issue findings. Useful for inspecting the impact of a particular commit on overall code health.

• get_commit_delta_statistics

  Retrieves quality metric deltas introduced by a specific commit, showing how the commit changed code quality indicators. Returns zero or null values for metrics if Codacy has not yet analyzed the commit.

• get_git_provider_app_permissions

  Retrieves the current status of Codacy's Git provider app permissions for a specified organization, indicating which permissions have been granted or are missing.

• get_organization

  Retrieves details for a specific organization from a Git provider. Returns organization metadata such as name, settings, and associated information.

• get_organization_billing

  Retrieves detailed billing information for a specific organization on a Git provider, including subscription and usage details.

• get_organization_billing_card

  Retrieves the payment card details associated with an organization's billing account on a specified Git provider. Useful for reviewing current billing payment method information.

• get_organization_by_installation_id

  Retrieves an organization associated with a specific provider installation ID. Currently supports GitHub ('gh') as the git provider.

• get_organization_for_user

  Retrieves details for a specific organization associated with the authenticated user on a given Git provider. Useful for confirming organization membership and accessing organization-level metadata.

• get_organization_onboarding_progress

  Retrieves the current onboarding progress for a specific organization on a Git provider. Useful for tracking setup completion status during the organization integration workflow.

• get_provider_settings

  Retrieves Git provider integration settings for a specific organization, including configuration details for the connected provider account.

• get_pull_request

  Retrieves detailed analysis data for a specific pull request in a repository. No authentication is required when accessing public repositories.

• get_pull_request_coverage

  Retrieves code coverage information for a specific pull request in a repository. No authentication is required when accessing public repositories.

• get_repository

  Retrieves detailed information about a specific repository within an organization on a given Git provider. Authentication is not required when accessing public repositories.

• get_repository_analysis

  Retrieves detailed analysis information for a specific repository on Codacy, including code quality metrics and insights for the authenticated user. Optionally scoped to a specific enabled branch, defaulting to the repository's main branch.

• get_repository_analysis_progress

  Retrieves the analysis progress overview for a specific repository on Codacy, indicating how far along the initial analysis has advanced. No authentication is required when accessing public repositories.

• get_repository_commit_quality_settings

  Retrieves the quality gate settings applied to commits for a specific repository. Note that diff coverage threshold is not included, as it is not currently supported for commit-level quality checks.

• get_repository_issue

  Retrieves detailed information about a specific open issue in a repository. Requires identifying the Git provider, organization, repository, and issue ID.

• get_repository_issues_overview

  Retrieves a summary of issues found by Codacy in a specific repository, including issue counts and breakdowns as shown on the Issues page. Supports filtering via request body parameters.

• get_repository_provider_integration_settings

  Retrieves the Git provider integration settings for a specific repository, including configuration details that control how Codacy interacts with the provider for that repository.

• get_repository_ssh_key

  Retrieves the most recently generated public SSH key associated with a repository, which may be either a user or repository-level SSH key. Useful for verifying or displaying the active SSH key configured for repository access.

• get_repository_tool_pattern_config

  Retrieves the pattern configuration for a specific tool pattern applied to a repository. Returns the organization-level standard configuration if one is applied, otherwise falls back to the repository-level settings.

• get_tool_patterns_overview

  Retrieves an overview of code patterns for a specific analysis tool in a repository, showing counts and summaries by category, severity, and status. Uses standard settings if applied, otherwise falls back to repository-level tool configuration.

• ignore_issue_false_positive

  Marks a false positive result on a specific issue as ignored, suppressing it from future analysis reports. Use this to dismiss incorrectly flagged issues within a repository.

• list_branch_required_checks

  Retrieves the required status checks configured for a specific branch in a repository. These checks must pass before pull requests can be merged into the branch.

• list_commit_analysis_logs

  Retrieves the analysis log entries for a specific commit in a repository, providing details about the analysis process and any issues encountered during execution.

• list_commit_clones

  Retrieves duplicate code blocks (clones) detected in a specific commit for a repository. Use the status parameter to filter results by new, fixed, or all duplicate occurrences.

• list_commit_delta_issues

  Retrieves issues introduced or fixed by a specific commit, calculated as a delta between the source commit and its parent (or an optional target commit). Use this to audit code quality changes at the commit level.

• list_commit_files

  Retrieves the list of files changed in a specific commit along with their static analysis and coverage results. Supports filtering, searching, sorting, and pagination to narrow down results.

• list_commit_statistics

  Retrieves daily commit analysis statistics for a repository over the last N days that have available analysis data. Note that returned days reflect days with actual data, which may not align with the last N consecutive calendar days.

• list_emails

  Retrieves all email addresses associated with the authenticated user's account, including primary and secondary addresses along with their verification and visibility status.

• list_ignored_issues

  Retrieves a paginated list of issues that Codacy detected but were manually marked as ignored in the specified repository. Supports filtering via request body parameters.

• list_integrations

  Retrieves all integrations connected to the authenticated user's account. Returns a paginated list of integration records up to the specified limit.

• list_organization_people

  Retrieves a list of people associated with a specific organization on a Git provider, including Codacy users and optionally commit authors who are not Codacy users.

• list_organization_people_suggestions

  Retrieves suggested people (users) to add to an organization on a specified Git provider. Useful for discovering potential members based on activity or association with the organization.

• list_organization_pull_requests

  Retrieves pull requests across all repositories in an organization that the authenticated user has access to. Results can be sorted by last updated date (default), impact, or merged status.

• list_organization_repositories

  Retrieves repositories belonging to a specific organization on a Git provider for the authenticated user. Supports filtering by sync status, language, and segment, with cursor-based pagination (Bitbucket cursors must be URL-encoded before use in subsequent requests).

• list_organization_repositories_with_analysis

  Retrieves repositories belonging to a specified organization on a Git provider, including their analysis metadata. Supports filtering by name or segment, with pagination cursor that must be URL-encoded for Bitbucket.

• list_organizations

  Retrieves all organizations that the currently authenticated user belongs to. Returns a paginated list up to the specified limit.

• list_organizations_by_provider

  Retrieves all organizations associated with the authenticated user for a specified Git provider. Useful for discovering available organizations before performing organization-scoped operations.

• list_pull_request_clones

  Retrieves duplicate code blocks (clones) detected in a specific pull request for a repository. Use the status filter to narrow results to new, fixed, or all duplicate occurrences.

• list_pull_request_commits

  Retrieves analysis results for all commits within a specified pull request, including code quality and issue data per commit. Results are paginated and scoped to a repository on a supported Git provider.

• list_pull_request_coverage_reports

  Retrieves all coverage reports uploaded for both the common ancestor commit and the head commit of a pull request branch. Useful for comparing coverage changes introduced by the pull request.

• list_pull_request_file_coverage

  Retrieves per-file code coverage information for a specific pull request in a repository. No authentication is required when accessing public repositories.

• list_pull_request_files

  Retrieves the list of files changed in a pull request along with their static analysis results. Supports sorting by filename, coverage delta, or total coverage.

• list_pull_request_issues

  Retrieves the list of issues found in a specific pull request for a given repository. Use the status filter to narrow results to new, fixed, or all issues, and optionally surface only potential issues.

• list_pull_request_logs

  Retrieves analysis logs for a specific pull request in a repository, useful for diagnosing issues or reviewing the details of a Codacy analysis run.

• list_pull_requests

  Retrieves a list of pull requests for a specified repository, supporting sorting by last-updated, impact, or merged status. No authentication is required for public repositories.

• list_repository_branches

  Retrieves a paginated list of branches for a specified repository, with optional filtering by enabled status or search term. No authentication is required when accessing public repositories.

• list_repository_category_overviews

  Retrieves analysis category overviews (e.g., code quality, security, complexity) for a specific repository, summarizing issue counts and grades per category. Authentication is not required for public repositories.

• list_repository_commits

  Retrieves Codacy analysis results for commits in a specified branch of a repository. Defaults to the main branch if no branch is specified.

• list_repository_languages

  Retrieves all programming languages detected in a repository, including their associated file extensions and whether each language is enabled for analysis.

• list_repository_people_suggestions

  Retrieves suggested people (collaborators or contributors) for a specific repository within an organization. Useful for discovering relevant users to add or assign within a given repository context.

• list_repository_tool_patterns

  Retrieves the code pattern configurations for a specific analysis tool applied to a repository. Returns standard organization-level settings if applied, otherwise falls back to repository-specific settings.

• list_repository_tools

  Retrieves the analysis tool settings configured for a specific repository, including which tools are enabled and their configurations. No authentication is required when accessing public repositories.

• list_tool_conflicts

  Retrieves a list of analysis tools that have configuration conflicts in the specified repository. Useful for diagnosing tool setup issues that may affect code analysis results.

• list_tool_pattern_conflicts

  Retrieves a list of patterns for a specific tool that conflict with the repository's configured Coding Standards, helping identify rule inconsistencies that may affect code analysis.

• reanalyze_commit

  Triggers a reanalysis of a specific commit in a repository. Optionally clears the cache before running the analysis to ensure fresh results.

• reanalyze_pull_request_coverage

  Triggers a reanalysis of the latest coverage report uploaded for a specific pull request. Useful when coverage data needs to be reprocessed without uploading a new report.

• refresh_repository_provider_integration

  Refreshes the Git provider integration for a specific repository on GitLab or Bitbucket, using the authenticated user's credentials to enable commenting on new pull requests.

• regenerate_repository_ssh_key

  Regenerates the SSH key Codacy uses to clone a specific repository, automatically updating the new public key on the Git provider.

• regenerate_repository_ssh_user_key

  Regenerates the user SSH key Codacy uses to clone the specified repository, automatically adding the new public key to the user's account on the Git provider. Using a user SSH key is recommended when the repository includes submodules.

• remove_organization_memberswrite action

  Removes one or more members from a Git provider organization by their email addresses. Useful for revoking access when offboarding users or managing organization membership.

• remove_user_emailwrite action

  Removes a specified email address from the authenticated user's account. The primary email and the last remaining email address cannot be removed.

• reset_repository_commit_quality_settings

  Resets the commit quality settings for a specific repository to Codacy's default values, discarding any custom configurations previously applied.

• reset_repository_quality_settings

  Resets all quality settings for a specific repository back to Codacy's default values, discarding any custom configurations that were previously applied.

• search_organization_repositories

  Search repositories within an organization on a specified Git provider, returning results enriched with analysis information. Supports filtering by repository name and paginated results.

• search_repository_issues

  Searches and returns issues found by Codacy in a specific repository, equivalent to the Issues page view. Supports filtering via request body to narrow results by category, severity, or other criteria.

• set_default_branch

  Sets the default branch for a specified repository on Codacy. The target branch must already be enabled on Codacy before it can be designated as the default.

• set_default_emailwrite action

  Designates a specified email address as the primary default for the authenticated user, automatically removing the default status from any previously designated email. Only one email address can hold default status at a time.

• set_issue_ignored_state

  Ignore or unignore a specific code analysis issue in a repository, optionally providing a predefined reason and comment to justify the action.

• set_organization_join_modewrite action

  Updates the membership join mode for an organization on a specified Git provider, controlling how new members are admitted (automatically, admin-approved automatically, or by request).

• sync_repository

  Synchronizes a repository's name and visibility settings in Codacy with the current state from the upstream Git provider. Useful after renaming or changing the visibility of a repository directly on the provider.

• trigger_pull_request_ai_review

  Triggers an AI-powered code review for a specific pull request in a repository. Initiates automated analysis and feedback generation for the pull request's changes.

• unfollow_repository

  Stops following a repository in the specified organization on a Git provider, removing it from the list of monitored repositories.

• update_current_userwrite action

  Updates profile settings for the currently authenticated user. Only the fields provided will be modified.

• update_organization_billingwrite action

  Updates the billing information for a specified organization on a given Git provider. Use this to modify billing details associated with the organization's Codacy account.

• update_repository_integration_settingswrite action

  Updates the Git provider integration settings for a specific repository, controlling which Codacy features are active such as status checks, pull request comments, AI reviews, and coverage summaries.

• update_repository_quality_settingswrite action

  Updates the quality gate thresholds for a specific repository, defining the criteria under which the repository is considered healthy or unhealthy across issues, duplication, coverage, and complexity metrics.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 64% of 915 Security servers

Tools

100

the typical Security server has 6

Tools that change things

16%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 95% of 587 Security servers

Codacy: common questions

Is Codacy MCP server safe?

Mostly: it is graded B (80/100). Read the Codacy safety report

How do I install Codacy?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Codacy need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Codacy maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.3.

What can I use instead of Codacy?

Servers from other publishers that do the same job: SonarQube MCP Server, Skylos MCP server and Snyk MCP server.

How does Codacy compare with other Security MCP servers?

safety score 80/100 (higher than 64% of 915 Security servers); tools 100 (the typical Security server has 6); tools that change things 16% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.