ai.logistify/quickbooks-desktop

Logistify for QuickBooks Desktop

Is the Logistify for QuickBooks Desktop MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.

Read QuickBooks Desktop data; after your yes, create sales orders and approve PO dates and payments

needs auth probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error": "invalid_token", "error_description": "Authentication required"}

Endpoint: https://mcp.logistify.ai/quickbooks-desktop/mcp (streamable-http)
Host: mcp.logistify.ai
Getting access: OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.logistify.ai/quickbooks-desktop/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server merciful-editorial-0626.customers.stytch.com, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:jwt-bearer.
Scopes quickbooks.read quickbooks.write offline_access.
Read from the server's public OAuth metadata, without a token. Method.
Website: https://logistify.ai/plugins/quickbooks-desktop/
Registry: active, updated 2026-11-13 · registry entry

More servers

Other registry entries on mcp.logistify.ai.

Servers that mention quickbooks.

DeepLedger: QuickBooks, Xero & Bill.com MCP for ChatGPT & Claude ai.deepledger/mcp · needs auth
PipeLedger ai.pipeledger/pipeledger · needs auth
RoboSystems ai.robosystems/robosystems · needs auth
com.accountingqb/accountingqb · needs auth
Caribooks (QuickBooks Online) com.caribooks/quickbooks · needs auth
QuickBooks Connector by Meridian com.pilot.meridian/qbo-connector · needs auth
Quickbooks io.github.pipeworx-io/quickbooks · alive
Paidnice com.paidnice/mcp · needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.