Connect Husk
Ask questions about Husk spend, subscriptions, invoices, burn rate, AI spend and missing receipts in plain language, answered from live Husk data.
Setup evidence reviewed 2026-11-06. Documentation review does not establish a successful connection.
Credentials and permissions
OAuth authorization code with PKCE S256 and dynamic client registration (scope openid), advertised in the endpoint metadata. The Husk docs also describe generating a URL and access key under Settings > Integrations > MCP Server. Tokens inherit the permissions of the Husk user who creates them.
Set up your connection
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.
Server endpoint
https://api.usehusk.com/mcpTransport: Streamable HTTP
Publisher documentation
Check these sources for current account requirements and client support before connecting.