How to integrate Codacy MCP with Codex

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Codacy logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Codacy MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Codacy with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Codacy MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Codacy MCP server, and what's possible with it?

The Codacy MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Codacy account. It provides structured and secure access to your code quality dashboard, so your agent can perform actions like listing projects, managing API tokens, checking organization repositories, and retrieving user account details on your behalf.

  • Automated project listing and discovery: Instantly fetch a comprehensive list of all projects accessible to your Codacy account for quick overview and navigation.
  • Organization and repository management: Ask your agent to enumerate all organizations you belong to and drill into the repositories associated with each, helping you keep track of where your code lives.
  • API token lifecycle management: Effortlessly create or delete API tokens as needed, making it easy to manage secure integrations and access controls without leaving your flow.
  • User account insights and verification: Retrieve account details to confirm authentication, audit user info, or set up new integrations with confidence.

Supported Tools & Triggers

Tools
Create API TokenCreates a new account API token for the authenticated user.
Delete API TokenTool to delete a specific API token from the authenticated user's account.
Get Account DetailsTool to retrieve details of the authenticated user's account.
Get Configuration StatusTool to retrieve the current configuration status of the Codacy system.
Get HealthTool to check the health status of the Codacy API.
Get Organizations Repositories Settings LanguagesTool to get the list of all languages with their extensions and enabled status for a repository.
Get Tool PatternTool to retrieve the definition of a specific pattern for a given tool.
Get User OrganizationsRetrieves all organizations the authenticated user belongs to for a specific Git provider.
Get VersionTool to retrieve the version of the Codacy installation.
List Analysis Organizations RepositoriesTool to list organization repositories with analysis information for the authenticated user.
List Duplication ToolsTool to retrieve the list of duplication detection tools available in Codacy.
List Languages and ToolsTool to retrieve the list of languages supported by available tools.
List Login IntegrationsTool to list configured login providers on Codacy's platform.
List Metrics ToolsTool to retrieve the list of metrics tools available in Codacy.
List ProjectsTool to list all projects accessible to the authenticated user.
List Provider IntegrationsTool to list provider integrations existing on Codacy's platform.
List ToolsTool to retrieve the list of analysis tools available in Codacy.
List Tools PatternsTool to retrieve the list of patterns for a specific tool.

Conclusion

You've successfully integrated Codacy with Codex using Composio's MCP server. Now you can interact with Codacy directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Codacy operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Codacy operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Codacy MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Codacy MCP?

With a standalone Codacy MCP server, the agents and LLMs can only access a fixed set of Codacy tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Codacy and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Codex?

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Codacy tools.

Can I manage the permissions and scopes for Codacy while using Tool Router?

Yes, absolutely. You can configure which Codacy scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Codacy data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.