WhyVault

Other MCP clients

What a client needs to connect to WhyVault.

Any client that supports remote MCP servers can connect to WhyVault. It needs:

  • Transport: Streamable HTTP
  • Authentication: OAuth 2.1 with authorization code and PKCE
  • Registration: Client ID Metadata Documents or Dynamic Client Registration

The metadata is at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server on the WhyVault domain. For testing, use the MCP Inspector.