Qbo Multicompany MCP

Name: Qbo Multicompany MCP
Author: dkaleganov

作者：dkaleganovバージョン 0.1.1i★ –iパソコンで動く

レジストリ名io.github.dkaleganov/qbo-multicompany-mcp

インストール

概要

作者による説明（英語の原文）

Unofficial read-only MCP server for several QuickBooks Online company files in one AI session.

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

利用者の声iレビューはまだありませんレビューは今後のステップで、アカウント機能と一緒に始まります
私たちの基本チェックi1項目中1項目に合格公開情報からチェック。コードはまだスキャンしていません
利用状況iとても新しい↓ 118/週 · ★ –

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

接続方法: パソコンで動く
トランスポート: stdio
カテゴリ: 会計・財務・税務
入力が必要なもの：QBO_CLIENT_SECRET, QBO_TOKEN_KEY

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

基本チェック：1項目中1項目に合格
あなたのパソコンで、あなたのユーザーと同じ権限（ファイル、ネットワーク、アプリ）で動きます。
自分で入力するもの： QBO_CLIENT_ID, QBO_CLIENT_SECRET, QBO_ENV, QBO_TOKEN_KEY_SOURCE, QBO_TOKEN_KEY, QBO_TOKEN_STORE, QBO_ALLOW_DOCUMENTS, QBO_ATTACHMENT_HOSTS

「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。

必要なもの

PyPIPythonのuvのインストール（uvxコマンドに必要）

どのアプリを使っていますか？

ClaudeClaude CodeCursorVS CodeChatGPT

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます

{
  "mcpServers": {
    "qbo-multicompany": {
      "command": "uvx",
      "args": [
        "qbo-multicompany-mcp",
        "--entities",
        "your-value"
      ],
      "env": {
        "QBO_CLIENT_ID": "your-value",
        "QBO_CLIENT_SECRET": "your-value",
        "QBO_ENV": "your-value",
        "QBO_TOKEN_KEY_SOURCE": "your-value",
        "QBO_TOKEN_KEY": "your-value",
        "QBO_TOKEN_STORE": "your-value",
        "QBO_ALLOW_DOCUMENTS": "your-value",
        "QBO_ATTACHMENT_HOSTS": "your-value"
      }
    }
  }
}

ターミナルでこれを実行します

claude mcp add qbo-multicompany --env QBO_CLIENT_ID=your-value --env QBO_CLIENT_SECRET=your-value --env QBO_ENV=your-value --env QBO_TOKEN_KEY_SOURCE=your-value --env QBO_TOKEN_KEY=your-value --env QBO_TOKEN_STORE=your-value --env QBO_ALLOW_DOCUMENTS=your-value --env QBO_ATTACHMENT_HOSTS=your-value -- uvx qbo-multicompany-mcp --entities your-value

動かす前に、空欄の値を入力してください。

このサーバーは起動コマンドに値を入れる必要があるので、設定をコピーして入力してください。

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "qbo-multicompany": {
      "command": "uvx",
      "args": [
        "qbo-multicompany-mcp",
        "--entities",
        "your-value"
      ],
      "env": {
        "QBO_CLIENT_ID": "your-value",
        "QBO_CLIENT_SECRET": "your-value",
        "QBO_ENV": "your-value",
        "QBO_TOKEN_KEY_SOURCE": "your-value",
        "QBO_TOKEN_KEY": "your-value",
        "QBO_TOKEN_STORE": "your-value",
        "QBO_ALLOW_DOCUMENTS": "your-value",
        "QBO_ATTACHMENT_HOSTS": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

このサーバーは起動コマンドに値を入れる必要があるので、設定をコピーして入力してください。

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "qbo-multicompany": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "qbo-multicompany-mcp",
        "--entities",
        "your-value"
      ],
      "env": {
        "QBO_CLIENT_ID": "your-value",
        "QBO_CLIENT_SECRET": "your-value",
        "QBO_ENV": "your-value",
        "QBO_TOKEN_KEY_SOURCE": "your-value",
        "QBO_TOKEN_KEY": "your-value",
        "QBO_TOKEN_STORE": "your-value",
        "QBO_ALLOW_DOCUMENTS": "your-value",
        "QBO_ATTACHMENT_HOSTS": "your-value"
      }
    }
  }
}

これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

QBO_CLIENT_ID env
Client ID of your own Intuit app, here or in the --env-file file. A value set here, even a blank one, overrides --env-file.
QBO_CLIENT_SECRET 秘密 env
Client Secret of your own Intuit app, here or in the --env-file file. A value set here, even a blank one, overrides --env-file.
QBO_ENV env
sandbox or production; sandbox when unset. A value set here, even a blank one, overrides --env-file.
QBO_TOKEN_KEY_SOURCE env
Where the token store key lives: keychain (the default, macOS only) or env (QBO_TOKEN_KEY). A value set here, even a blank one, overrides --env-file.
QBO_TOKEN_KEY 秘密 env
The store key when QBO_TOKEN_KEY_SOURCE=env: 32 bytes as 44 characters of base64 or 64 of hex. A value set here, even a blank one, overrides --env-file.
QBO_TOKEN_STORE env
Token store directory. Defaults to $XDG_STATE_HOME/qbo-multicompany-mcp, else ~/.local/state/qbo-multicompany-mcp. A git working copy or a cloud-sync folder is refused. A value set here, even a blank…
QBO_ALLOW_DOCUMENTS env
Set to 1 to register get_attachment, which fetches nothing until QBO_ATTACHMENT_HOSTS pins a host. Off by default. A value set here, even a blank one, overrides --env-file.
QBO_ATTACHMENT_HOSTS env
Comma-separated storage hosts attachment downloads may contact. Empty refuses every download. A value set here, even a blank one, overrides --env-file.

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月10日にチェック

✓ 合格
作者とリポジトリが一致
レジストリ名は、リポジトリを所有するGitHubアカウント dkaleganov で確認済みです
… 未チェック
今もメンテナンスされている
このリポジトリはまだGitHubから読み取っていません
… 未チェック
ライセンスがある
このリポジトリはまだGitHubから読み取っていません
– 対象外
エンドポイントが応答する
これはパソコンで動くため、インターネット上のエンドポイントはありません
– 対象外
OAuthでサインイン
パソコンで動き、代わりにローカルの設定を使います
… 未チェック
ツールの説明に隠れた指示がない
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです

会計・財務・税務のほかのサーバーとの比較i

このカテゴリのほかの3051件のうち0%よりスターが多い
このカテゴリのほかの3051件のうち84%より最近レジストリに公開
基本チェックの結果が、このカテゴリのほかの3051件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Qbo Multicompany MCPは安全ですか？

当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか？

入力が必要なもの：QBO_CLIENT_SECRET, QBO_TOKEN_KEY

パソコンで動きますか、それともクラウドですか？

あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません（サーバー自体がオンラインサービスを呼び出す場合を除きます）。

今もメンテナンスされていますか？

GitHubリポジトリの最終更新は–、最新バージョン（0.1.1）がレジストリに届いたのは4 日前です。

どのアプリで使えますか？

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにPython (uv)も必要です。

代わりに使えるものは？

同じカテゴリには：Finance Toolkit, SolidInvoice, Korea Tax Calculator

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：↓ 週あたりのダウンロードi★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

Finance Toolkit

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

作者：JerBouma広く使われている↓ 1.6万/週★ 5496今日更新

パソコンでもクラウドでも

インストール

SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

作者：SolidInvoice成長中★ 981今日更新

クラウドで動く✓ solidinvoice.co

インストール

Korea Tax Calculator

Korean tax calculation and tax-audit judgment MCP: 97 tools with statutory citations.

作者：UpstageAI成長中↓ 3172/週★ 97昨日更新

パソコンで動く

インストール

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

qbo-multicompany-mcp

A read-only MCP server that serves several QuickBooks Online company files to one AI session over stdio. Every call to QuickBooks names its company through an explicit entity key. There's no default company and no matching on company name.

Unofficial. Not affiliated with or endorsed by Intuit. Each user registers their own Intuit app and

answers Intuit's questions for themselves.

Who it's for

You run or keep books for more than one QuickBooks company and want an assistant to read across them without mixing them up: close the month, compare companies, trace a transaction, cross-check vendor payments.
You build tools for AI agents and want a worked example of an MCP server designed around how a model actually behaves.

Other QuickBooks MCP servers exist, some from Intuit, and some serve several companies or write to the books. Compare them against what you need. This one never writes.

AI client  -- stdio -->  qbo-multicompany-mcp  -- GET, checked before send -->  QuickBooks Online

| +-- entities.yaml your companies, by key +-- encrypted store one token chain per company

Quickstart on sandbox

You need Python 3.11+, uv, and an Intuit developer app with http://localhost:8765/callback registered as a development redirect URI.

git clone https://github.com/dkaleganov/qbo-multicompany-mcp.git

cd qbo-multicompany-mcp && uv sync --frozen && cp entities.example.yaml entities.yaml && cp .env.example .env && chmod 600 .env entities.yaml

Put your app's Client ID and Client Secret in .env, and your sandbox companies in entities.yaml. Then create the store key and connect each company in a browser:

uv run qbo-multicompany-mcp-auth --env-file .env --entities entities.yaml init-key

uv run qbo-multicompany-mcp-auth --env-file .env --entities entities.yaml connect acme_main

A first connect usually reports a name mismatch: answer y and copy the printed display_name into entities.yaml. Then add the server to your client with absolute paths. --scope user makes it available to every Claude Code session on your account, so you can run those sessions outside the repo folder:

claude mcp add --scope user qbo -- "<repo>/.venv/bin/qbo-multicompany-mcp" --env-file "<repo>/.env" --entities "<repo>/entities.yaml"

docs/getting-started.md walks through every step, including Claude Desktop and Codex. Production needs more: docs/production.md.

From PyPI, without a clone

uvx runs the published package. Save .env.example as .env and entities.example.yaml as entities.yaml in a private folder, chmod 600 both, and fill them in as above. With standing for that folder's absolute path:

uvx --from qbo-multicompany-mcp@0.1.1 qbo-multicompany-mcp-auth --env-file "<dir>/.env" --entities "<dir>/entities.yaml" init-key

uvx --from qbo-multicompany-mcp@0.1.1 qbo-multicompany-mcp-auth --env-file "<dir>/.env" --entities "<dir>/entities.yaml" connect acme_main

claude mcp add --scope user qbo -- uvx qbo-multicompany-mcp@0.1.1 --env-file "<dir>/.env" --entities "<dir>/entities.yaml"

Tools

Eighteen by default, and one opt-in. docs/tools.md has every parameter and a "Choosing a tool" table.

Tool	Returns
`list_entities`	Configured companies, auth state and token freshness. Makes no request
`server_info`	Build, environment, read-only status, store protection. Makes no request
`get_company_info`	Company profile, settings and derived capabilities
`list_accounts`	Chart of accounts with balances
`list_vendors`	Vendors, the 1099 flag, and whether a tax id is on file, never the id
`list_customers`	Customers with their balances, and no tax ids, notes or contact fields
`list_reference_data`	Classes, departments, items, terms, payment methods, tax codes, tax rates
`list_transactions`	Transactions in a window of up to six months
`get_transaction`	One transaction with its lines
`run_query`	One parsed `SELECT`, rebuilt from its parse tree and sent by `GET`
`list_changes`	Changes and deletions within 30 days, on list objects such as vendors and accounts, with no transactions
`summarize_vendor_payments`	Per-vendor candidate totals for a calendar year
`report_profit_and_loss`	Income and expense by section
`report_balance_sheet`	Balances as of a date
`report_general_ledger`	Postings by account
`report_aging`	Open payables or receivables by bucket
`run_report`	The other 21 documented reports
`list_attachments`	Attachment metadata, never a link
`get_attachment` (opt-in)	The file, only with `--allow-documents` and a pinned storage host

What makes it work well with AI agents

A model will call the wrong company, trust an empty result, and retry a bad value. The server is built around that.

An explicit company on every call. With no default, a model has to name the company each time, so a wrong choice shows in the transcript. list_entities gives the keys, and a guard checks the company's name on first use in each process.
Results name their company and age. Every answer from QuickBooks carries the entity, environment, the last four digits of the realm id (Intuit's Company ID), and when it was fetched, so a model can say which file a number came from.
One list vocabulary. Every list that walks QuickBooks's pages returns count, rows, truncated, duplicates_dropped and pages_walked, so a model learns the shape once.
Partial reports say so first. A problem in a cell or a row makes the result partial, and the text a model reads opens with PARTIAL RESULT. An empty report never establishes that there's no data, and list_transactions re-checks a filtered request with zero rows, unfiltered, before it reports "none".
Refusals name the fix and never echo a value. A refusal names the parameter and the reason, usually before any request, and no text, id, date or number you sent comes back; it can name a configured entity key or one of this server's own option values. A test sends a marked value through every parameter of every tool and finds it repeated in no refusal.
Company text is flagged as untrusted. Names, memos and report cells can carry anything. Every tool that returns them says in its description that they're untrusted input to the model and that the data can reach its provider.
Sign-in stays with a person. Consent happens in a terminal and a browser, secrets come from the environment, and no tool takes a secret or an authorization code or returns one. Anything running as you can read a plain .env and the token store's key, from any folder. Keeping AI sessions out of the repo folder keeps .env and entities.yaml out of an agent's working folder; an agent with a shell can still reach both, and the key, as SECURITY.md explains.
Descriptions route. Every tool's description says when another fits better, and the "Choosing a tool" table in docs/tools.md covers the whole surface for people.

Read-only, and how that's enforced

Intuit offers no read-only accounting scope: the one scope covers reads and writes alike. So read-only lives in this code. Every request is inspected as a fully built httpx.Request immediately before it's sent, and accounting requests may only be GETs to an allowlisted path on the exact bound company. OAuth calls go only to Intuit's fixed endpoints, the opt-in attachment download goes only to a host you pin, and everything else is denied. docs/design.md has the policy, and how walks, reports and the token store behave.

How it's verified

Tests. uv sync --frozen --extra dev, then uv run pytest -q: 2,805 pass and 4 skip, with no credentials and no network. That count needs git 2.32 or later and gitleaks on your PATH; without gitleaks 25 more skip.
Mutation gate. A passing suite doesn't prove a safety behaviour is protected, so scripts/mutation_gate.py has 480 entries that each delete one and require its tests to fail. It has controls of its own, so it can't quietly pass by testing nothing.
Leak checks. Custom gitleaks rules for Intuit credentials, each proven to fire on a canary, plus scripts/scrub_check.py for identifier-shaped values.
Live runs. Every tool has run over stdio in sandbox: the default tools on this release, and get_attachment on a pre-release build. Every default tool ran on production, read-only, on 2026-09-28 with a pre-release build, apart from TaxSummary under run_report, which has never returned rows. What the live runs found is in docs/api-findings.md.

CHANGELOG.md separates what was verified live from what has only run on fixtures.

Example prompts

Which companies can you see, and is each one connected?

Compare profit and loss for acme_main and acme_ops, this fiscal year-to-date against last. Say where each

number came from.

Show the balance sheet for acme_ops as of the end of last quarter, then the journal entries behind any

account that moved by more than 10%.

Which vendors in acme_ops carry the 1099 flag?

Give me candidate vendor payments for acme_main for 2025, and what needs review.

Known limits

Read only, and QuickBooks Online only. There are no writes, and no QuickBooks Desktop.
Transactions have their own tools. On transaction types run_query answers COUNT(*) and refuses SELECT *, and list_changes refuses them too. Use list_transactions and get_transaction.
Filters validate differently. An unknown parameter name is discarded upstream, a bad enum value is a 400, and an id or text that matches nothing is an empty 200. This server handles each, and docs/design.md explains how.
Vendor payment totals are candidates. They're a cross-check against a bank ledger, not a filing classifier, and they haven't been reconciled by hand against one.
Sandbox isn't production. A value confirmed in sandbox may not hold on a production company.
Some columns are unobserved. Class, department and currency report columns are documented, but no live response has shown them.
`get_attachment` is only proven in sandbox. Production's storage host hasn't been observed, and the host check is a pre-check, not a binding to the address con

冒頭だけを表示しています。続きはリポジトリで読めます

Qbo Multicompany MCP

概要

PopNx MCPの3つの柱

できること

インストール

インストールの前に

自分で入力する値

できること

基本チェックi

作者とリポジトリが一致

今もメンテナンスされている

ライセンスがある

エンドポイントが応答する

OAuthでサインイン

ツールの説明に隠れた指示がない

会計・財務・税務のほかのサーバーとの比較i

よくある質問

代わりの候補

Finance Toolkit

SolidInvoice

Korea Tax Calculator

作者のREADME

qbo-multicompany-mcp

Who it's for

Quickstart on sandbox

From PyPI, without a clone

Tools

What makes it work well with AI agents

Read-only, and how that's enforced

How it's verified

Example prompts

Known limits