Update MCP server
Edit an MCP server’s connection settings or reassign its owning team.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | None — any valid app_key can call this operation |
Usage
- Built-in MCP servers are read-only and cannot be modified.
- Every call is recorded in the account’s audit log.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call.
Body
Editable fields of an MCP server; omitted fields are left unchanged.
Identifier of the server to update.
New display name.
1 - 255New description.
1 - 1024New transport for the server.
stdio, sse, streamable-http New stdio executable.
New stdio arguments.
New stdio environment variables.
New endpoint URL for remote transports.
New HTTP headers for the remote endpoint.
New connection timeout in seconds.
New per-call timeout in seconds.
Reassign the server to this team; omit to leave unchanged, 0 for account scope.
New credential model.
New per-user secret JSON schema.
New OAuth metadata JSON.
Response
Success
Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.
Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.
"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"
Error payload inside the response envelope. Present only on non-2xx responses.
A configured MCP (Model Context Protocol) server the agent can call tools through.