MuleSoft
by MuleSoft
Discover, govern and monitor every API, agent, MCP server and LLM in your Anypoint estate from an AI assistant. 66 tools, OAuth sign-in via Anypoint Platform, SSE transport.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect MuleSoft via MCP
https://omni.mulesoft.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
MuleSoft Tools & Capabilities (66)
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,
fullandoffline_access, and MuleSoft's troubleshooting tells you to addFull AccessandBackground Accessto 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 includingread: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
controlnames in Anthropic's directory andguardrailnames 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: truein 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
Which MuleSoft MCP server does this connector actually run?
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.
What permissions does the MuleSoft MCP server ask for?
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.
Do you need an Anypoint connected app to use the MuleSoft connector?
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.
Why does MuleSoft MCP authorization keep failing in Claude Code or Cursor?
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.
Which Anypoint roles do you need for the MuleSoft MCP tools to work?
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.
Can the MuleSoft MCP server change things in production?
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.
Sources
- Live OAuth posture check against
https://omni.mulesoft.com/mcp— an anonymousinitializereturns HTTP 401 withWWW-Authenticate: Bearer realm="mcp"pointing at an RFC 9728 protected-resource descriptor. That descriptor returns HTTP 200 and declaresauthorization_servers: ["https://anypoint.mulesoft.com"]withscopes_supported: ["full", "offline_access"]. This is our own observation on 2026-08-18, and it is why the sign-in requirement and the missing read-only scope are stated as verified rather than quoted. It is also why no tool descriptions, parameter schemas or safety annotations appear on this page: the handshake never reachedtools/list. The/mcp/ssepath and theeu1regional host returned the same challenge on the same date. · retrieved 2026-08-18 - Anypoint Platform authorization server metadata (HTTP 200, our own read on 2026-08-18; 133 scopes,
code_challenge_methods_supported: ["S256"]) · retrieved 2026-08-18 - Getting Started with MuleSoft Platform MCP Server (HTTP 200, retrieved 2026-08-18). Source for prerequisites, connected app setup, per-permission tool tables, client configuration, regional endpoints and troubleshooting. · retrieved 2026-08-18
- MuleSoft Platform MCP Server Tool Reference (HTTP 200, retrieved 2026-08-18). Source for the Command Summary categories, per-tool descriptions and the control-vs-guardrail naming comparison. · retrieved 2026-08-18
- Using MuleSoft Platform MCP Server (HTTP 200, retrieved 2026-08-18). Source for the example prompts and the documented policy-application call sequence. · retrieved 2026-08-18
- MuleSoft MCP Servers Release Notes (HTTP 200, retrieved 2026-08-18). Source for the 28 May 2026 launch date and the DX rename. · retrieved 2026-08-18
- MuleSoft documentation index — and (HTTP 200, retrieved 2026-08-18).
docs.mulesoft.com/robots.txtallows crawling and carriesContent-Signal: ai-input=yes, ai-train=no, search=yes— synthesis into AI-generated output is expressly permitted by the publisher, and this page honours the training refusal. · retrieved 2026-08-18 - Anthropic Connectors Directory entry, including the 66 tool names, transport, tier and
has_mcp_appflag (from the committed directory snapshot of 2026-08-16) · retrieved 2026-08-16 - MuleSoft support — · Privacy (Salesforce's, as MuleSoft's parent; HTTP 200, checked 2026-08-18) · retrieved 2026-08-18
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Analytics
- Developer
- MuleSoft
- Tools
- 66
- Domain
- omni.mulesoft.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.