Skip to main content
POST
Update MCP server

Restrictions

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
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call.

Body

application/json

Editable fields of an MCP server; omitted fields are left unchanged.

server_id
string
required

Identifier of the server to update.

server_name
string

New display name.

Required string length: 1 - 255
description
string

New description.

Required string length: 1 - 1024
transport
enum<string>

New transport for the server.

Available options:
stdio,
sse,
streamable-http
command
string

New stdio executable.

args
string[]

New stdio arguments.

env
object

New stdio environment variables.

url
string

New endpoint URL for remote transports.

headers
object

New HTTP headers for the remote endpoint.

connect_timeout
integer

New connection timeout in seconds.

call_timeout
integer

New per-call timeout in seconds.

team_id
integer<int64>

Reassign the server to this team; omit to leave unchanged, 0 for account scope.

auth_mode
string

New credential model.

secret_schema
string

New per-user secret JSON schema.

oauth_metadata
string

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.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

error
object

Error payload inside the response envelope. Present only on non-2xx responses.

data
object

A configured MCP (Model Context Protocol) server the agent can call tools through.