Qodo Documentation
HomepageBlogCommunityGet Started
  • Overview
  • Qodo Gen
  • Qodo Portal
  • On Prem
  • Introduction
  • Quickstart
  • Setup and Installation
    • VSCode Installation
    • JetBrains Installation
    • Sign In
    • Extension Settings
    • Uninstall
  • Qodo Gen Chat
    • Agentic Mode
      • Agentic Tools (MCPs)
      • Built-in Tools (MCPs)
    • Standard Mode
      • Focus
        • Current File Focus
        • Git Diff Focus
      • Context
        • Add Entire Folder or Project as Context
        • Add Image as Context
      • Commands
        • /ask
        • /changelog
        • /commit
        • /describe
        • /docstring
        • /enhance
        • /explain
        • /find-on-github
        • /generate-best-practices
        • /help
        • /improve
        • /issues
        • /recap
        • /review
    • Inline Context
    • Chat History
    • Model Selection
    • Chat Preferences
  • Qodo Gen CLI
    • Setup and Quickstart
    • Creating and Managing Agents
    • CI and Automation
    • List of CLI Commands and Flags
    • Use Cases and Examples
  • Company Codebase (RAG)
    • Tagging
    • Configuration File
  • Code Completion
  • Test Generation
    • Configuring Your Test Setup
  • Data Sharing
  • Release Notes
Powered by GitBook
LogoLogo

Terms and Privacy

  • Terms of Use
  • Privacy Policy
  • Data Processing

© 2025 Qodo. All Rights Reserved.

On this page
  • What is MCP?
  • Requirements
  • Agentic Tools Configuration
  • 1. Local MCPs
  • 2. Remote (SSE) MCPs
  • Create a new Agentic Tool
  • Remove or Manage Tools
  • Manage sub-tools
  • Troubleshooting
  • Agentic Tools Allow List
  • Activation Flow
  • Developer Behavior

Was this helpful?

  1. Qodo Gen Chat
  2. Agentic Mode

Agentic Tools (MCPs)

PreviousAgentic ModeNextBuilt-in Tools (MCPs)

Last updated 3 days ago

Was this helpful?

Agentic Tools (MCPs) allow you to integrate external tools and services into Qodo Gen. This enables Qodo Gen to access and use custom tools when needed.

What is MCP?

MCP stands for Model Context Protocol. It’s an open protocol that standardizes how applications provide context to AI Models. You can learn more about MCPs in Anthropic's MCP documentation.

Using the MCP protocol, Qodo Gen can interact with external services.

For example, if a Jira MCP is set up, you could ask "Find me a Jira ticket about creating an authentication protocol" in the chat, and get relevant information from your Jira project.


Requirements

You will need Node.js installed in order to run tools properly.

To verify you have Node installed, open the command line on your computer.

  • On macOS, open the Terminal from your Applications folder

  • On Windows, press Windows + R, type “cmd”, and press Enter

Once in the command line, verify you have Node installed by entering in the following command:

node --version

If you get an error saying “command not found” or “node is not recognized”, download Node from nodejs.org.

Learn more on why Node.js is required in Anthropic's official MCP documentation.


Agentic Tools Configuration

Note: If you're an Enterprise user, you may be unable to add new Agentic Tools if your system administrator has restricted additions in the Agentic Tools Allow List.

In order to create a tool and add it to Qodo Gen, you need the applicable MCP server configuration.

Qodo Gen supports two types of MCPs:

  1. Local MCPs These run directly in your environment and don’t require network calls. Ideal for internal tools or logic that doesn’t rely on external APIs.

  2. Remote MCPs (SSE MCPs) These are hosted externally and communicate via HTTP. When setting up a Remote MCP, you'll provide a URL, and optionally, you can add custom HTTP headers (e.g., for authentication).

1. Local MCPs

The configuration for a local MCP is usually in JSON form. For example, the GitHub MCP server configuration is:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-github"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

You can find many MCP tools and setup options in the MCP GitHub.

2. Remote (SSE) MCPs

We recommend using SSE MCPs, especially in Enterprise environments. They are easier to manage, more secure and ideal for external services like Jira. Also, if you're setting up an Allow List in your Enterprise environment, we recommend enabling SSE-based MCPs for a smoother and more secure user experience.

The SSE MCPs configuration relies on a URL.

To configure this type of tool, add the following as to the Agentic Tools configuration text box:

{
    "semgrep": {
        "url": "https://mcp.semgrep.ai/sse"
    }
}

Create a new Agentic Tool

Once you've got your required MCP configuration, you can create a new Agentic Tool for Qodo Gen's Agent to use:

  1. Open Qodo Gen in Agentic Mode Learn more about Agentic Mode and what it does.

  2. Go to the Tools Management page

    Either click on Connect more tools or on the tools link under the chatbox.

  1. Create a New Tool Click Add new MCP button at the top left of the tools management page.

  1. Enter Tool Configuration Details Paste a JSON configuration script to configure your new tool. Learn more about tools configuration.

  1. Save and Test Save your configuration.

  • A green dot will indicate a successful connection.

    • A list of sub-tools will appear under the tool, indicating all the services this tool is capable of. You can toggle all sub-tools on or off.

    • Clicking on Auto approve will let you set if the use of the sub-tool will be automatically approved for every use in-chat.

    • You can turn sub-tools on or off by pressing the toggle button.

  • A yellow dot indicates a problem with your connection. Try checking your configuration and API keys and make sure you've set them all correctly.

  1. Modify or Delete: You can edit or remove a tool as needed. Some of the built-in tools, like Code Navigation, cannot be edited.

Remove or Manage Tools

You can scroll through all connected tools in Qodo Gen's Agentic Mode welcome page.

Click Connect more tools to get to the tools management page.

You can enable, disable, or modify the configuration of tools at any time. Click the pen and note symbol next to a custom tool's toggle button to modify a tool's configuration.

Toggling a tool off will disable Qodo Gen from using it.

See the number of available tools any time at the bottom of Qodo Gen Chat, under the chatbox. Clicking on it displays a list of available tools.

Manage sub-tools

Click the small arrow next to a tool's name to open a list of sub-tools, indicating all the services this tool is capable of.

You can toggle all sub-tools on or off, and set whether your approval is needed for their use.

Troubleshooting

A yellow dot near the tool's name indicates a problem with your connection.

Try checking your configuration and API keys and make sure you've set them all correctly. Also, ensure your internet connection is stable.


Agentic Tools Allow List

This feature is only available for Enterprise users.

The Agentic Tools Allow List feature enables enterprise organizations to enforce stricter governance over Agentic Tools usage in Qodo Gen.

When enabled, this mode restricts developers to using only a predefined set of tools defined at the organization level.

This feature is ideal for organizations requiring tight control over configuration parameters to comply with internal policies, reduce misconfigurations, and standardize environments across teams.

Activation Flow

  1. Request Enablement An organization admin submits a request to Qodo Support to enable Agentic Tools Allow List mode.

  2. Allow List Configuration The Qodo DevOps team configures the organization's MCP allow list manually.

Developer Behavior

Once MCP Allow List mode is active:

  • ✅ View Access: Developers can view the organization-defined tools list upon their next login to Qodo Gen.

  • ✅ Overrides Allowed: Developers may override values for existing environment variables listed in the allow list.

  • ❌ No Custom Agentic Tools: Developers cannot add new or custom tools outside the allow list.