diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index f3c61c60..a510afe6 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -7,6 +7,7 @@ *** xref:create-instance-task-mule.adoc[Add a Mule Gateway API Instance] *** xref:create-instance-task-flex.adoc[Add a Flex Gateway API Instance] *** xref:create-instance-task-agent-tool.adoc[Add a Flex Gateway Agent or Tool instance] + *** xref:create-instance-public-exchange.adoc[Add an MCP Server from Public Exchange] ** xref:find-api-id-task.adoc[Obtain an API Instance ID] ** xref:export-api-latest-task.adoc[Export an API Instance] ** xref:access-developer-portal-task.adoc[Access the Developer Portal] diff --git a/modules/ROOT/pages/api-instance-landing-page.adoc b/modules/ROOT/pages/api-instance-landing-page.adoc index ef4dcf10..14b2eda4 100644 --- a/modules/ROOT/pages/api-instance-landing-page.adoc +++ b/modules/ROOT/pages/api-instance-landing-page.adoc @@ -22,6 +22,7 @@ To manage instances in API Manager: ** xref:create-instance-task-mule.adoc[] ** xref:create-instance-task-flex.adoc[] ** xref:create-instance-task-agent-tool.adoc[] +** xref:create-instance-public-exchange.adoc[] . View an instance's summary for information or to export it: ** xref:find-api-id-task.adoc[] - API Manager generates the `apiId` of new APIs managed by API Manager for use with Mule 4. ** xref:export-api-latest-task.adoc[] - After creating an instance, you can export it. This exports the instance configuration and Exchange asset relationship. You can then import it into another environment in the same business group to create a new instance. diff --git a/modules/ROOT/pages/create-instance-public-exchange.adoc b/modules/ROOT/pages/create-instance-public-exchange.adoc new file mode 100644 index 00000000..f1a6293c --- /dev/null +++ b/modules/ROOT/pages/create-instance-public-exchange.adoc @@ -0,0 +1,54 @@ += Adding an MCP Server from Public Exchange +ifndef::env-site,env-github[] +include::_attributes.adoc[] +endif::[] + +This workflow describes how to create an MCP server in API Manager by selecting an asset published in the public Exchange (Provided by MuleSoft). + +To base a new instance on an MCP server published to Exchange and maintained outside your organization, use this workflow. + +== Add an MCP Server or Agent Instance from Public Exchange + +. Navigate to *Anypoint Platform* > *API Manager*. +. Select an instance type. +. Click *Add* to start the guided experience. +. Click *Next* until you reach the *Select asset from Exchange* step. + +. In *Organization*, select *Provided by MuleSoft*. ++ +Selecting *Provided by MuleSoft* lets you browse and search assets that are publicly available in Exchange. + +. To find an asset, search by name or filter using the *Provided by Mulesoft* tag. ++ +Use tags to narrow down the list of available assets. + +. Select an asset from the list. ++ +The asset list shows the latest available version and the date it was published to Exchange. You can select a different version if needed. + +. To review the asset details before continuing, click *View in Exchange*. + +. Click *Next*. + +[NOTE] +-- +When you select an asset from *Provided by MuleSoft*, API Manager automatically populates the instance metadata from Exchange, including the asset name and version. +-- + +. Continue through the remaining steps of the guided experience to configure the instance. ++ +The remaining configuration steps are the same as when creating an instance from a private Exchange asset. + +. Review the configuration and click *Save*. + +== What Happens Next + +After the instance is created, you can manage it in API Manager like any other instance. This includes applying policies, viewing instance details, and monitoring its status. + +Public Exchange assets are treated as read-only sources. The instance maintains a reference to the original Exchange asset rather than copying it into your organization’s private Exchange. + +== See Also + +* xref:latest-overview-concept.adoc[] +* xref:anypoint-exchange::index.adoc[] +* xref:create-instance-task-agent-tool.adoc[]