- Home
- Resources
- Integrations
- MuleSoft
Claude MuleSoft connectorWhat Claude can do in your MuleSoft account.
The Claude MuleSoft connector exposes 66 tools: 52 read, 9 write, 5 undocumented. Below: what Claude can look up across your Anypoint landscape, what it can apply, provision or delete, the connected app you need first, and the tools no source describes.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your integration team
Answering a simple question about your API estate usually means switching between Exchange, API Manager, Monitoring and governance reports. With the connector, a platform lead asks Claude in plain English: it searches the catalogue, reads the governance and traffic data behind each service, and can apply a policy or deploy a server once you agree. The consoles stay the source of truth; Claude becomes a faster way in.
Find what already exists before building it. A product team asks whether a payments API is already published. search_assets_semantic searches the portfolio by meaning, not keywords, and view_api_version_details shows the instances and lifecycle of the match.
Spot the service that hurts. Error rates rose overnight. fetch_monitoring_overview gives the org-wide snapshot, then fetch_monitoring_drill_down ranks which services or instances drive the errors or the latency.
Tighten governance without a ticket queue. Asked to add rate limiting on one API, Claude loads the options with prepare_policy_creation, shows the form through get_policy_template_form, then apply_policy_to_instance puts it in place. MuleSoft's own example says the policy applies immediately.
What the directory sheet leaves out: nothing connects until someone creates a connected app in Anypoint Platform, and many tools need an extra Anypoint permission on top. Five tools on the sheet are absent from MuleSoft's current reference. No source says whether Claude prompts before the nine write tools. And nothing runs by itself: Claude acts while you talk to it. For CloudHub actions inside scheduled scenarios instead, the MuleSoft Make integration covers that use.
The vocabulary in one minute
Five words you will meet while connecting MuleSoft.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and revocable.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Connect MuleSoft to Claude in three steps
- 01
Find MuleSoft in the list
In Claude's settings, open Customize, then Connectors, and look for MuleSoft. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first before each member can sign in.
- 02
Start the connection
Click Connect on its row. MuleSoft's guide adds one step here: enter the Client ID and Client Secret of your Anypoint connected app, then sign in to Anypoint in the window that opens. If the link breaks, use Disconnect.
- 03
Read the authorization screen
Read Anypoint's authorization screen before you approve. It belongs to the service, not to Claude, and it sets what the access covers. From then on, Claude works through the connected app, which acts on your behalf.
The 66 MuleSoft tools, grouped by what they do
MuleSoft gives Claude 66 tools: 52 that read your account, 9 that change something in it, and 5 no official source describes.
Three groups: what Claude reads, what it applies, deploys or deletes, and five names that MuleSoft's current reference does not describe. Names stay the ones Claude displays, in English.
- 52 read
- 9 write
- 5 not documented
Tools index
- check_policy_conformance
- fetch_automated_policy_template
- fetch_cost_instance_timeseries
- fetch_cost_instances
- fetch_cost_optimization_recommendations
- fetch_cost_overview
- fetch_governance_service_report
- fetch_governance_services
- fetch_monitoring_drill_down
- fetch_monitoring_instance
- fetch_monitoring_overview
- fetch_service_facets
- fetch_services
- get_business_group
- get_mcp_server_state
- get_omni_gateway_target_domains
- get_omni_gateway_usage_report
- get_policy_template_form
- get_provision_status
- get_trusted_mcp_catalog
- list_agents
- list_apis
- list_business_groups
- list_governance_strategies
- list_llms
- list_mcp_servers
- list_omni_gateway_environments
- list_omni_gateway_targets
- list_provider_gateways
- list_scanner_providers
- prepare_automated_policy_creation
- prepare_policy_creation
- search_assets_semantic
- search_global_content
- search_portfolio_services
- search_repository_knowledge
- select_active_business_group
- select_active_environment
- select_active_provider
- select_api_version
- show_observability_performance
- test_scanner_connection
- view_agent_details
- view_api_instance_details
- view_api_instance_monitoring
- view_api_instance_policies
- view_api_version_details
- view_api_version_governance_report
- view_api_version_instances
- view_governance_report
- view_llm_details
- view_mcp_server_details
What Claude reads (52)
52 toolsFifty-two tools that browse, search and report on your landscape without touching any resource.
check_policy_conformance
Converts a selected policy payload into a structured linked-data format and prints it in the server's logs.
fetch_automated_policy_template
Fetches one policy template by its identifier, with the configuration details needed to fill it in.
fetch_cost_instance_timeseries
Returns token usage and response time over time for a single instance, and MuleSoft notes it is the only tool that gives an agent's timeline.
fetch_cost_instances
Lists token usage and optimization coverage instance by instance, across tool servers and agents, including which cost policies are not yet applied.
fetch_cost_optimization_recommendations
Ranks the instances with the highest projected token savings from cost policies that have not been applied yet.
fetch_cost_overview
Gives the org-wide cost summary: token totals, tokens saved by optimisation policies and tool call counts, plus agent spend in dollars when cost data exists.
fetch_governance_service_report
Returns detailed governance conformance data for a single service, rule by rule.
fetch_governance_services
Searches, filters and counts governance conformance across all your services at once, for the big picture rather than one API.
fetch_monitoring_drill_down
Ranks services or instances by their share of one metric: availability, reliability, average latency, request volume, error rate or policy violations.
fetch_monitoring_instance
Pulls monitoring data for one API instance: charts for requests, error rate, latency and violations, plus its busiest endpoints and clients.
fetch_monitoring_overview
Shows an org-wide health snapshot: total requests, error rate, average latency, availability, reliability and compact trend charts.
fetch_service_facets
Computes aggregate counts and buckets, by type or provider for instance, when a summary is needed rather than full service rows.
fetch_services
Returns concrete service entries with identifiers and names, the tool Claude uses when it needs real rows to pick from or open.
get_business_group
Gets the full metadata of one business group from its identifier.
get_mcp_server_state
Reads the deployed state of a catalog-managed tool server: its current systems, tools and upstream identifiers, the input that any later adjustment depends on.
get_omni_gateway_target_domains
Gets the ingress domains and application identifier of one managed gateway target.
get_omni_gateway_usage_report
Reports how much of your managed gateway size entitlement is currently in use.
get_policy_template_form
Loads one policy template's details, including its configuration schema, so the matching form can be shown right after you pick a policy.
get_provision_status
Polls the progress of a provisioning job, or of a job that adjusts a tool server.
get_trusted_mcp_catalog
Returns the catalogue of SaaS systems available for tool server provisioning, each with its tools, authentication type, credential fields and upstream settings.
list_agents
Lists the agents registered for your organization and presents a browsable view with filters for picking one.
list_apis
Lists the APIs in your organization's catalogue with an interactive view for browsing, filtering and selecting them.
list_business_groups
Lists the business groups available to you, optionally filtered by name.
list_governance_strategies
Lists the governance strategies of your organization in a searchable, filterable table styled like the main web app.
list_llms
Lists the language models registered for your organization, with a view to browse, filter and select them.
list_mcp_servers
Lists the tool servers registered for your organization, the ones that give AI agents access to systems, with a browsable view.
list_omni_gateway_environments
Lists the Anypoint environments available for managed gateway setup, so the right one can be chosen first.
list_omni_gateway_targets
Lists the deployment targets available for managed gateways in one environment.
list_provider_gateways
Lists gateways for the active provider; with MuleSoft as provider, that means your Flex Gateways.
list_scanner_providers
Gets the list of providers a scanner can connect to, such as Google Vertex or Microsoft Copilot.
prepare_automated_policy_creation
Opens the wizard for a new automated-policy strategy, with the scope options and policy templates to choose from.
prepare_policy_creation
Loads the policy options available for one API instance, the starting point for adding protection to it.
search_assets_semantic
Searches portfolio assets by meaning, for concepts or use cases rather than exact words, and returns names, descriptions, relevance scores and types.
search_global_content
Searches content across agents, tool servers and APIs of your platform in one go, a tool MuleSoft designed for embedded agents.
search_portfolio_services
Discovers assets from the capabilities and use cases they cover, a way to explore the portfolio by need.
search_repository_knowledge
Answers conceptual questions from a curated, fixed corpus of policy, governance and security documents and rulesets, with cited snippets.
select_active_business_group
Shows the current business group context and, when given an identifier, sets a new active group for the tools that follow. No source says it touches any Anypoint resource.
select_active_environment
Browses the Anypoint environments of the active provider and sets one as the working context for later calls.
select_active_provider
Browses the available providers and sets one as the active context for the provider tools that come next.
select_api_version
Shows an interactive selector of versions for one API and lets the host know which version you pick.
show_observability_performance
Loads observability dashboard data so it can be displayed as an embedded view inside the conversation.
test_scanner_connection
Tests the connection to a scanner provider before the scanner itself is set up, so a wrong credential shows up early.
view_agent_details
Shows one agent's details in read-only form: versions, instances and metadata.
view_api_instance_details
Displays one API instance with a header matching the web app, from the instance itself or from its identifiers.
view_api_instance_monitoring
Presents monitoring charts, traffic and clients for one API instance, as a visual panel rather than raw figures.
view_api_instance_policies
Displays the policies applied to one API instance, grouped the same way as in the web app.
view_api_version_details
Shows one API version in read-only form, with its instances, metadata and lifecycle fields.
view_api_version_governance_report
Presents the governance ruleset report summary and its findings for one API version.
view_api_version_instances
Lists the instances of one API version and lets you select some of them to hand back to the conversation for the next step.
view_governance_report
Fetches the latest governance strategy report for your organization and displays it in an interactive panel inside the chat.
view_llm_details
Shows one language model's details in read-only form: versions, instances and metadata.
view_mcp_server_details
Shows one tool server's details in read-only form, with its versions, instances and metadata.
What Claude changes (9)
9 toolsNine tools that apply policies, set up gateways, scanners and servers, or delete strategies. No source describes a Claude confirmation specific to them.
apply_policy_to_instance
Approval: see the rulePuts the selected policy in place on the target API instance, using the configuration you filled in.
create_automated_policy_strategy
Approval: see the ruleSets up a governance strategy that applies policies automatically, from the answers given in its wizard.
create_omni_gateway
Approval: see the ruleOpens the managed gateway wizard for the active MuleSoft provider and, once fully configured, sets up the gateway in Anypoint Platform.
create_scanner
Approval: see the ruleRuns the scanner wizard, which walks through provider choice, authentication and configuration, then returns the new scanner's details.
delete_automated_policy_strategy
Approval: see the ruleRemoves one automated-policy governance strategy, picked by its identifier.
delete_governance_strategy
Approval: see the ruleTakes one governance strategy away, identified by its strategy identifier.
provision_mcp_server
Approval: see the ruleDeploys a composite tool server on Flex Gateway, assembled from systems picked in the trusted catalogue.
resume_provision_job
Approval: see the rulePicks a failed provisioning or update job back up from its last checkpoint, provided some steps had already completed.
update_mcp_server
Approval: see the ruleBrings an existing catalog-managed server in line with a new configuration by comparing it with what is deployed and applying only the differences; it returns a job to follow.
Not documented (5)
5 toolsThe directory lists these five names, but MuleSoft's reference dated September 2026 does not. This page will not guess what they do.
check_control_scope_targets
This name sits in the directory's tool list and nowhere in MuleSoft's current reference. No official source describes it, so this page says nothing more about it and makes no guess.
create_control
Listed on the directory sheet, absent from MuleSoft's tool reference: no documentation describes this one either. Filling the gap with a guess from its name would be misleading.
fetch_control_ruleset
Here again the directory shows a name that MuleSoft's reference does not contain. With no official description available, the note stops at that fact and draws no conclusion from the name.
prepare_control_creation
One more name from the directory with no entry in MuleSoft's reference and no description anywhere official. The page leaves it undocumented rather than inventing a role for it on the strength of a name.
view_service_governance_findings
The fifth name the directory lists without any match in MuleSoft's tool reference. No official text describes it, so this page does not either, and no role is assumed from the wording.
What Claude asks you before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. No source describes a MuleSoft-specific confirmation, so that rule covers policies, deployments and deletions.
Anypoint adds its own gate. The connected app acts on your behalf, and MuleSoft says some tools need additional permission scopes, tied to Anypoint roles such as API Manager Environment Admin or Governance Administrator. Without the right one, a call cannot go through, whatever Claude does. On Team or Enterprise, Claude's owners decide whether members may skip prompts and can restrict the connector for everyone.
Which plans this is available on
Out of 819 directory sheets, not one shows availability by plan. The connector-by-connector answer is published nowhere: it is a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can connect. On the MuleSoft side, the connected app and Anypoint permissions set what works. For this connector's current state, check its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: no scan, report or policy runs because a new API was published.
Everything known here comes from MuleSoft's documentation and the directory sheet; Claude's help centre has no page on this connector. The tool list is an observed floor, not a promise, and MuleSoft's reference already mentions tools the sheet does not show. The verification badge is not a security audit either: Anthropic states on every sheet that it does not choose the tools a publisher exposes. The Integrations hub gathers the other ways to connect MuleSoft.
Need help connecting MuleSoft to Claude?
A person reads every message.