All articlesConnectors And MCP

Add a connector or MCP server

Register tools that agents can use while preserving ownership and scoped access.

Connect tools deliberately

A connector gives agents a route to real systems. Before adding one, know who owns it, which agents need it, what scopes are required, and what failure should look like. Review connector health after the connection is live.

Iron Gorilla connectors page with MCP servers, native integrations, status, and tool counts.
Connectors show each tool surface with owner, health, scope, and registered capabilities.

Adding the connection

Add connectors from the Connectors page by choosing an official provider or custom MCP server. Review the authentication type, tool list, and requested scopes before connecting, especially if an agent will use the tool through LLM Proxy.

Use the owner account or an approved service identity, then assign the connector only to agents that need it. Broad connector access should be treated as production risk, not a convenience.

Need help?

Tell us where you got stuck.

Share what you were trying to do, what happened, and how urgent it is. We will route it to the right team.

Submit a ticket