This is a Model Context Protocol (MCP) server implementation for QuickBooks Online integration, using HTTP transport with OAuth 2.1 Device Authorization Grant.
Add the following to your MCP client configuration (e.g., ~/.factory/mcp.json):
{
"mcpServers": {
"quickbooks": {
"type": "http",
"url": "https://qbo-mcp.lcsnetworks.com/mcp",
"disabled": false
}
}
}The QuickBooks MCP server uses OAuth 2.1 for authentication. To connect:
- Click the "Authorize" button provided by the MCP server in your AI assistant interface
- Complete QuickBooks login - You'll be redirected to QuickBooks to sign in with your credentials
- Grant permissions - Approve the requested scopes for the app
- Automatic token setup - After successful authorization, the server will store your tokens and you'll receive a 30-day access token
The OAuth flow is handled entirely through the HTTP interface - no local server or additional setup required on your machine.
- Access tokens are valid for approximately 30 days
- Refresh tokens are used to obtain new access tokens automatically
- The server handles token refresh transparently in the background
- If you see "QuickBooks not connected" errors, simply repeat the authorization process
After authentication is complete, you can use the MCP server to interact with QuickBooks Online. The server provides various tools for managing customers, estimates, bills, and more.
The server provides Create, Delete, Get, Search, and Update tools for the following entities:
- Account
- Bill Payment
- Bill
- Customer
- Employee
- Estimate
- Invoice
- Item
- Journal Entry
- Purchase
- Vendor
If you see an error message like "QuickBooks not connected", make sure to:
- Complete the OAuth authorization flow (click "Authorize" button)
- Verify that your QuickBooks credentials are correct
- Check that your tokens are still valid (access tokens expire after ~30 days)