The MuleSoft Terraform Provider lets you manage your entire MuleSoft platform — Business Groups, Environments, VPCs, APIs, MCP servers, and AI Agents — as code. Rather than configuring resources manually through the UI, you define them in a single version-controlled file that serves as the source of truth for repeatable, consistent deployments across environments.
If you’re new to the provider, start with the original announcement for a full introduction. This post covers what’s new in the latest release.
What’s New
This release expands Terraform coverage across five areas: Role-Based Access Control and Connected Apps under Access Management, Transit Gateway support for CloudHub 2.0 networking, Exchange Asset Management, Self-Managed Omni Gateway registration, and MCP Bridge. Together they extend IaC coverage, covering everything from platform setup and network connectivity to API publishing and AI agent tooling. It also removes a previous requirement for user credentials on Organization and Environment reads — previously, these reads required an on-behalf-of-user connected app (auth_type = “user”), but a standard connected app with client credentials now works for read operations.
Access Management — Role-Based Access Control and Connected Apps
RBAC resources:
- anypoint_role — create and manage platform-wide roles, including default roles and custom roles for users and connected apps. Requires Organization Administrator access.
- anypoint_role (data source) — retrieve role details by role ID.
- anypoint_roles (data source) — list all roles in an org.
- anypoint_team (updated) — now supports adding permissions and users to teams in addition to existing team management.
- anypoint_teams (data source) — list all teams in an org.
- anypoint_available_permissions (data source) — list available permissions.
- anypoint_users (data source) — list all users in an org.
Connected Apps resources:
- anypoint_connected_app — create connected apps and manage their scopes.
- anypoint_connected_apps (data source) — list all connected apps in an org.
- anypoint_connected_app (data source) — retrieve details for a specific connected app by ID.
- anypoint_available_scopes (data source) — list available connected app scopes in human-readable form.
CloudHub 2.0 — Transit Gateway
The anypoint_transit_gateway_connection resource automates the attachment between a CloudHub 2.0 Private Space and your enterprise AWS network. Connecting a Private Space to a corporate AWS network requires three sequential steps, all of which can now be driven by Terraform:
- MuleSoft side — provision the CloudHub 2.0 Private Space (covered in Phase 1).
- AWS side — use AWS RAM to share your enterprise Transit Gateway with MuleSoft’s internal AWS account ID.
- MuleSoft routes — configure the outbound static routes inside the Private Space so applications know how to route traffic back to your on-premises subnets. This step runs once the TGW attachment state shows as Available.
Resources:
- anypoint_transit_gateway_connection — create a TGW attachment and configure routes.
- anypoint_transit_gateway_connection (data source) — retrieve a TGW connection by gateway ID.
- anypoint_transit_gateway_connections (data source) — list all TGW connections in an org.
- anypoint_private_spaces (data source) — list available private spaces by org ID.
Anypoint Exchange — Asset Management
The anypoint_exchange_asset resource supports creating and versioning assets, adding tags, documentation, terms and conditions, and updating status.
Supported asset types: REST APIs, AsyncAPIs, GraphQL APIs, gRPC APIs, HTTP APIs, LLMs, MCP assets, AI agents, custom assets, policies, and API spec fragments.
Resources:
- anypoint_exchange_asset — create and manage an Exchange asset.
- anypoint_exchange_asset (data source) — retrieve asset details by group ID, asset ID, and version.
- anypoint_exchange_assets (data source) — list all assets in an org.
Deployment Targets — Self-Managed Omni Gateway
Key outcome:
- Automated Gateway Bootstrapping & Registration — eliminates manual token management by programmatically generating registration credentials and bootstrapping self-hosted gateway instances directly into private Kubernetes or VM clusters via code.
Resources:
- anypoint_self_managed_gateway — provision a self-managed gateway and retrieve its registration token.
- anypoint_self_managed_gateway (data source) — retrieve details for a specific gateway by ID.
- anypoint_self_managed_gateways (data source) — list all self-managed gateways in an org.
MCP Bridge
The anypoint_mcp_bridge resource creates an MCP Bridge instance on a managed or self-managed Omni Gateway. MCP Bridge turns existing Exchange APIs into MCP tools without requiring a separate MCP server implementation — you select one or more APIs from Exchange, map their methods to MCP tools, and configure upstream and downstream settings.
Key behaviors:
- By default, three inbound policies are applied automatically: MCP Support, MCP Schema Validation, and MCP Transcoding Router. An MCP Transcoding outbound policy is applied per upstream.
- Additional inbound and outbound policies can be applied using the existing anypoint_api_policy resource, the same as any other API instance.
- TLS context configuration is supported on upstream URLs.
- When the instance is updated, a new version of the corresponding MCP asset is created in Exchange.
- Deleting the instance removes it from API Manager instance and its policies, and deletes the current generated Exchange asset version.
Resources:
- anypoint_mcp_bridge — create and manage an MCP Bridge instance.
Demo
What’s Next
The MuleSoft Terraform Provider is built around a simple goal: every resource you can configure in the platform should be manageable as code. This release moves that closer to reality, but there’s more to come. Upcoming releases will continue to expand coverage across the MuleSoft platform, working toward full lifecycle IaC support from initial provisioning through to governance and retirement. For more practical guidance on bringing infrastructure-as-code to your MuleSoft deployments,
- Get started: Explore the HashiCorp Registry
- Deep dive: Release notes












