Validate MCP tools
POST/v1/brains/:brain_id/mcps/validate
Returns the tools as a write would store them, without writing anything. A tool keeps only the fields and the JSON Schema keywords described in McpToolDefinition, so a caller that holds a listing from the MCP server can tell what a write would change. A listing that no write would accept answers 400, as the write itself would, and so does a call on a published brain version, like every other MCP route.
Permissions - brains.write. API keys - manage.
Request
Responses
- 200
- 400
- 401
- 500
The tools as they would be stored
BadRequest
Response Headers
X-Request-Id
Unique identifier for the API request, useful for debugging and tracking.
Example:
abc123xyz789Unauthorized
Response Headers
X-Request-Id
Unique identifier for the API request, useful for debugging and tracking.
Example:
abc123xyz789Internal Server Error
Response Headers
X-Request-Id
Unique identifier for the API request, useful for debugging and tracking.
Example:
abc123xyz789