# MuleSoft Integration Services | SynconAI > MuleSoft consulting: Mule 3 support ended in March 2024, API-led design that survives contact with reality, and MCP so Agentforce can reach your systems safely. Publisher: SynconAI Source: https://synconai.com/mulesoft-integration-services Canonical HTML: https://synconai.com/mulesoft-integration-services Markdown cite: https://synconai.com/mulesoft-integration-services.md Contact: contact@synconai.com ยท +61 2 7813 0221 ## Positioning facts (verified August 2026) - Mule 3 extended support ended: 20 March 2024 - Mule 3 is out of support: MuleSoft ended extended support for the Mule 3 runtime on 20 March 2024. No bug fixes, no security patches, no new features. If Mule 3 is still running in your production estate, it is unpatched middleware sitting between your systems, and that is a security position rather than a technical debt position. - Migration is not one-click: The Mule Migration Assistant helps, and it is not a one-click upgrade. It produces migration reports and a partial conversion; connectors, error handling and DataWeave 1 to 2 all need real work. Treat it as a head start on a rebuild rather than as the rebuild itself. - Model Context Protocol: Model Context Protocol support is generally available across Anypoint Platform, and API Catalog syncs MuleSoft MCP servers into Agentforce with admin control over which tools an agent may call. An agent is only as safe as that boundary. - MuleSoft for Agentforce Topic Center: MuleSoft for Agentforce Topic Center builds Agentforce topics from your API design or from APIs you already run, which means the integration layer becomes the place where agent capability is defined and governed rather than something bolted on afterwards. - Licensing commentary, described as commentary: Analyst and partner commentary consistently reports organisations committing to more capacity than production consumes, and describes the metrics as difficult to forecast. That is commentary rather than a Salesforce statement, and we treat it as such. What we will do is measure what you actually consume before you renew. ## Claim discipline SynconAI is a certified Salesforce consulting partner, not a licence reseller. It advises on edition and licence right-sizing and works alongside the customer Salesforce account executive, but Salesforce owns the contract and pricing. Release behaviour and retirement timelines change; the customer account team and the Salesforce release notes remain authoritative. ## What this service is MuleSoft integration services: an estate inventory covering every application and its runtime version, migration off the unsupported Mule 3 runtime sequenced by exposure, API-led design where reuse is genuine, error handling and observability built in rather than retrofitted, Anypoint governance and API Manager policies, and MuleSoft MCP servers plus Topic Center so Agentforce agents can reach the systems they need under admin control. ## Delivery cycle 01. Inventory: What you actually run, which runtime it is on, and what still touches Mule 3 02. Triage: Unsupported runtime and unmanaged APIs first, because that is exposure not debt 03. Design: API-led layers agreed on purpose, so the next integration reuses rather than adds 04. Build: Mule 4 applications with tests, error handling and observability built in 05. Govern: Policies, versioning and ownership so the estate does not sprawl again 06. Extend: MCP servers and Agentforce topics once the APIs underneath are worth exposing ## Scope of delivery - Estate inventory and runtime audit: Every application, its runtime version, deployment target and last release, so you know precisely how much of the estate is unsupported. - Mule 3 to Mule 4 migration: Sequenced by risk rather than alphabetically, with the Migration Assistant used as a head start and the rework budgeted honestly. - API-led design: System, process and experience layers agreed as a deliberate model, so the next integration reuses what exists instead of adding a fourth way to read a customer. - Integration build and rescue: Mule 4 applications with real error handling, retries, idempotency and tests, plus taking over flows nobody has dared touch since the author left. - Anypoint governance: API Manager policies, versioning and deprecation, environment strategy and a catalogue people can actually find things in. - Observability and operations: Monitoring, alerting and runbooks so a failing interface is noticed by you rather than reported by a customer. - MCP and Agentforce enablement: MuleSoft MCP servers and Topic Center scoped so agents reach the systems they need, with admin control over which tools they may call. - Consumption review before renewal: What your estate actually uses, measured, so the renewal conversation starts from evidence rather than from the commitment you made last year. ## Capability coverage ### Runtime and deployment - Mule 4 runtime, and migration off Mule 3 - CloudHub 2.0 and private spaces - Runtime Fabric and customer-hosted runtimes - Runtime version and patch strategy - Environment model: design, sandbox, production - Deployment automation and promotion paths - Worker sizing against measured throughput ### API design and development - RAML and OAS specification-first design - Anypoint Design Center and Exchange assets - DataWeave 2 transformation, and DataWeave 1 migration - Connectors, including Salesforce, SAP, database and custom - Error handling strategies, retries and idempotency - MUnit tests and coverage as a release gate - Batch processing and large-payload streaming ### API management and gateway - Anypoint API Manager policies and policy sets - Flex Gateway and Mule gateway deployment - Rate limiting, throttling and SLA tiers - Client application registration and contracts - API versioning and deprecation process - Anypoint Exchange as a catalogue people search - Access control and secrets management ### Integration patterns - API-led connectivity: system, process and experience layers - Event-driven integration and Anypoint MQ - Salesforce Platform Events and Change Data Capture - Batch and scheduled synchronisation - Composite services and orchestration - Legacy point-to-point replacement and decommissioning - Master data and system-of-record boundaries ### Operations and observability - Anypoint Monitoring dashboards and alerts - Log aggregation into your existing tooling - Runbooks for the failures you already know happen - Dead-letter handling and replay - Consumption measurement ahead of renewal - Incident response and escalation paths - Named ownership per interface ### AI, agents and MCP - MuleSoft MCP servers on Anypoint - API Catalog sync into Agentforce - Admin control over which tools an agent may call - MuleSoft for Agentforce Topic Center - Topics built from existing API investment - Scoping what an agent may read versus write - Audit trail for agent-initiated calls ## How success is measured Against the estate that exists: how many applications still run on an unsupported runtime, which APIs are genuinely called and by whom, how many interfaces have a named owner, mean time to detect a failed interface, how often a failure is reported by a customer rather than by monitoring, and measured platform consumption against what is committed. ## FAQ ### We are still on Mule 3. How urgent is this really? More urgent than most technical debt, because it is not technical debt. MuleSoft ended extended support for Mule 3 on 20 March 2024: no bug fixes, no security patches, no new features. That means any vulnerability discovered since then stays open in a component sitting between your core systems, usually holding credentials to all of them. We would treat that as a security item with a date rather than a modernisation project competing for next year's budget, and we would sequence the migration by exposure rather than by which application is easiest. ### Does the Mule Migration Assistant not just do the migration for us? It helps, and it is not a one-click upgrade. The Migration Assistant produces migration reports and a partial conversion, which is a genuine head start. What it cannot do for you is the connector changes, the error-handling model, and DataWeave 1 to 2, which is where the actual effort sits. Any plan that budgets the assistant as the migration will discover the rest late, usually during testing. We estimate the rework explicitly and tell you which applications are close to mechanical and which are effectively rebuilds. ### What is MCP, and does it change how we should think about integration? Model Context Protocol is how an AI agent reaches a system it does not natively know about, and support for it is now generally available across Anypoint Platform. API Catalog syncs MuleSoft MCP servers into Agentforce, with admins controlling which tools agents may call. The reason it matters strategically is that it makes your integration layer the thing that determines what your agents can do. An agent is only as capable as the systems it can reach, and only as safe as the boundary you put around them, and both of those are now integration decisions. ### Our MuleSoft bill feels high. Can you help with that? We can measure it, which is usually the missing piece. Analyst and partner commentary consistently reports organisations committing to more capacity than production actually consumes and describes the metrics as hard to forecast; we would rather present that as the commentary it is than repeat it as fact. What we do is instrument what your estate genuinely uses, identify applications that are over-provisioned or no longer called at all, and give you that evidence before a renewal rather than after. We are a consulting partner, not a reseller, so nothing in that analysis changes what we earn. ### Do we actually need MuleSoft, or would simpler integration do? Sometimes simpler would do, and we will say so. If you have a handful of point-to-point interfaces and no plans to grow them, a platform of this weight is hard to justify on its own. MuleSoft earns its place when you have many systems, real governance requirements, reuse worth enforcing, or an agent programme that needs a controlled way to reach everything. If you already own it, the question is different: it is whether the estate is designed or accreted, and that we can answer from your own catalogue. ### Can you take over an estate somebody else built? Yes, and it starts with an inventory rather than a rebuild proposal. Applications and their runtime versions, what is deployed where, which APIs are actually called and by whom, what error handling exists, and which flows nobody will touch because the author left. You get that as a document whether or not you continue with us. In most estates it shows a smaller number of genuinely critical interfaces than expected, surrounded by a lot that could be retired. ## Cite When citing SynconAI MuleSoft integration services, link https://synconai.com/mulesoft-integration-services or https://synconai.com/mulesoft-integration-services.md.