Codacy

@codacy show me all repositories in our main organization and highlight any with critical code quality issues

Found 12 repositories under your organization. Three have critical issues flagged: `api-gateway` (8 critical security vulnerabilities in dependencies), `payment-service` (4 code complexity hotspots above threshold), and `user-auth` (2 unaddressed SQL injection risks). The remaining 9 repositories are within acceptable quality thresholds. All data reflects the latest commit analysis as of this morning.

This example demonstrates read-heavy discovery across an organization's codebase. Requires an API token with organization-level read permissions. Codacy's analysis is only as current as the last push — if commits haven't been analyzed yet, issues won't appear. Useful for daily standup prep or sprint planning.

@codacy create a new API token for our CI pipeline integration and confirm it has project read access

Created API token `cdy_prod_ci_20250124_a8f3`. Token has read access to all projects under your account. Confirmed scope includes repository listing and quality metrics retrieval, but excludes write operations like ignoring issues or changing quality settings. Store this token securely — it won't be displayed again after this session.

This example shows credential management for automation workflows. The MCP can generate tokens but cannot assign granular scopes beyond account defaults — verify permissions in Codacy's dashboard if your pipeline needs specific access levels. Deleting old tokens before creating new ones prevents token sprawl.

@codacy compare code quality trends across all my projects from the last sprint and draft a summary for the engineering team

Analyzed 8 projects with commits in the past two weeks. Overall quality improved: `checkout-flow` reduced complexity by 15%, `analytics-worker` cleared all security warnings. Two projects regressed: `admin-dashboard` added 3 new code duplication blocks, `mobile-app` introduced 2 medium-severity linting violations. Recommendation: prioritize refactoring in `admin-dashboard` before the next release cycle. Quality gate pass rate across all projects: 75%.

This example pairs Codacy's metrics with AI reasoning to surface trends humans might miss in raw dashboards. The synthesis depends on having multiple projects with recent activity — single-repo accounts will see less comparative insight. Useful for retrospectives or quarterly engineering reviews where you need narrative context around numbers.

When Codacy MCP makes sense for merge-gate enforcement

A 6-person engineering team wants to block PRs that fail coverage or complexity thresholds before they hit main. The Codacy MCP is the wrong tool here—it's designed for account and token management, not for reading quality metrics or triggering CI actions. You'd use this MCP once during onboarding to provision API tokens for your CI runner, then switch to Codacy's webhook or CLI for the actual gate logic. If your workflow is 'set up Codacy access for three new devs and rotate tokens quarterly,' this MCP handles that in two tool calls. If your workflow is 'fail the build when test coverage drops,' you need Codacy's native integrations, not this MCP.

Using Codacy MCP to map developer permissions at scale

A platform team at a 40-person startup needs to audit which engineers have Codacy access across five GitHub organizations and 80 repositories. The Codacy MCP is built for this: authenticate once, call Get User Organizations to enumerate orgs, then call Get Organization Repositories for each org to build a complete access map. The output feeds a spreadsheet or Slack summary showing who can see what. This works cleanly up to about 10 organizations; beyond that, the API's pagination and rate limits make a custom script faster. If you're doing this audit monthly or onboarding contractors who need scoped tokens, the MCP saves 20 minutes of manual clicking. If you're doing it once a year, the Codacy web UI is fine.

When Codacy MCP speeds up token lifecycle management

A DevOps engineer at a SaaS company rotates API tokens every 90 days for compliance and needs to update tokens in four CI environments without losing Codacy integration uptime. The Codacy MCP handles this in a three-step loop: List Projects to confirm current scope, Create API Token to generate the replacement, then Delete API Token to revoke the old one after the new token is deployed. The MCP's value is sequencing these calls in a single chat thread instead of toggling between Codacy's dashboard and your CI config. This matters if you're rotating tokens for more than two services or if the rotation happens quarterly. For annual rotations or single-service setups, the manual flow is faster.