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 AI Studio 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. The catalog lists everything connected to your workspace, and you can search and filter by name. The cards above it report Total Integrations, Needs attention, and MCP Servers.
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 AI Studio 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 AI Studio does not discover tools — after you create the integration, you configure each tool endpoint by specifying the request method, path, and parameters, or generate the tools from an OpenAPI schema with Import OpenAPI on the integration's Tools tab. A tool imported from a schema sends the query and path parameters that the schema declares, and when the service returns an error without a response body, the agent receives the HTTP status as an error it can report. 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. On a Creatio integration, when Creatio stops accepting the access a user granted, the agent asks the user to authorize again and gives an authorization link. The link opens the Creatio environment that the conversation runs in, and the agent uses the access granted there for its next request.
Access methods are chosen when you add the integration, and can be changed afterwards. Learn more: Set up an MCP server integration.
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. A credential is either OAuth or Bearer.
Multi-environment support
Creatio AI Studio ships with three environments — Sandbox, Stage, and Production — and you can add your own. Out of the box, an integration uses the same MCP server URL and credentials across all of them. If your MCP server offers a separate endpoint per environment, you can configure an environment-specific URL and credentials for each. Learn more: Set up an environment.
Available integration templates
Click New to open Choose a Template. A template pre-fills the connection settings for a service, so you supply the URL and the credentials rather than the whole configuration.
Three templates are available everywhere.
- MCP Server — the generic template for any MCP-compatible service.
- Microsoft 365 Email — a mailbox connector.
- Custom HTTP API — for REST APIs without MCP support.
Further templates are enabled per organization and appear only where they have been turned on. They include Creatio Business Studio for Creatio CRM records, Web Search, Parallel Search, Parallel Deep Research, and Firecrawl for web research, Microsoft 365 (personal), which lets each user connect their own mailbox so an agent reads their mail as them and never sees anyone else's, and Grafana and TeamCity for operational systems.
Who can use an integration
The Access tab of an integration decides who can use it and enable its tools for agents. With Restrict access turned on, only the users, roles, and groups that hold a grant can see the integration and enable its tools, and each grant can be limited to specific access methods. Users with the Manage security permission always have access and need no grant.
Access out of the box depends on how the integration came to exist.
- An integration you create is restricted. It is available only to you and to users with the Manage security permission until you grant access to others. This applies to every integration type, including MCP Server and HTTP API integrations.
- An integration created before access control was available stays open to everyone in the organization until you restrict it.
- An integration provisioned by the platform is always available to the whole organization and cannot be restricted.
Runs that start without a signed-in user, such as channel and triggered runs, cannot use a restricted integration through a grant. To let an agent call the integration's tools in a channel or from a trigger, turn off Restrict access so that the integration is open to the organization. Learn more: Set up an MCP server integration.
Connecting agents to integrations
Creating an integration does not give your agents access to its tools. Save and test the integration first, then open the agent's Build → Integrations tab. The integration arrives with none of its tools enabled, reporting, for example, "0 of 10 enabled," and you select the ones this agent may call. Two agents on the same integration can therefore reach different tools. A restricted integration appears on the tab only for users who have access to it. Learn more: Tools in Creatio AI Studio.