Integrations
AI agents need access to external data and services to act on your behalf. Integrations provide that access by connecting Creatio AI Studio to third-party systems. Creatio AI Studio supports two protocols: MCP Server and HTTP API. With MCP Server, Creatio discovers available tools from the server. With HTTP API, you define each tool endpoint yourself.
Integration catalog
All configured integrations live in the Integrations section under Connectivity in the left navigation menu. The catalog lists everything connected to your workspace. You can search and filter by name. Summary cards at the top show the total count, how many need attention due to credential or connectivity issues, and how many use the MCP Server type.
Any integration flagged in Needs Attention has a configuration error, expired credentials, or a failed connectivity test. Agents that rely on it may not work until you fix the issue.
Integration types
The integration type determines how tools become available to your agents.
MCP Server integrations connect to any service that exposes a Model Context Protocol endpoint. Once the connection is established, Creatio discovers all tools the server offers — you do not need to define them one by one. Use this type for MCP-compatible services or any third-party tool with MCP support.
HTTP API integrations connect to standard REST APIs. Creatio does not discover tools — after you create the integration, you configure each tool endpoint by specifying the request method, path, and parameters. Use this type when the external service does not support MCP.
MCP access modes
For MCP Server integrations, you choose which access modes are available to agent creators. Each agent uses exactly one access mode — the agent creator selects it when configuring the agent.
Integration credentials — the MCP server uses the credentials configured for the integration. All agents whose creators select this mode use the same credentials and appear identical to the server. Use this mode for tools where caller identity does not affect permissions.
Agent owned credentials — each agent has its own credentials for the MCP server. The server can identify which agent is calling and apply agent-specific permissions. For Creatio-hosted MCP servers, credentials can be generated automatically from within AI Studio.
Delegated access — the end user authenticates directly with the MCP server at the start of a session. All tool calls made during that session run on behalf of that user. The MCP server applies the user's own role-based access controls. This mode is per session: each user who talks to the agent authenticates independently.
Authentication
When creating an MCP Server integration, you choose whether the server requires authentication. Public or internally trusted servers can be connected with just a URL. For servers that require authentication, you select existing credentials from your workspace or create new ones. Credentials can use OAuth 2.0, bearer token, or API key authentication.
Multi-environment support
Creatio AI Studio has three environments: sandbox, stage, and production. Out of the box, an integration uses the same MCP server URL and credentials across all environments. If your MCP server follows the same pattern — separate endpoints for sandbox, stage, and production — you can configure environment-specific URLs and credentials for each.
Available integration templates
Creatio AI Studio provides integration templates that pre-fill the connection settings for common services. Available out of the box is a template for connecting to a Creatio CRM-based MCP server. For any other MCP-compatible service, use the Custom MCP Server template. For REST APIs without MCP support, use Custom HTTP API.
Connecting agents to integrations
Creating an integration does not give your agents access to its tools. Save and test the integration first, then assign it to an agent in that agent's configuration. Once assigned, the agent can use all tools the integration exposes.