Update MCP Server
Apply a partial update. The fields you send are merged over the stored configuration, then the merged url_template, auth, headers, and Vault secret references are re-validated. Changing connection behavior resets discovered capabilities and reschedules a probe.
Authorizations
Your SLNG consumer API key.
Path Parameters
UUID of the MCP server to update. A server in another organisation or one that is soft-deleted returns 404.
Body
Fields to change on the MCP server.
Partial update for an MCP server. Only the fields you supply change; omitted fields keep their stored values.
1 - 200New endpoint URL for the MCP server. Supports {{$NAME}} Vault secret placeholders.
1 - 2000New transport for the MCP server, either streamable_http or sse.
streamable_http, sse Optional human-readable description of the MCP server. Omit to keep the current value.
500Send requests to the MCP server without an Authorization header.
- No authentication
- Bearer token
- Custom auth header
Replacement set of request headers. Each header is a literal value or a Vault secret reference.
64A request header with a fixed, inline value.
- Literal header
- Vault-backed header
Vault secrets to create or reference for the updated configuration. Every supplied credential name must be referenced.
64Reference a secret already stored in Vault by secret_name.
- Use an existing Vault secret
- Create a new Vault secret
Response
The updated MCP server.
Stored MCP server record with its configuration and the latest discovered capability state. Secret values and transient credential input never appear here.
Transport used to reach the MCP server: streamable_http for streamable HTTP, or sse for Server-Sent Events.
streamable_http, sse Stored endpoint URL for the MCP server. Any {{$NAME}} Vault secret placeholders are kept verbatim and resolved at connection time.
Send requests to the MCP server without an Authorization header.
- No authentication
- Bearer token
- Custom auth header
Health of the MCP server capabilities: unknown (not probed yet), healthy (reachable and tools discovered), unavailable (probe failed or unreachable), invalid (reachable but returned an unsupported contract), or circuit_open (temporarily disabled after repeated failures and retried after a cooldown).
unknown, healthy, unavailable, invalid, circuit_open Stored request headers for the MCP server; each value is inline or resolved from a Vault secret.
A request header with a fixed, inline value.
- Literal header
- Vault-backed header
Tools discovered from the MCP server, with flags for whether discovery was truncated and how many pages were fetched.