Start MCP server
POSThttp://localhost:3282/v0/servers/:id/start
Launches an MCP server instance identified by its unique ID. This endpoint executes the server's configured command with appropriate arguments and environment variables. The server process is monitored by the router, and its status is updated accordingly. If the server is already running, the request will return the current status without restarting the server.
Request
Path Parameters
id stringrequired
ID of the server to start
Responses
- 200
- 400
- 404
- 500
Server started successfully
- application/json
- Schema
- Example (auto)
Schema
successboolean
Whether the server was started successfully
messagestring
Success message
statusstring
Current status of the server
{
"success": true,
"message": "string",
"status": "string"
}
Missing server ID
- application/json
- Schema
- Example (auto)
Schema
error object
{
"error": {
"code": "string",
"message": "string"
}
}
Server not found
- application/json
- Schema
- Example (auto)
Schema
error object
{
"error": {
"code": "string",
"message": "string"
}
}
Failed to start server
- application/json
- Schema
- Example (auto)
Schema
error object
{
"error": {
"code": "string",
"message": "string"
}
}
Authorization: http
name: bearerAuthtype: httpscheme: bearerdescription: Authentication uses Bearer token format. The token can be provided directly or with 'Bearer ' prefix. Different API endpoints may require different token scopes: - /v0/servers/* requires MCP_SERVER_MANAGEMENT scope - /v0/logs/* requires LOG_MANAGEMENT scope - /v0/apps requires APPLICATION scope - /mcp endpoint doesn't require a specific scope but still requires authentication
- curl
- javascript
- python
- CURL
curl -L -X POST 'http://localhost:3282/v0/servers/:id/start' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <token>'
ResponseClear