PROTOCOL REFERENCE

Understand what your client exchanges.

MCP separates the transport, the resources made available by a server and the tools a client can invoke.

A remote connection

Streamable HTTP carries MCP messages over HTTP. Use a compatible client to handle protocol compatibility and message exchange; opening the connector URL in a browser is not a connection test.

MCP: transport overview

Resources and tools are different

MCP operation	Purpose
resources/list	Discover resources exposed by the server.
resources/read	Read a resource using its returned URI.
tools/list	Discover tools and their input schemas.
tools/call	Invoke a discovered tool with its expected arguments.

Availability depends on the capabilities declared by the server. These are protocol operation names, not a guaranteed list of MyVaultDesk-specific tools. Use discovery in your client to see what your connection exposes.

MCP: resources MCP: tools

Use returned identifiers

Illustrative operation parameters — not a complete wire request

{
  "method": "resources/read",
  "params": {
    "uri": "<URI_RETURNED_BY_THE_SERVER>"
  }
}

JSON

Replace the placeholder with the URI returned by resource discovery. Let your MCP client supply the envelope and protocol metadata required by the negotiated revision.