Create MCP Server
Register an MCP server for the organisation and schedule an immediate capability probe. The url_template, auth, and headers are validated and every referenced Vault secret must already exist. A duplicate live name returns 409.
Authorizations
Your SLNG consumer API key.
Body
Configuration for the MCP server to register.
Configuration for registering a new MCP server, covering transport, endpoint URL, authentication, extra headers, and any Vault secrets to create or reference.
1 - 200Endpoint URL for the MCP server. Embed Vault secret placeholders with the {{$NAME}} grammar to keep credentials out of the URL.
1 - 2000Transport to reach the MCP server: streamable_http (the default) for streamable HTTP, or sse for Server-Sent Events.
streamable_http, sse Optional human-readable description of the MCP server.
500Send requests to the MCP server without an Authorization header.
- No authentication
- Bearer token
- Custom auth header
Extra request headers to send to the MCP server. Each header is a literal value or a reference to a Vault secret.
64A request header with a fixed, inline value.
- Literal header
- Vault-backed header
Vault secrets to create or reference for use by the URL, auth, or headers. Every credential name you supply must be referenced by the configuration.
64Reference a secret already stored in Vault by secret_name.
- Use an existing Vault secret
- Create a new Vault secret
Response
The registered 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.