Initialize connection
Loading server catalog…. Download catalog
https://app.advarde.com/mcpAvailable subject to your connection’s permissions.
Description: Negotiate the MCP protocol version and client capabilities. Use the version returned by the server for subsequent requests.
Method: initialize
Output: See the protocol description and workflow notes below.
Access: Workspace-scoped MCP authentication.
Authentication
Use an MCP access token from MCP connections, or connect through OAuth. Send your token in the Authorization: Bearer header.
For full protocol initialization and tool discovery, use an MCP client. These examples show individual JSON-RPC requests.
Request parameters
Send these fields inside params. The JSON-RPC envelope is shown in the request example.
protocolVersionstringrequiredMCP protocol version supported by the client.
capabilitiesobjectrequiredClient capabilities.
clientInfoobjectrequiredEXPAND CLIENTINFO
namestringrequiredversionstringrequiredFull JSON Schema
{
"type": "object",
"properties": {
"protocolVersion": {
"type": "string",
"description": "MCP protocol version supported by the client."
},
"capabilities": {
"type": "object",
"description": "Client capabilities."
},
"clientInfo": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"version": {
"type": "string"
}
},
"required": [
"name",
"version"
]
}
},
"required": [
"protocolVersion",
"capabilities",
"clientInfo"
]
}Responses
200Successful protocol response
Inspect result.isError for tool-level failures, even when the HTTP status is 200.
202Notification accepted
MCP notifications return no JSON-RPC response body.
400Invalid request
Check the JSON-RPC envelope, parameters, and protocol version.
406Not acceptable
Accept must include application/json and text/event-stream.
429Rate limited
Wait for the Retry-After interval before making another request.
401Unauthorized
A valid, unexpired MCP bearer token is required.
403Access denied
Your connection needs access to this workspace and the requested operation.