intuit/quickbooks-online-mcp-server

A comprehensive Model Context Protocol (MCP) server for QuickBooks Online
Quick Start | Available Tools | Authentication | Documentation
## Overview
This MCP server provides complete QuickBooks Online API integration for Claude Code and other MCP-compatible clients. It includes full CRUD operations for 29 entity types and 11 financial reports, giving you comprehensive access to QuickBooks Online functionality.
### Key Features
145 Total Tools - Complete coverage of QuickBooks Online API
29 Entity Types - Full CRUD operations (Create, Read, Update, Delete, Search)
11 Financial Reports - Balance Sheet, P&L, Cash Flow, and more
OAuth 2.0 Authentication - Secure token-based authentication
TypeScript - Full type safety with Zod validation
Tested - Jest test suite with ESM support
> Note: this is a local MCP server. It runs as a stdio subprocess on the developer's or partner's machine and authenticates to a QuickBooks Online company.
> Before you start: This MCP server is easy to run once authenticated, but QuickBooks Online integration is gated by Intuit's OAuth app setup. You must register an app on the Intuit Developer Portal and complete a one-time, browser-based OAuth handshake. Sandbox supports http://localhost redirect URIs; production requires a public HTTPS callback for the initial authorization. After that initial handshake, the server runs locally without further browser interaction (until the 100-day refresh window lapses). See Authentication for full details.
## Quick Start
### Installation
bash
# Clone the repository
git clone https://github.com/your-username/mcp-quickbooks-online.git
cd mcp-quickbooks-online
# Install dependencies
npm install
# Build the project
npm run build
### Configuration
Copy the template .env.example to .env in the root directory and fill in your values:
bash
cp .env.example .env
env
QUICKBOOKSCLIENTID=yourclientid
QUICKBOOKSCLIENTSECRET=yourclientsecret
QUICKBOOKSENVIRONMENT=sandbox
QUICKBOOKSREFRESHTOKEN=yourrefreshtoken
QUICKBOOKSREALMID=yourrealmid
# Optional: restrict which tool categories are registered (default: all enabled)
# QUICKBOOKSDISABLEWRITE=true # suppress create tools
# QUICKBOOKSDISABLEUPDATE=true # suppress update tools
# QUICKBOOKSDISABLEDELETE=true # suppress delete tools
.env is gitignored so your real credentials stay local.
> Read-only or containerized installs: the server reads .env at startup and writes the rotated refresh token back to it on each refresh. When the installed module sits on a read-only filesystem (a container with a read-only root, an immutable/Nix install), set QUICKBOOKSTOKENSTOREPATH to an absolute, writable path for both operations. A per-tenant host can also point each connection at its own isolated token file this way. Three things to know: it must be set in the host process env (e.g. the env block of your MCP server config) — setting it inside .env has no effect, because the path is resolved before .env is read; it must be an absolute path (the server refuses to start otherwise); and when set, the package's own .env is not read at all, so any file-based config (including credentials) must live in the file it points to.
### Claude Code Integration