mcp.schema.request

A request from the server to sample an LLM via the client. The client has full discretion over which model to select. The client should also inform the user before beginning sampling, to allow them to inspect the request (human in the loop) and decide whether to approve it.

Used by the client to get a prompt provided by the server.

This request is sent from the client to the server when it first connects, asking it to begin initialization.

Sent from the server to request a list of root URIs from the client. Roots allow servers to ask for specific directories or files to operate on. A common example for roots is providing a set of repositories or directories a server should operate on.

This request is typically used when the server needs to understand the file system structure or access specific locations that the client has permission to read from.

Sent from the client to request a list of tools the server has.

A ping, issued by either the server or the client, to check that the other party is still alive. The receiver must promptly respond, or else may be disconnected.

A request from the client to the server, to enable or adjust logging.

Sent from the client to request resources/updated notifications from the server whenever a particular resource changes.

Sent from the client to request cancellation of resources/updated notifications from the server. This should follow a previous resources/subscribe request.