CRM

Creatio MCP server

Connect Creatio (cloud or on-prem) to Claude, ChatGPT, Cursor, and any MCP-compatible AI agent. Live access to contacts and accounts, identity-resolved with Gmail, Intercom, your tracker, and the rest of your stack — through one unified profile per customer.

Why Pathbound

Creatio is one of your customer’s rooms. Not all of them.

A direct Creatio connector shows your agent Creatio records. Pathbound shows your agent the customer — across Creatio, Gmail, Intercom, your website tracker, Apollo, and Calendly — through one unified profile served over the Model Context Protocol.

Beyond Creatio

Gmail threads, Intercom conversations, page views, Apollo enrichment, Calendly meetings — all stitched onto one timeline per contact. Your agent stops re-asking "who is this?" every time it changes tools.

Identity-resolved

Same person as [email protected] in Creatio, [email protected] in Gmail, "Jane R." in Intercom — Pathbound resolves to one entity. A direct connector only knows its own GUIDs.

Cloud + on-prem

Works with Creatio Cloud and self-hosted instances. You supply your App URL and Identity Service URL during connect; OAuth runs against your own Identity Service, no relay required.

Built for LLMs

Token-efficient response shapes (count_only, fields=summary), server-side aggregation, batch tools. Agents get the answer, not raw OData dumps. Stays inside the context window.

Setup

How do I connect Creatio to Claude?

Register an Integrated app in Creatio admin. Connect once in Pathbound. Drop a snippet into your MCP client.

  1. 01

    Sign up for Pathbound

    Create an account at pathbound.ai. Free during public alpha.

  2. 02

    Register an Integrated app in Creatio

    In Creatio admin: System designer → Integrated apps → New. Note your client_id, client_secret, your App URL (e.g. https://yourcompany.creatio.com), and the Identity Service URL from the system setting "Authorization server Url for OAuth 2.0 integrations". Cloud customers may need Creatio support to retrieve the Identity Service URL.

  3. 03

    Connect Creatio in Pathbound

    Integrations → Creatio → Connect. Enter both URLs, complete the OAuth handshake. Pathbound runs an hourly incremental sync on ModifiedOn and a daily full reconciliation that catches deletes.

  4. 04

    Add Pathbound to your MCP client

    Drop the snippet below into your Claude Desktop config (or in Claude.ai web: Settings → Connected Apps → Add custom MCP → enter https://mcp.pathbound.ai/mcp). The same URL works for ChatGPT, Cursor, Cline, and any MCP client that supports OAuth.

    claude_desktop_config.json
    {
      "mcpServers": {
        "pathbound": {
          "url": "https://mcp.pathbound.ai/mcp"
        }
      }
    }
  5. 05

    Run a test prompt

    Ask the agent: "How many contacts do I have from Creatio?" The agent calls list_contacts via MCP and returns the count.

FAQ

Common questions.

Is this an official Creatio MCP server?

Pathbound is an independent platform. We connect to Creatio via its OAuth 2.0 Identity Service and OData v4 API, and expose your data through one Model Context Protocol server alongside your other sources. Not affiliated with Creatio.

Does it work with on-prem Creatio?

Yes. You supply your own App URL and Identity Service URL during connect, so cloud and self-hosted instances are both supported. Pathbound mints fresh client_credentials tokens against your Identity Service on every sync.

How is this different from Creatio’s OData API?

OData is for backends and scheduled jobs. MCP is for AI agents — it’s the protocol Claude, ChatGPT, and Cursor speak. Pathbound’s MCP also unifies Creatio with Gmail, Intercom, your website tracker, and other sources into one profile per contact, so the agent doesn’t glue multiple APIs together itself.

What does the initial sync pull?

v1 syncs Creatio Contacts and Accounts (companies). Each Contact is resolved to a unified profile by email → phone → external_id, then linked to its Account via the unified Company. Leads, Opportunities, and Activities are on the roadmap.

How does Pathbound handle deletes?

Creatio does not push delete events or surface them via its modified-since filter. Pathbound runs a daily full reconciliation that enumerates every live record ID, tombstones any satellite row no longer in Creatio, and refuses to run the pass if the enumeration is incomplete — so a large tenant past Creatio’s 20k OData cap never gets mass-tombstoned by accident.

Which MCP clients does this work with?

Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue — any client that supports the Model Context Protocol with OAuth.

Is my customer data secure?

Tenant-isolated and OAuth-scoped per user, with encryption at rest via our infrastructure provider’s default configuration. Pathbound does not sell customer data, and we don’t call AI providers on your behalf — your MCP client does, under your account and the AI provider’s terms.

What about HubSpot, Pipedrive, Salesforce, Apollo, Intercom?

Same MCP server, same tools — just connect a different source. See the integrations directory.

Try it on your own data

Within five minutes, your agent is querying real customer context.

Sign up. Drop in the tracker snippet. Connect one CRM. Point your MCP client at mcp.pathbound.ai/mcp.