Skip to main content
Glama
ortizl20

qbo-mcp

by ortizl20

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
INTUIT_ENVYesIntuit environment (e.g., sandbox or production).
QBO_DRY_RUNYesSet to '1' for dry-run mode, preventing any live submissions.
INTUIT_CLIENT_IDYesYour Intuit client ID. A placeholder value selects the fixture mode.
INTUIT_REDIRECT_URIYesOAuth redirect URI, e.g., http://localhost:8000/callback
INTUIT_CLIENT_SECRETYesYour Intuit client secret.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
qbo_oauthA

Connect OAuth. With placeholder Intuit app env this completes the recorded Acme fixture sandbox. Live mode returns an authorize URL for your own Intuit app.

qbo_read_companyA

Read the connected QuickBooks Online company profile.

qbo_list_employeesA

List employees for the connected company (Acme Bookkeeping fixture names on the prove path).

qbo_update_employee_salaryA

Update one employee's example annual salary. Confirm-screen defaults ON; pass confirm=true to apply. Never submits payroll.

qbo_payroll_statusB

Fetch payroll run status. Door 1 is always dry-run / not submitted.

qbo_payroll_previewA

Fetch dry-run payroll preview totals and write screenshot-ready markdown/html. Confirm-screen defaults ON. Never submits payroll.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct area: OAuth, company read, employee listing, salary update, payroll status, and payroll preview. The only potential confusion is qbo_payroll_status vs qbo_payroll_preview, since both concern the dry-run payroll path, but the descriptions clarify that one reports run status while the other produces preview totals and output artifacts.

Naming Consistency4/5

All tools share the qbo_ prefix and snake_case style, and most follow a verb_noun pattern (read_company, list_employees, update_employee_salary). Minor deviations exist: qbo_oauth is a bare noun and the two payroll tools are noun phrases, but the overall pattern remains predictable and readable.

Tool Count5/5

Six tools is well-scoped for a QuickBooks employee/payroll integration. Each tool earns its place, covering a step in the auth → company → employees → payroll workflow without padding or bloat.

Completeness4/5

The core workflow is covered: authenticate, read company, list employees, update salary, preview payroll, and check status. Minor gaps like employee creation/deletion, company update, and actual payroll submission are absent, but the payroll submission omission appears intentional given the repeated 'never submits payroll' notes, so agents can still complete the intended workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues