· David

SnapLogic SnapCode: integration pipelines written by AI coding agents

SnapLogic launched SnapCode, which lets Claude Code generate SnapLogic pipelines, and an MCP server that lets agents deploy and run them under central governance.

Les på norsk

A week after Celigo, SnapLogic took a similar step. On 14 July, it announced two products that let developers build and run integrations from an AI coding agent instead of from SnapLogic’s own designer. Both have been generally available since 7 July.

What SnapLogic launched

  • SnapCode lets developers describe an integration in natural language inside Claude Code, including the VS Code extension, and get production-ready SnapLogic pipeline code back. The developer owns the code and manages it through ordinary software development workflows. Support for other coding agents is planned.
  • SnapLogic MCP Server gives AI agents governed access to the platform itself, so they can deploy, run and manage integrations through MCP.

SnapLogic stresses that the MCP server is not the same as exposing pipelines as MCP tools, which it launched in May. There, a pipeline becomes a tool an agent can call. Here, the agent works on the platform: it deploys and operates the pipelines.

The generated integrations run on SnapLogic’s platform, with its central security, monitoring and operational controls and more than 1,000 prebuilt connectors to systems such as SAP, Oracle, Salesforce and Workday.

SnapLogic’s CTO, Jeremiah Stone, sums up the argument: builders should not have to choose between the speed of AI coding agents and the governance enterprises require.

Why it matters

AI coding agents are already writing integration code in many companies, often as scripts and small services outside any integration platform. That is fast, but it creates exactly the kind of point-to-point integrations that iPaaS was meant to replace, with no shared monitoring, credentials or connectors.

SnapCode is SnapLogic’s answer: let developers keep their coding agent, but make the result a pipeline on a governed platform. If it works, companies get the speed without the sprawl.

How it compares

Celigo, Boomi and MuleSoft have all released CLI tools, MCP servers for their platforms or agent skills for popular AI assistants this year. The direction is the same everywhere: the integration platform becomes something agents and developers work with from their own tools, not only something people click through.

What differs is how the result is stored. SnapCode generates code that developers manage in their normal repositories and pipelines, which suits teams that already work that way.

What to ask

  1. Where does AI-written integration code live today? Find integrations that coding agents have built outside the platform, and decide whether they should be moved.
  2. Who reviews generated pipelines? Make sure pipelines from SnapCode go through the same review and testing as those built by hand.
  3. What may the MCP server do? Decide which environments agents may deploy to, and whether production deployments need approval from a person.

Sources

This post was written with AI assistance and reviewed by the editor before publishing.

← All posts