Skip to main content
Glama
qbo-multicompany-mcp

qbo-multicompany-mcp

Related Servers

Alternatives to qbo-multicompany-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables agents to operate QuickBooks Online for a bookkeeping tenant, including company profile, employee listing, salary updates, and dry-run payroll previews without submitting actual pay.
      6
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to securely access and query QuickBooks Online accounting data through natural language, translating requests into structured queries and returning results for analysis, reporting, and financial workflows.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that provides AI assistants with secure access to multiple QuickBooks Online company files through a single connection, featuring a company registry, OAuth-based authorization, and comprehensive read/write tools.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read and analyze consolidated financial data across banks, cards, payments, accounting, payroll, and equity sources. Provides tightly controlled, read-only access so AI can answer finance questions without moving money.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read a company's accounting data — customers, vendors, items, accounts, invoices, estimates, payments, bills, purchases, journal entries, time activities, attachments and financial reports — through the QuickBooks Online Accounting API v3. On explicit request it can also create, update and void records, email invoices and upload attachments, using per-request OAuth headers for stateless, multi-tenant operation.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves 142 QuickBooks Online tools over remote HTTPS with OAuth sign-in and an email allowlist, enabling authorized AI assistant users to access one company from anywhere. Administrators can connect the company and control write, update, and delete permissions.
      MIT

    TDQS

    A4.1/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a distinct resource (entities, accounts, vendors, customers, transactions, attachments) or a distinct report family, and the descriptions explicitly cross-reference each other to route the agent (e.g. report_profit_and_loss vs report_balance_sheet vs report_general_ledger, get_transaction vs list_transactions). The main residual overlap is run_query, which can serve Account/Vendor/Customer/Class rows that list_accounts, list_vendors, list_customers and list_reference_data already cover, and run_report sitting alongside the four named report tools; the descriptions disambiguate both, so misselection is possible but unlikely.

    Naming Consistency4/5

    The dominant patterns are verb_noun (list_*, get_*, run_query, run_report, summarize_vendor_payments) plus a clean report_* family for the special-case report readers, all snake_case. Deviations are minor: report_* uses a noun prefix instead of a verb, and server_info is the one name with no action verb, but each family is internally consistent and readable.

    Tool Count4/5

    18 tools is above the ideal band but justified: the server covers an entity/token layer, six resource listers, transaction row+detail, change tracking, attachments, and a report layer split into four named reports plus one catch-all for 21 lesser reports. No tool looks redundant, and the grouping of rare QuickBooks reports under run_report keeps the count down rather than inflating it.

    Completeness4/5

    For a read-only surface the lifecycle coverage is strong: entity discovery, company settings, reference data, chart of accounts, parties, transactions with drill-down, aging/GL/P&L/balance sheet plus 21 auxiliary reports, change feed and attachment metadata. Gaps remain: no single-record getters for vendor, customer or account, no employee or journal-entry listing (transaction entities are COUNT-only through run_query), and the descriptions reference get_attachment as conditionally enabled, which is a potential dead end for an agent following the guidance.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues