AI integrations

    AI Integrations: How We Connect Claude and Other Models to Your Business Systems

    For operators who want AI working inside Shopify, Klaviyo, HubSpot and the rest of their stack, with a person approving what matters.

    Book a scoping call Take the AI readiness assessment

    How Operator Intelligence connects AI to the systems you run

    An AI model is only as useful as what it can see and do. Operator Intelligence connects models such as Claude to the systems a business already runs, using three building blocks:

    • Native connectors. Vendors including Shopify, Klaviyo and HubSpot publish their own connectors in Claude's directory. They're the fastest start for interactive work: a person asks, Claude reads or drafts, and the vendor's permission model applies.
    • MCP servers. The Model Context Protocol, an open standard Anthropic introduced in November 2024, is how AI applications discover and call tools. We configure official MCP servers first and build custom MCP servers when none does the job safely.
    • n8n workflows. For work that runs on a trigger or schedule, n8n handles the fixed steps and hands judgment calls to an AI step with human approval.

    Most integrations combine two or three. For where MCP ends and an API begins, read MCP vs API.

    Native connector, MCP server or n8n workflow: which route fits

    How to choose, as of October 2026.

    RouteBest forWatch out for
    Native connector in ClaudeInteractive questions, reports and one-off edits by a signed-in userRuns only when someone asks; write access depends on what you approve
    Official MCP serverAgents and multiple AI tools using one vendor's systemGeneric tools that may expose more than the job needs
    Custom MCP serverTask-level tools, your business rules in code, or jobs that span systemsYou own maintenance as vendor APIs change
    n8n workflowTriggered or scheduled work with fixed steps and occasional AI judgmentNeeds an owner for errors, credentials and hosting

    Integration guides

    Each guide covers what you can automate, setup options, permissions and security, and how Operator Intelligence builds it.

    Claude + Shopify

    Shopify's connector for Claude, the Shopify Dev MCP server for Claude Code, and the custom workflow behind ROAM Luggage's days-to-minutes site updates.

    Learn more

    Claude + Klaviyo

    The Klaviyo MCP server and Claude connector, set up read-only first with scoped toolsets and human approval before any send.

    Learn more

    n8n + HubSpot

    n8n's HubSpot node and trigger for lead routing, deal alerts and ticket triage, with Claude steps, rate-limit handling and review gates.

    Learn more

    What every Operator Intelligence integration includes

    The same guardrails apply whatever the route.

    • Read-only access first, with write access added tool by tool
    • The narrowest scopes and roles that do the job
    • Drafts, staging or development themes before anything goes live
    • A named person approving sends, publishes and anything touching money or customers
    • A log of every tool call, reviewed by an owner
    • Credentials held in your company's accounts
    • A runbook, training and regular access reviews

    Frequently asked questions

    Which route should we start with?

    Usually the vendor's native connector, read-only, so your team learns what Claude can do with the data. For a full rollout around those connectors, see Claude for business. Add n8n when a task should run without anyone asking, and a custom MCP server when the official one exposes too much or too little.

    Do you hold partner status with these platforms?

    No. Operator Intelligence is an independent consultancy. We build on each platform's official connectors, MCP servers and APIs and recommend whichever fits the job.

    Is it safe to give AI access to our systems?

    It can be, with least-privilege scopes, separate read and write tools, logging and human approval on risky actions. Vendors now support this: Klaviyo's MCP server has a read-only setting, and Claude admins can restrict each connector's actions.

    What does an integration cost?

    Configuring an official connector takes far less work than a custom MCP server or multi-step workflow. Each integration is scoped as a project after discovery; see how we price.

    Connect AI to your systems without handing it the keys

    Tell us which systems you want AI to work with. We'll recommend a connector, an MCP server, an n8n workflow or a mix.

    Book a scoping call

    Sources

    1. Anthropic (2024): Anthropic introduced the Model Context Protocol, an open standard for secure two-way connections between data sources and AI tools, on November 25, 2024
    2. Anthropic, Claude connector directory (2026): Shopify connector for Claude is made by Shopify and listed in Claude's connector directory (Anthropic verified, added April 2026)
    3. Anthropic, Claude connector directory (2026): Klaviyo connector for Claude is made by Klaviyo and listed in Claude's connector directory (Anthropic verified, added January 2026)
    4. Anthropic, Claude connector directory (2026): HubSpot connector for Claude is made by HubSpot and listed in Claude's connector directory (Anthropic verified, added November 2025)
    5. Klaviyo developer docs, Connect to the MCP server (2026): Klaviyo remote MCP server read-only parameter disables any tools that can perform write actions; toolsets parameter limits tools by API scope
    6. Anthropic (claude.com blog) (2026): Admins can restrict which actions are available within each MCP connector, e.g. allowing read access but disabling write operations (April 9, 2026)
    7. Shopify Help Center, Authorizing AI tool access (2026): Shopify AI tool access can be read-only or include write access; access is limited by staff permissions and can be revoked by uninstalling the integration
    8. n8n docs, MCP Server Trigger (2026): n8n MCP Server Trigger makes n8n tools and workflows available to MCP clients; MCP Client Tool lets n8n agents use tools from external MCP servers
    9. n8n docs, Human-in-the-loop for AI tool calls (2026): n8n can require human approval before an AI Agent runs selected tools; denied actions are canceled

    Related

    Claude + Shopify integration

    Connector, Dev MCP and custom workflows.

    Claude + Klaviyo integration

    The Klaviyo MCP server, set up safely.

    n8n + HubSpot integration

    CRM workflows with AI steps and approvals.

    MCP vs API

    How MCP works with your APIs.

    n8n vs Zapier vs Make

    Which automation platform fits each workflow.