This is the single endpoint for all Model Context Protocol (MCP) interactions, which follow the JSON-RPC 2.0 specification.
The specific action to be performed is determined by the method property within the JSON request body. The params object structure varies depending on the method being called.
Below are the supported methods:
initialize: Establishes a connection and negotiates protocol versions.ping: A simple method to check if the connection is alive.tools/list: Retrieves a list of available tools that an AI agent can execute.tools/call: Executes a specific tool with the provided arguments.resources/list: Retrieves a list of available knowledge resources.resources/read: Reads the content of a specific resource.prompts/list: Retrieves a list of available, pre-defined prompts.prompts/get: Retrieves the full message structure for a specific prompt, populated with arguments.Authentication is performed via an OAuth 2.0 Bearer Token. The token should be included in the Authorization header.
A standard JSON-RPC 2.0 request object. The params will vary based on the method.
Specifies the version of the JSON-RPC protocol. MUST be "2.0".
"2.0"
A string containing the name of the method to be invoked.
"tools/list"
A unique identifier established by the client. The server MUST reply with the same value in the response.
"request-id-12345"
A structured value that holds the parameter values to be used during the invocation of the method. The structure of this object is method-dependent.
{ "limit": 20, "cursor": "abc-123" }
A standard JSON-RPC 2.0 success response. The structure of the result object depends on the method called in the request.
Specifies the version of the JSON-RPC protocol.
"2.0"
The value returned by the invoked method. Its structure is determined by the specific method that was called.
The identifier from the corresponding request.
"request-id-12345"