MuleSoft

Name: MuleSoft MCP Server
Availability: InStock
Author: MuleSoft

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Analytics66 tools

Discover, govern and monitor every API, agent, MCP server and LLM in your Anypoint estate from an AI assistant. 66 tools, OAuth via Anypoint Platform.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect MuleSoft via MCP

https://omni.mulesoft.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect MuleSoft once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

MuleSoft Tools & Capabilities (66)

apply_policy_to_instance

check_control_scope_targets

check_policy_conformance

create_automated_policy_strategy

create_control

create_omni_gateway

create_scanner

delete_automated_policy_strategy

delete_governance_strategy

fetch_automated_policy_template

fetch_control_ruleset

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_control_creation

prepare_policy_creation

provision_mcp_server

resume_provision_job

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

update_mcp_server

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

view_service_governance_findings

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

There is no read-only scope. The endpoint's own RFC 9728 descriptor advertises exactly two scopes, full and offline_access, and MuleSoft's troubleshooting tells you to add Full Access and Background Access to the connected app when authorization fails. On a 66-tool server that can apply policies to live API instances and provision gateways, that is the single most important fact on this page. Anypoint's own authorization server publishes 133 scopes including read:full, so a narrower grant exists at the platform level — it is simply not what this MCP resource offers. Constrain access with Anypoint roles instead, not with the OAuth grant.
Access is governed by your Anypoint org, not by the connector. Every tool maps to an existing Anypoint permission. An assistant holding your token inherits your roles exactly, which is reassuring if your role model is tight and alarming if it is not.
Setup is not one click. You create a connected app, choose grant types, add scopes and register a redirect URL before the connector will authorise at all. MuleSoft states that Dynamic Client Registration is not supported.
Two tool-naming conventions are in circulation. Four governance tools are listed under control names in Anthropic's directory and guardrail names in MuleSoft's reference, and three further names appear on only one side. We could not resolve which the live server answers to.
The product is new. MuleSoft's release notes date the Platform server to 28 May 2026. Expect the tool surface to move; check the release notes before relying on a specific name.
We did not exercise any tool. Our checks were anonymous protocol requests that returned an OAuth challenge, plus reads of two public well-known documents. Everything above about tool behaviour comes from MuleSoft's documentation or the directory listing, not from running anything.
Anthropic's directory flags this connector as shipping an MCP app (has_mcp_app: true in the snapshot of 2026-08-16), and MuleSoft's tool reference repeatedly describes tools that "launch a wizard" for gateway, scanner, policy and guardrail creation. We could not confirm what that interactive surface renders, because reading it requires a session we do not have.

Frequently asked questions

MuleSoft Platform MCP Server, the hosted one at omni.mulesoft.com. MuleSoft ships three MCP things and only this one is a remote connector. MuleSoft DX MCP Server is a local npm package for IDE development work, and the MuleSoft MCP Connector is a component you drop inside a Mule application to expose your own flows as tools.

Full Access, plus Background Access for token refresh. When we queried the endpoint's own protected-resource descriptor on 2026-08-18 it advertised exactly two scopes, full and offline_access. There is no read-only scope on offer, so a token that can read your governance reports can also apply policies.

Yes, and you have to create it yourself first. MuleSoft's setup guide requires a connected app that acts on the user's behalf, with the Authorization Code and Refresh Token grant types selected. Its documentation states the servers do not support Dynamic Client Registration, so the client ID and secret are manual.

Almost always a redirect URL mismatch. MuleSoft's troubleshooting explains that IDE clients use a localhost callback whose port changes each session, so the URL stops matching the one registered in your connected app. Fix it by pinning a fixed callback port and registering that exact localhost URL.

It depends on the tool, and MuleSoft publishes the mapping per tool. Reading APIs needs Exchange Viewer, monitoring needs Monitoring Viewer, applying a policy needs API Manager Environment Admin, and creating a guardrail needs Governance Administrator. Your existing Anypoint org roles govern what the assistant can do.

Yes. The tool list includes applying policies to live API instances, creating managed gateways and scanners, provisioning MCP servers on Flex Gateway, and deleting governance strategies. MuleSoft documents these as actions taken on your behalf, gated by Anypoint role rather than by any per-tool read-only switch.