> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your own MCP servers to DinoAI agents

> Connect external MCP servers such as Looker in Settings, and DinoAI agents can call their tools, with control per server, per environment, and per agent.

*September 28, 2026*

DinoAI agents can now call tools from MCP servers outside Paradime. Connect a server once in **Settings** > **Integrations**, under **MCP Servers**, and its tools become available to your agents next to the built-in ones.

* **Public or OAuth 2.1 servers.** Add the server's URL and choose **Public (no auth)** or **OAuth 2.1**. For a server that doesn't support dynamic client registration, such as Looker, enter the **Client ID** you registered for Paradime.
* **Choose which tools agents get.** Each server's page lists its tools with a toggle for each. An Agent environment can turn off a server or single tools, and each agent can allow or deny specific tools in the builder or with `mcpTools` in its YAML.
* **Named by server.** MCP tools appear as `mcp__<server>__<tool>`, so `mcp__looker__*` covers every tool from a server named Looker.

MCP tools are available to agent runs, and not yet to the copilot in the Code IDE. See [Connect external MCP servers](/products/dino-ai/programmable-agents/external-mcp-servers). Shipped in Paradime v6.15.0.


## Related topics

- [Changelog](/changelog/overview.md)
- [Connect external MCP servers](/products/dino-ai/programmable-agents/external-mcp-servers.md)
- [Paradime MCP server: connect AI clients to your data](/products/dino-ai/mcp-server/index.md)
- [Connect any MCP client to the Paradime MCP server](/products/dino-ai/mcp-server/other-clients.md)
- [Connect Claude Code to the Paradime MCP server](/products/dino-ai/mcp-server/claude-code.md)