Husk connection settings

Host setup required

Connect an MCP client to https://api.usehusk.com/mcp over Streamable HTTP. The endpoint advertises OAuth (authorization code with PKCE S256, dynamic client registration at https://api.usehusk.com/mcp/register, scope openid). The token endpoint accepts only client_secret_post and client_secret_basic, so clients must use the client secret issued at registration; public clients without a secret are not supported. Husk documents an alternative flow: in Husk go to Settings > Integrations > MCP Server, click Generate Token and copy the server URL and access key into the client. Tokens inherit the permissions of the Husk user who generates them, so create shared-client tokens from a viewer. Revoked tokens stop working immediately. Publisher documentation and the endpoint OAuth metadata were reviewed on November 6, 2026; tool list and account access have not been runtime-tested.

Publisher setup documentation →

Source-declared authentication: oauth2. Publisher affiliation and successful connection are not inferred.