Summary

This project provides a Model Context Protocol (MCP) server enabling AI assistants to access and manipulate QuickBooks Online (QBO) data. It targets developers building AI applications, offering a standardized interface to QBO's extensive features, thereby simplifying data integration and automation.

How It Works

The server acts as a bridge, translating MCP requests into QuickBooks Online API calls. It exposes QBO functionalities, including full CRUD operations for 29 entity types and 11 financial reports, as callable tools. Built with TypeScript and Zod for type safety, this approach abstracts the complexity of the QBO API, allowing AI models to interact with financial data programmatically and efficiently.

Quick Start & Requirements

Installation involves cloning the repository, running npm install, and npm run build. Key prerequisites include Node.js and npm. Configuration requires setting up an application on the Intuit Developer Portal to obtain OAuth 2.0 credentials (Client ID, Client Secret) and a Refresh Token. Environment variables (.env file) must be populated with these credentials and the Realm ID. The npm run auth command initiates the OAuth handshake. For production, redirect URIs must be publicly accessible, often requiring tools like ngrok or a deployed callback handler.

Highlighted Details

• Exposes 144 distinct tools for QuickBooks Online operations.
• Provides complete CRUD capabilities for 29 entity types (e.g., Customers, Invoices, Bills).
• Offers access to 11 core financial reports, including Balance Sheet, P&L, and Cash Flow.
• Boasts 100% code coverage across 396 unit tests, ensuring high quality.
• Features full type safety through TypeScript and Zod validation.

Maintenance & Community

The provided README does not contain specific details regarding notable contributors, community channels (like Discord or Slack), or a public roadmap.

Licensing & Compatibility

The project is released under the MIT License. This permissive license generally allows for commercial use and integration into closed-source applications without significant restrictions.

Limitations & Caveats

This is strictly a local MCP server, designed to run as a stdio subprocess on a developer's machine. Production deployment requires workarounds for Intuit's redirect URI restrictions, necessitating either tunneling services like ngrok or a dedicated public callback endpoint for the initial OAuth authentication flow.