You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/a4d-mcp-server.adoc
+5-81Lines changed: 5 additions & 81 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,92 +1,21 @@
1
1
= Configure an MCP Server
2
2
3
+
Add and manage MCP servers in Anypoint Code Builder to extend MuleSoft Dev Agent with tools for API design, integrations, governance, and agent networks.
4
+
5
+
== Use the MuleSoft MCP Server
6
+
3
7
The MuleSoft MCP Server is integrated within Anypoint Code Builder and provides built-in tools to extend MuleSoft Dev Agent’s capabilities.
4
8
5
9
You can use these tools to generate API specifications, create and deploy integrations, manage governance rulesets, and build Agent Fabric agent networks. You can also work with DataWeave and gain insights into the performance of your applications and APIs—all directly from Anypoint Code Builder.
6
10
7
11
MuleSoft MCP Server tools are available in Anypoint Code Builder and are also supported when you use the Anypoint Extension Pack in compatible IDEs such as VS Code, Cursor, and Windsurf.
8
12
9
-
For more information about these tools and their parameters, see: xref:mulesoft-mcp-server::reference-mcp-tools.adoc[MuleSoft MCP Server Tool Reference].
* `create_agent_network_project` – Create and scaffold agent-network projects.
15
-
* `deploy_agent_network` – Deploy an agent network to a runtime environment.
16
-
* `publish_agent_network_assets` – Publish agent network assets to Anypoint Exchange for reuse.
17
-
18
-
== Application Development
19
-
20
-
* `create_and_manage_assets` – Create, update, and delete assets in Anypoint Exchange.
21
-
* `create_and_manage_metadata` – Define, attach, and update metadata for Mule flow components.
22
-
* `create_MCP_server` – Use the MCP Connector in a Mule project to create a MuleSoft MCP server.
23
-
* `create_mule_project` – Create a Mule project structure in a given directory.
24
-
* `generate_api_spec` – Use AI to generate, modify, or enhance an API specification.
25
-
* `generate_mule_flow` – Generate or update Mule flows and integration logic from natural language prompts.
26
-
* `generate_munit_test` - Generates MUnit test cases for Mule flows, one test scenario at a time, with support for mocks, assertions, and dependencies.
27
-
* `get_topics_agent_actions_metadata_instructions` – Retrieve metadata and instructions for enabling topics and agent actions from an OpenAPI spec.
28
-
* `implement_api_spec` - Use APIkit flows to implement an API specification in a new integration project. You can implement a specification from a local project or an Anypoint Exchange asset.
29
-
* `mock_api_spec` – Mock an API specification to test endpoint functionality through a mocking service.
30
-
* `modify_munit_test` - Modify or fix an existing MUnit test case, including updating assertions, mocks, payloads, and test logic.
31
-
* `open_project` – Open or manage an existing API, Mule, or agent-network project.
32
-
* `run_local_mule_application` – Run a Mule application locally, handling build and local runtime setup.
33
-
* `search_asset` – Search for assets in Anypoint Exchange by using flexible filters and criteria.
34
-
* `test_connection` – Validate connector configurations (such as HTTP or Salesforce connectors) in a Mule project.
35
-
* `validate_project` – Validate the current project, such as an API spec or agent network project, before deploying or publishing.
36
-
37
-
38
-
== Connector Development
39
-
40
-
* `uc_create_connector_workflow` – Create a complete LinkWeave connector end-to-end with a guided workflow plan.
41
-
* `uc_generate_api_spec` – Generate an OpenAPI 3.0 spec from use cases and API documentation.
42
-
* `uc_generate_connector` – Generate a complete LinkWeave connector from an existing API spec.
43
-
44
-
45
-
== DataWeave Development
46
-
47
-
* `dataweave_create_documentation` – Generate DataWeave documentation for functions based on descriptions, parameters, and examples.
48
-
* `dataweave_create_project` – Create a new DataWeave project and return the project location.
49
-
* `dataweave_create_sample_data` – Create DataWeave input sample data for a given transformation file.
50
-
* `dataweave_get_module_metadata` – Return functions, parameters, and types for a specific DataWeave module.
51
-
* `dataweave_get_project_metadata` – Return metadata for a DataWeave project, including modules, functions, and supported data formats.
52
-
* `dataweave_open_project` – Open a DataWeave project from a given URL in the current window or a new window.
53
-
* `dataweave_run_script_tool` – Run a DataWeave transformation with sample data to validate the script output.
54
-
55
-
56
-
== Application Management
57
-
58
-
* `create_and_manage_api_instances` – Create and configure API instances in Anypoint API Manager.
59
-
* `deploy_mule_application` – Deploy Mule applications to CloudHub 2.0 or Runtime Fabric with optional HA, security, and performance settings.
60
-
* `list_api_instances` – List API instances in an environment and optionally include applied and available policies.
61
-
* `list_applications` – List Mule applications in an environment and optionally include metrics and logs.
62
-
* `update_mule_application` – Update a Mule application deployment configuration, including runtime version, replicas, and scaling options.
63
-
64
-
65
-
=== Governance
66
-
67
-
* `add_governance_ruleset` – Add a governance ruleset from Anypoint Exchange to your project.
68
-
* `list_governance_rulesets` – List governance rulesets that apply to your project.
69
-
* `validate_api_against_ruleset` – Validate an API spec against governance rulesets and rules.
* `manage_api_instance_policy` – Apply or update policies on an API instance in API Manager.
76
-
* `manage_flex_gateway_policy_project` – Guide the LLM in creating, configuring, building, and publishing Flex Gateway custom policy projects.
77
-
78
-
79
-
== Usage and Insights
80
-
81
-
* `get_platform_insights` – Get usage and operational insights for applications and APIs across your organization.
82
-
* `get_reuse_metrics` – Get reuse metrics for assets across your organization to understand adoption and reduce duplication.
83
-
13
+
For more information about the MuleSoft MCP Server tools and their parameters, see: xref:mulesoft-mcp-server::reference-mcp-tools.adoc[MuleSoft MCP Server Tool Reference].
84
14
85
15
== Add and Manage Custom MCP Servers
86
16
87
17
From the MuleSoft Dev Agent panel, you can add your own MCP server or manage connected MCP servers through the MCP Server settings.
88
18
89
-
90
19
== Open MCP Server Settings
91
20
92
21
. Open the MuleSoft Dev Agent panel in Anypoint Code Builder.
@@ -103,7 +32,6 @@ This opens the MCP Servers UI with three tabs:
103
32
104
33
With these views, you can install new MCP servers, connect to remote MCP servers, and manage existing MCP servers.
105
34
106
-
107
35
== Add an MCP Server
108
36
109
37
You can add a custom MCP server by installing the server from the Marketplace, adding a remote MCP server, or manually editing the configuration file.
@@ -124,7 +52,6 @@ NOTE: Marketplace servers include community-provided MCP servers. Not all server
124
52
. Click *Add Server* to connect to the remote instance.
125
53
. (Optional) Select *Edit Configuration* to manually configure the MCP server by updating the `a4d_mcp_settings.json` file.
126
54
127
-
128
55
=== Manually Configure the JSON File
129
56
130
57
If needed, you can configure MCP servers directly by editing the `a4d_mcp_settings.json` file:
@@ -145,7 +72,6 @@ Once an MCP server has been installed, you can manage it from the *Installed* ta
145
72
. Toggle each MCP server on or off.
146
73
. To restart a server, select *Restart Server* from its configuration panel.
147
74
148
-
149
75
== Manage Tools for an MCP Server
150
76
151
77
Each MCP server provides a set of tools that Dev Agent can use. The following steps show you how to work with an MCP server:
@@ -157,15 +83,13 @@ Each MCP server provides a set of tools that Dev Agent can use. The following st
157
83
NOTE: Auto-approval for tools is available only if Auto-approve has been enabled in Dev Agent settings.
158
84
. To auto-approve all tools from a server, scroll to the bottom of the list and enable *Auto-approve all tools*.
159
85
160
-
161
86
== Configure Request Timeout
162
87
163
88
Follow these steps to configure how long Dev Agent waits for a response from an MCP server:
164
89
165
90
. In the server details panel, locate *Request Timeout*.
0 commit comments