
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
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.
- 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.
- 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: You can find many MCP tools and setup options in the MCP GitHub.2. Remote (SSE) MCPs
SSE (Server-Sent Events) MCPs are recommended for Enterprise environments. They are easier to manage, more secure, and ideal for external services like Jira. If you’re setting up an Allow List in your Enterprise environment, enable SSE-based MCPs for a smoother 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:Create a new Agentic Tool
Once you’ve got your required MCP configuration, you can create a new Agentic Tool for Qodo’s Agent to use:Enter Tool Configuration Details Paste a JSON configuration script to configure your new tool. Learn more about tools configuration.

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.
- Click Auto approve to automatically approve every in-chat use of that sub-tool.
- 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.

Remove or manage tools
You can scroll through all connected tools in the tools management page.




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. When enabled, this mode restricts developers to using only a predefined set of tools defined at the organization level. This feature is ideal if you need tight control over tool configuration to comply with internal policies, reduce misconfigurations, and standardize environments.Activation flow
- Request Enablement An organization admin submits a request to Qodo Support to enable Agentic Tools Allow List mode.
- 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.
- 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.



