Skip to main content
DinoAI agents and the DinoAI copilot in the Code IDE can call tools from MCP servers outside Paradime, next to their built-in tools. Connect a server once for your workspace, then choose which of its tools DinoAI can use.
The copilot in the Code IDE gets MCP tools too. See MCP tools in the Code IDE copilot for which tools it gets and when they ask for approval.

​
Before you start

  • Access to Settings > Integrations in your workspace.
  • The server’s URL. Paradime connects over MCP’s Streamable HTTP transport, to https:// addresses on the public internet only.
  • For an OAuth server that supports neither dynamic client registration nor client ID metadata documents, such as Looker, a client ID registered for Paradime on that server. See Register Paradime with the server first.

​
Add a server

1

Open MCP Servers

Go to Settings > Integrations. Under the DinoAI agent integrations, find MCP Servers and select Add MCP Server.
2

Enter the server details

Enter the Server URL, and optionally a Display name (for example GitHub, Linear, or Sentry). The display name also names the server’s tools: see Tool names.Under Authentication, choose:
  • Public (no auth) for a server that needs no credentials.
  • OAuth 2.1 for a server that asks you to sign in. Leave Client ID (optional) empty to register Paradime automatically, or enter the client ID registered for Paradime on that server. Servers that identify clients from a client ID metadata document, such as Loops, need no client ID either.
3

Connect

Select Connect for a public server, or Connect & Authorize for an OAuth server and approve access in the window that opens. The dialog shows each stage, from validating the URL to discovering the server’s tools.
The server shows as Connected under MCP Servers, and its page lists the tools it offers. If the dialog says the server doesn’t support dynamic client registration, register Paradime with it first and enter the client ID. If a Public (no auth) server turns out to need sign-in, the dialog shows the error and nothing is saved, so you can add it again with OAuth 2.1.

​
Register Paradime with the server first

Some OAuth servers, such as Looker, only accept clients registered in advance. On the server, register an OAuth client for Paradime with this redirect URI, using the address you open Paradime at:
For example, https://app.paradime.io/mcp-client/callback. Then enter the client ID it gives you in Client ID (optional) when you add the server. For Looker, see Google’s Looker MCP server documentation for registering the client and choosing which tools to expose.

​
Choose which tools agents can use

Three layers decide which of a server’s tools an agent gets. Each one can only narrow the one before it: To restrict one agent, pick its MCP tools in the builder’s Allowed tools or Denied tools list, under Tools, next to its other tools. Each connected server has its own group there: the first option, such as All Looker tools, covers every tool on the server, and the options after it pick single tools. In YAML, list them under tools as mcp__<server>__<tool>, or mcp__<server>__* for every tool from one server:
An allowlist refuses any tool it doesn’t name, MCP tools included.
Agents used to limit MCP tools with a separate mcpTools block. It’s deprecated, but an agent that still has one stays limited by it, on top of tools. The builder shows a notice under Tools with a Remove button. Add the MCP tools the agent needs to its Tools lists before you remove the block, because removing it can give the agent MCP tools the block refused.

​
MCP tools in the Code IDE copilot

In Agent mode, the DinoAI copilot in the Code IDE gets the enabled tools of every connected MCP server in your workspace, narrowed by your workspace’s default Agent environment. An agent’s Tools lists don’t apply to it. Each MCP call shows in the chat panel as a card named after the server and tool, such as looker: get_models. Your approval mode decides when an MCP tool runs: Manual always asks, Auto sends the call to the reviewer, and Full auto runs it without asking. The copilot can use at most 128 tools in a message, its own tools included. When your MCP servers take it past that, DinoAI keeps its own tools, leaves out the MCP tools that don’t fit, and shows a notice in the chat saying how many it left out. To stay under the limit, turn off tools you don’t need under Settings > Integrations > MCP Servers. If your MCP tools can’t be loaded, or the model provider rejects them, the copilot answers without them for that message and shows a notice saying so. A single tool that can’t be loaded is skipped, and the others stay available.

​
Tool names

An MCP tool’s name is mcp__<server>__<tool>. The server part is the server’s display name in lowercase, with anything other than letters and digits replaced by _: a server named “My GitHub” gives mcp__my_github__<tool>. To match every tool from one server, use mcp__<server>__*. Names you list for an agent are at most 64 characters: a longer server part is cut to 40 characters, and a longer tool part is cut to fit what’s left. The builder’s options already use the shortened names.

​
Keep a connection working

Paradime refreshes a server’s OAuth tokens before each agent run. If access is revoked on the server’s side, the connection shows an error and its tools are left out of agent runs until you reconnect it. A server that isn’t connected shows Connect or Reconnect on its card. Select it to open the server’s page, which shows the status (Authorization not completed or Needs reconnecting) and the error, with two actions:
  • Reconnect removes the server and adds it again with the same URL, name, and authentication, then opens the authorization window. This resets the server’s tool settings in your Agent environments.
  • Remove deletes the server.
If you added the server with your own client ID, such as for Looker, don’t use Reconnect: remove the server and add it again with that client ID.

​
Next steps

Creating agents in the app

Build an agent and choose its tools in the builder.

YAML configuration

Every key in an agent’s YAML, including tools.