What can I do with this?
Ask Claude or ChatGPT about company spend, subscriptions, invoices and runway through Husk’s MCP server.
Husk API
Ask Claude or ChatGPT about company spend, subscriptions, invoices and runway through Husk’s MCP server.
Find your starting point
Your appHusk API
Husk APIWhat credentials do I need?
Authentication and permission requirements have not been reviewed here. Check the provider documentation for the required keys, OAuth scopes and account access before sending a request.
Check provider documentation ↗Can I test without an account?
Account-free API calls have not been verified for this profile. You can inspect specifications and prepare requests in the explorer without running them.
Requests run only when you choose to send them. Browser access depends on the provider’s CORS policy.
MCP implementations
- Husk MCP · Official
Ask questions about Husk spend, subscriptions, invoices, burn rate, AI spend and missing receipts in plain language, answered from live Husk data.
Husk: connection requirements
- Transport
- Streamable HTTP
- Authentication
- 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.
- Server URL
https://api.usehusk.com/mcp
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.
Documentation reviewed · Connection not runtime-tested.
Publisher evidence applies to the linked implementation. It does not establish endpoint health or access to every API operation.
Integration details
This profile contains a reviewed summary. Pricing, rate limits, authentication requirements, and SDK availability should be checked in the provider documentation before implementation. The linked provider documentation describes MCP support.
Frequently asked questions
What is Husk?
Ask Claude or ChatGPT about company spend, subscriptions, invoices and runway through Husk’s MCP server.
Where can I find Husk provider documentation?
Use the linked Husk provider documentation to check setup and supported capabilities.
Read documentationWhat does the official Husk MCP implementation support?
Ask questions about Husk spend, subscriptions, invoices, burn rate, AI spend and missing receipts in plain language, answered from live Husk data. Supported operations are limited to those exposed by this implementation. Publisher evidence reviewed 2026-11-06. This review does not establish a working connection.
View publisher evidenceHow do I connect to Husk MCP?
Streamable HTTP. 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. 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. Documentation reviewed 2026-11-06; not runtime-tested.
Read connection instructionsHow current is this Husk profile?
API Tracker summarizes available catalog information. Missing fields mean we have not established those details; they do not mean a feature is unsupported. Confirm current requirements with the provider.
Read our methodologyShare this listing For your docs, website, or community
Help developers discover this integration
Share the profile or add a listing badge to your website. Sharing is optional and does not affect placement or verification.
Add to your website
Listed on API Tracker ↗A directory listing, not a certification or Official MCP badge.