How to Use the Codacy MCP in CrewAI

Q: Can a CrewAI manager agent restrict access to Codacy tools?

Yes. By using MCPServerHTTP with a toolfilter, you can limit which agents can run tools like listrepositorywebhooks while allowing others to search for issues.

Deploy a team of autonomous CrewAI agents to monitor Codacy repository quality and coordinate issue resolution.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Codacy MCP to CrewAI

Create your Vinkius account to connect Codacy to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Codacy with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-agent quality auditing with CrewAI

Let a specialized crew manage your technical debt. You can assign one agent to fetch repository grades using `get_repository_quality_analysis` while a second agent analyzes the results and drafts a remediation plan using this MCP server. This collaborative approach means you don't rely on a single prompt to do everything. By using specialized roles, your CrewAI team can systematically audit your entire portfolio of projects.

Autonomous issue triage and developer assignment

Build an autonomous operations desk that monitors code health. Your lead agent can search for fresh bugs with `search_repository_issues` and pass them to a coordinator agent. The coordinator agent then calls `list_organization_members` to match the open issues with the developers who own the code. The entire process runs in the background without requiring a human to manually assign tickets.

Declarative MCP Server integration for crews

Connecting your agents to your code metrics takes only a single line of configuration. By passing the Vinkius URL directly to the mcps parameter in your CrewAI agent definition, your crew instantly gains access to the full suite of analysis tools. For complex setups, you can use MCPServerHTTP with a tool_filter. This lets you restrict access, ensuring your research agents can only call `list_supported_languages` while keeping administrative tools locked down.

Setup guide

Set up Codacy MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Codacy tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Codacy Analyst",
    goal="Access and analyze Codacy data via MCP.",
    backstory="Expert analyst with direct Codacy access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Codacy transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Codacy Analyst",
        goal="Access and analyze Codacy data via MCP.",
        backstory="Expert analyst with direct Codacy access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Codacy transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Codacy. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Codacy now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Codacy MCP in CrewAI

You define multiple agents with distinct tasks. One agent uses `get_repository_quality_analysis` to find failing projects, and another agent drafts the cleanup tasks based on the issues found.

You can pass the connection URL directly to the mcps array when defining your agents. For more control over which tools are exposed, use MCPServerHTTP from the crewai.mcp library.

Yes. By using MCPServerHTTP with a tool_filter, you can limit which agents can run tools like `list_repository_webhooks` while allowing others to search for issues.

CrewAI supports stdio, SSE, and Streamable HTTP transports. When hosted on Vinkius, your crew connects securely over a high-performance SSE connection.

The tools only read repository grades, static analysis findings, and organization membership lists. Your raw source code remains untouched on your Git provider, and all data transfers are protected by Vinkius's ephemeral sandboxing.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript