Create MCP server
Register a new MCP server the agent can call tools through.
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
transportmust be one of stdio, sse, or streamable-http; other values return InvalidParameter.- Duplicate server names return InvalidParameter.
- 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
Configuration for a new MCP server.
Display name of the server.
1 - 255What this MCP server provides.
1 - 1024Transport used to reach the server.
stdio, sse, streamable-http Executable to launch for stdio transport.
Command-line arguments for the stdio executable.
Environment variables for the stdio process.
Endpoint URL for sse or streamable-http transport.
HTTP headers sent to the remote endpoint.
Connection timeout in seconds.
Per-call timeout in seconds.
Initial lifecycle state of the server.
enabled, disabled Owning team for the new server; 0 for account scope.
Credential model; defaults to shared.
JSON schema of the per-user secret; required when auth_mode is per_user_secret.
OAuth metadata JSON; reserved for OAuth-based auth.
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.