Skip to main content
MCP Apps SDK Core MCP 2026-07-28 requires servers to implement server/discover. A client can call it to learn which protocol versions and capabilities a server supports before calling tools. The call is optional for clients, which can instead send a request with their preferred version and handle UnsupportedProtocolVersionError. This is the Host-to-server protocol. The MCP App View still connects to its Host with the separate ui/initialize handshake.
sunpeak’s public HTTP server wrappers currently speak core MCP 2025-11-25 through the SDK’s legacy transport. They do not implement this modern wire path. Use the legacy/modern compatibility guide before testing a sunpeak server with this request.

Send a discovery request

This request advertises that the client can display MCP App HTML. Replace the URL with a server that implements core MCP 2026-07-28:
The MCP-Protocol-Version header must match the body’s protocol version. Mcp-Method must match method. clientCapabilities is required on each modern request, while clientInfo is recommended. For the header rules on other methods, see MCP HTTP request headers.

Read the response

A modern server response has this shape. The capabilities and instructions depend on the server:
Discovery confirms that the server advertises the MCP Apps extension, but it does not tell you which tool opens a View. Next, call tools/list with the same MCP Apps client capability and inspect the UI tool’s _meta.ui.resourceUri. Then call resources/read for that exact ui:// URI and check for text/html;profile=mcp-app. See the tool and resource contract for those fields.

Handle incompatible versions

If the server returns UnsupportedProtocolVersionError (JSON-RPC code -32022), read error.data.supported and retry with a mutually supported version. A recognized modern error means the endpoint speaks the modern protocol, so do not treat that response as a signal to start a legacy handshake. A legacy-only endpoint follows the older initialize lifecycle instead. For the normative request and response fields, see the MCP server discovery specification and version negotiation rules.