After you create an MCP server, you manage it from the MCP servers list in AI studio. From there, you can update its tools and settings, test it, monitor the requests it receives, review configuration changes, and delete servers you no longer need. This article is for account owners and administrators.
Who can manage MCP servers: MCP servers, including their request history, are available only to account owners and administrators.
View your MCP servers
Go to AI studio > MCP servers to see every MCP server in your account. The list shows the key details for each server.
To install an MCP server from a ZIP file, select Upload next to Create MCP server. See Upload an MCP server.
Select Actions (...) next to a server to open these options:
- Edit MCP server – Update the server's configuration and the tools it exposes.
- View request logs – Open the server's request history to see every request MCP clients sent, open a trace view for a request, and delete stored request data.
- View audit logs – See the history of configuration changes made to the server.
- Download MCP – Downloads the MCP server as a ZIP file that you can upload to another account or environment.
- Delete MCP server – Remove the server from your account.
Edit an MCP server
Edit an MCP server when you need to change which tools it exposes, rename it, update its URI, or turn it on or off. When you save your changes, Celigo automatically updates any resources that depend on the server so they reflect the new tool set.
Use the following steps to edit or update each MCP server:
-
On the Home page in the left pane, click MCP server under AI studio. A list of MCP servers are displayed.
Note
If you don’t have any MCP server added, you click Create MCP server to add one.
- Click the Actions (...) icon for the required MCP server and select Edit MCP server.
-
Use the following tabs to make the required changes in the Edit MCP server page.
Edit MCP server tabs
| Tab | What you can do |
|---|---|
| Configuration | Add or remove MCP tools, rename the server or update its description, edit the server URI, view or update the assigned token, and enable or disable the server. Select Test server to see the tools the server exposes. |
| Access | Choose how users and clients authenticate to the server, manage API tokens, and see which end users, groups, and roles have access. Create capability sets to assign groups of capabilities together. For more information, see Set up authentication for an MCP server, Create and manage capability sets on MCP servers, and manage API tokens. |
| Audit log | View detailed configuration change history for a selected time frame. Select Download to export the details. |
| Connections | View the connections used by the server's tools, configure end user authentication for a connection, and check the status of connections that end users have configured. |
In the Edit MCP server header, you can also change what the server logs with Change log mode, or capture debug logs for a limited time with Debug. For more information, see View MCP server request and execution logs.
Set the MCP server URI
The Relative URI field sets the resource path that MCP clients use to reach the server. The URI must meet these rules:
- It's a single root-level segment.
- It starts with exactly one leading slash (for example,
/orders). - It contains no other slashes, so nested paths such as
/sales/ordersaren't allowed. - It's unique within your account.
If another MCP server in your account already uses the same URI, you see this error when you save: An MCP server with relative URI 'URI name' already exists. Enter a different URI and save again.
Test the server
After you save your changes, select Test server on the Configuration tab. The Preview window lists every tool the server exposes, so you can confirm it includes all the tools your MCP clients need.
Note
Save and enable the MCP server before you test it.
View request logs
View MCP server request logs to monitor server activity, identify users and access tokens, and troubleshoot failed requests. Depending on the configured log mode, you can also review request and response details and tool execution steps.
Request logs, like the rest of MCP servers, are available only to account owners and administrators.
For instructions, see View MCP server request and execution logs. To remove stored request and response data, see Delete logs from MCP server request history.
View audit logs
Audit logs record every configuration change made to an MCP server and its tools, so you can track who changed what and meet governance and compliance requirements. Select Actions (...) > View audit logs, or open the Audit log tab while editing the server. The audit log also records each log mode change, each debug logging session, and each time someone deletes request logs, which appears as a Purge logs action. You can view the logs in Celigo or download them. For more information, see view or download your audit logs.
Download an MCP server
Download an MCP server as a ZIP file to reuse its capabilities and configuration in another account or environment.
- Go to AI studio, and then select MCP servers.
- Select Actions next to the MCP server, and then select Download MCP.
The ZIP file is saved to your browser's default download location.
The ZIP file includes the MCP server's supported capabilities and configuration, such as tools and their dependencies, APIs, prompts, resources, MCP proxies, capability sets, traffic limits, and which connections require end user authentication.
Note
Connection credentials, API tokens, end users, groups, roles, access assignments, end users' own connections, network policies, and request log settings aren't included. The MCP server in the ZIP file is turned off.
Download limitations
You can't download an MCP server if:
- A resource file exceeds 3 MB.
- The resource files total more than 32 MB.
- A resource file is missing, deleted, or hasn't finished uploading to Celigo Storage.
- A capability set references a capability that's no longer on the server.
Note
The ZIP file contains a copy of the MCP server at the time of download. If you update the server or its resources later, download it again to include those changes.
Upload an MCP server
Upload an MCP server from a ZIP file to reuse its capabilities and configuration in another account or environment without publishing it to the Marketplace. The ZIP file must be created using Download MCP.
Prerequisites:
- You must be an account owner or administrator.
- Your account must have an MCP account alias.
- If the ZIP file includes resources, Celigo Storage must be available in your account. You can't install resources in a legacy sandbox.
To upload an MCP server:
- Go to AI studio, and then select MCP servers.
- Select Upload next to Create MCP server.
- In Upload an MCP server, select Select a file and choose the ZIP file, or drag and drop it into the upload area. You can upload one ZIP file of up to 32 MB.
- In Install MCP server, review the components that will be created. The preview lists the tools, APIs, prompts, resources, and connections included in the file. Proxied capabilities and capability sets aren't listed, but they're included in the server.
- Select Install.
- If the ZIP file contains only prompts, Celigo creates the MCP server and returns to the MCP servers list.
- Otherwise, Celigo creates an integration and opens its setup steps. Complete the required connection configurations to finish installing the MCP server.
After uploading
Celigo creates the MCP server in your current account and environment, with its supported capabilities and configuration.
The server is turned off by default. If its Relative URI is already in use, Celigo assigns a unique URI, such as /orders-2.
Before using the server:
- Review its configuration, including the Relative URI and connections.
- Grant access to the required end users and groups. Capability sets are uploaded without assignments.
- Turn on the MCP server using Off/On in the MCP servers list.
Note
Each upload creates a new MCP server, even when you upload the same ZIP file again.
Troubleshoot upload issues
If an upload fails, Celigo checks the ZIP file before it creates anything and shows the reason in the upload area:
| Message | What it means |
|---|---|
| Only .zip files are supported. | The file isn't a .zip file. |
| Only one file can be uploaded at a time. | You selected more than one file. |
| File exceeds the 32 MB limit | The ZIP file is larger than 32 MB. |
| Upload failed. Please try again. | The file couldn't be uploaded. Try again. |
| The MCP template zip is damaged or is not a zip file. | The file is damaged or isn't a valid ZIP file. Download the MCP server again. |
| mcpserver.json not found. | The ZIP file wasn't created with Download MCP. For example, it's an integration ZIP file. |
| The MCP template zip exceeds the allowed size. | The ZIP file's contents are larger than 32 MB uncompressed, or it contains more than 500 files. |
| A resource file in this MCP server exceeds the allowed size. | A resource file is larger than 3 MB, or the server has more than 100 resources. |
| The MCP template contains an invalid entry. | The ZIP file contains a file or path that isn't allowed. Download the MCP server again instead of editing the ZIP file. |
| MCP server references tool …, which is missing from the template zip. | A tool the server uses is missing from the ZIP file. |
| The MCP template is missing a required dependency. | An API or connection the server uses is missing from the ZIP file. |
| A resource file in this MCP server is missing or cannot be exported. | The ZIP file includes resources, and you're working in a legacy sandbox. |
If installation fails during the setup steps, Celigo shows: The MCP template could not be processed. Common causes are an existing connection that isn't the same type as the template's connection, Celigo Storage not being available in your account, or a temporary error.
Important
If installation fails during the setup steps, fix the issue and retry the failed step. Don't upload the ZIP file again, because that creates another integration.
Delete an MCP server
Delete an MCP server when you no longer need it. Only account owners and administrators can delete MCP servers.
Before you delete a server, remove all the associated references to it. For example, if an access token is assigned to the MCP server, go to the Access tokens tab, find the token, and delete it first.
If the server is still referenced by another resource, Celigo blocks the deletion and shows this message:
Unable to delete MCP server. This MCP server is referenced by at least one resource. Before you can delete this MCP server, you must edit each resource to remove the reference.
If nothing references the server, Celigo removes it from your list and archives it so it can be retrieved later. Archived servers aren't permanently deleted or automatically cleaned up.
Note
Deleting an MCP server installed from a Marketplace template or ZIP file doesn't delete the resource files copied to Celigo Storage. The files remain in the integration's folder. To remove the installed server completely, delete the MCP server, its tools, and then the integration.
Use the following steps to delete each MCP server:
-
On the Home page in the left pane, click MCP server under AI studio. A list of MCP servers are displayed.
Note
If you don’t have any MCP server added, you click Create MCP server to add one.
- Click the Actions (...) icon for the required MCP server and select Delete MCP server. Before deleting a MCP server, you must remove all the associated references with the selected MCP server from other sources.