프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Qbo Multicompany MCP

제작자: 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의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 내 컴퓨터에서 실행
  • 전송 방식: 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 명령어용)

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

  • 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월 9일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 dkaleganov 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • – 해당 없음

    엔드포인트 응답

    내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요

  • – 해당 없음

    OAuth로 로그인

    내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

회계, 재무 및 세금 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 2960개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 2960개 중 87%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 2960개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Qbo Multicompany MCP, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: QBO_CLIENT_SECRET, QBO_TOKEN_KEY

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.1)은 3일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Finance Toolkit, SolidInvoice, Korea Tax Calculator

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Finance Toolkit

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

제작자: JerBouma널리 사용됨↓ 1.6만/주★ 5.5천그저께 업데이트

컴퓨터 또는 클라우드

SolidInvoice

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

제작자: SolidInvoice성장 중★ 98110일 전 업데이트

클라우드에서 실행✓ solidinvoice.co

Korea Tax Calculator

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

제작자: UpstageAI성장 중↓ 3.2천/주★ 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.

ToolReturns
list_entitiesConfigured companies, auth state and token freshness. Makes no request
server_infoBuild, environment, read-only status, store protection. Makes no request
get_company_infoCompany profile, settings and derived capabilities
list_accountsChart of accounts with balances
list_vendorsVendors, the 1099 flag, and whether a tax id is on file, never the id
list_customersCustomers with their balances, and no tax ids, notes or contact fields
list_reference_dataClasses, departments, items, terms, payment methods, tax codes, tax rates
list_transactionsTransactions in a window of up to six months
get_transactionOne transaction with its lines
run_queryOne parsed SELECT, rebuilt from its parse tree and sent by GET
list_changesChanges and deletions within 30 days, on list objects such as vendors and accounts, with no transactions
summarize_vendor_paymentsPer-vendor candidate totals for a calendar year
report_profit_and_lossIncome and expense by section
report_balance_sheetBalances as of a date
report_general_ledgerPostings by account
report_agingOpen payables or receivables by bucket
run_reportThe other 21 documented reports
list_attachmentsAttachment 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

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기