`POST /api/v1/mcp/servers`, Add a new MCP server and persist it to `mcp.db`.

POST 
/api/v1/mcp/servers

The addition is first submitted to the connection admission; a refusal answers 403 Forbidden with its reason, before any process is spawned and before anything is written to mcp.db. Spawns the server process and registers its tools, then saves the configuration and journals the addition. Returns 201 Created with the server status on success. Returns 409 Conflict when a server with the same name is already managed. Returns 400 Bad Request for invalid configurations or spawn failures. Returns 503 Service Unavailable when MCP is not configured.

Responses

201

Server added and persisted

400

Invalid configuration or spawn failure

403

Refused by the connection admission

409

Server already exists

500

Repository error

503

MCP not configured