Spec: keep trace on mcp specification

[dugenkui03]

This issue lists some unimplemented specification features. You can use it to check if the problem you met is related to these missing capabilities. If you're interested, feel free to pick any of them and open another issue/pr to implement them.

Cancellation

Cancellation: allows client and server to terminate an in-progress request by sending a notification.

specification link: cancellation

in #321 we will discuss sending notification from server to client, including Cancellation notification.

Roots

Roots: define filesystem access boundaries that clients expose to servers, enabling controlled directory/file operations.

specification link: roots

Sampling

Sampling refers to the secure, human-reviewed process where servers request LLM-generated text/audio/image responses through clients, maintaining control over model access and permissions.

specification link: sampling

Completion on the server side

Completion in MCP enables IDE-like autocompletion for prompts and resources, providing contextual suggestions as users type.
specification link: Completion

[pottekkat]

Thank you. Complying with the spec must be the number one priority (at a reasonable pace, though). SDK sugar can come afterwards.

Anyone reading this, feel free to point out the blocking issues you have with spec compliance and maybe we can prioritize what to implement first.