BeanHub

io.beanhub由 beanhub.io 發布官方發布者v1.0.0更新於 Oct 24, 2026

Read and update hosted Beancount books over OAuth. No CLI access token.

已驗證Streamable HTTP可網頁執行效率與工作流金融

概覽

AI 產生的概覽

BeanHub 的託管 MCP 伺服器，讓助理透過 OAuth 讀取 Beancount 帳本的科目、交易與餘額，並可選擇更新帳本。

可以做什麼
列出託管 Beancount 帳本中的帳簿、科目、分錄、檔案、表單與提交記錄，並讀取單筆分錄與檔案。搜尋交易並查看科目餘額。開啟更新後，可建立、修改與刪除分錄，重新命名科目，提交表單並更新檔案。
適用情境
當你的記帳資料存放在 BeanHub 託管的 Beancount 帳本中，並希望 AI 助理查詢交易、餘額與分錄，或在你明確允許時修改帳本時使用。
執行需求
需要 BeanHub 帳號，並在帳號的 MCP 設定中啟用 MCP，同時由 AI 應用完成 OAuth 2.0 登入（動態用戶端註冊，無需用戶端密鑰）。伺服器為遠端端點，無需本機執行環境或存取權杖。
安裝前請注意
開啟更新後，寫入工具可建立、修改與刪除帳本分錄、重新命名科目、提交表單並更新檔案；新連線預設為唯讀，除非確實需要編輯，否則請保持唯讀。應用無法變更帳單、連接銀行、公開帳本或刪除帳本。僅支援 OAuth 登入，請勿加入 Bearer 權杖或靜態用戶端密鑰。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 BeanHub，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.beanhub%2Fmcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "beanhub": {
      "type": "http",
      "url": "https://api.beanhub.io/mcp"
    }
  }
}

README

BeanHub MCP

Listing files for BeanHub's hosted MCP server. This repository is not the server source. The live endpoint is https://api.beanhub.io/mcp.

BeanHub is a hosted Beancount book on Git. An AI app signs in with OAuth, then can list accounts, search transactions, check balances, and update the ledger if you allow it. The app does not use a CLI access token. New connections start read-only.

Enable MCP on your account before you connect: https://app.beanhub.io/mcp/. Full steps: Connect an AI app with MCP.

Files

Each client looks for its own filename. They all point at the same URL.

FileUsed by
server.jsonOfficial MCP Registry (io.beanhub/mcp)
mcp.jsonCursor plugins and Agent Plugins
.mcp.jsonClaude Code plugins
plugin.jsonAgent Plugins
.cursor-plugin/plugin.jsonCursor Marketplace
.claude-plugin/plugin.jsonClaude Code plugins
.claude-plugin/marketplace.jsonClaude Code marketplace catalog
gemini-extension.jsonGemini CLI gallery

Do not paste https://app.beanhub.io/mcp/ into an AI app. That page is MCP settings, not the server.

Auth

The server uses OAuth 2.0 with dynamic client registration and token_endpoint_auth_method=none. Do not add a Bearer access token or a static client secret.

What the app can do

Read tools: list_books, list_accounts, search_transactions, get_balances, list_entries, get_entry, list_files, get_file, list_forms, list_commits.

Write tools (only if you turn on updates): create_entries, update_entry, delete_entry, rename_account, submit_form, update_files.

The app cannot mint access tokens, change billing, connect a bank, dump Connect or Inbox data, make a book public, or delete a book.

Public source

The public copy is https://github.com/LaunchPlatform/beanhub-mcp. Cursor, Claude Code, Gemini CLI, and the official registry repository.source field use that GitHub repo.

To pull Amendable updates and push GitHub:

bash
cd beanhub-mcpgit fetch origingit merge origin/mastergit push github master

For Gemini CLI gallery, add the GitHub topic gemini-cli-extension.

Official MCP Registry

This repo publishes metadata only for the hosted server https://api.beanhub.io/mcp. The registry name is io.beanhub/mcp. That namespace needs HTTP or DNS proof on beanhub.io, not GitHub OIDC. Docs: remote servers, authentication, GitHub Actions.

Do not run mcp-publisher init. It would overwrite server.json.

devenv

bash
direnv allow   # or: devenv shellmcp-validatemcp-gen-auth   # encrypts MCP_PRIVATE_KEY into secrets.sops.yaml + gitignored mcp-registry-auth

The publisher key is stored in secrets.sops.yaml, encrypted with SOPS using PGP fingerprint A57616E62A499B512EDA662E0FC8D7008588874B. Edit later with sops secrets.sops.yaml. Commit the encrypted file; do not commit key.pem.

The public proof is served from the Hugo site as static/.well-known/mcp-registry-auth. Deploy beanhub.io so https://beanhub.io/.well-known/mcp-registry-auth returns that one line. DNS alternative: TXT on the apex beanhub.io. Then:

bash
mcp-publish

mcp-publish reads MCP_PRIVATE_KEY (64 hex chars), decrypts ./secrets.sops.yaml, or falls back to ./key.pem. Default auth method is HTTP. For DNS: MCP_AUTH_METHOD=dns mcp-publish.

Without devenv:

bash
./scripts/validate-mcp.sh./scripts/gen-mcp-registry-auth.sh./scripts/publish-mcp.sh

GitHub Actions

CI runs ./scripts/validate-mcp.sh on pulls and pushes to master.

Publish to MCP Registry runs on v* tags and on workflow_dispatch. Create a GitHub Environment named mcp-registry-publish, store MCP_PRIVATE_KEY as an environment secret (not a repo secret), and restrict the environment to master and tags. Then:

bash
git tag v1.0.0git push github v1.0.0

A tag v1.0.0 publishes version 1.0.0 (the committed server.json is not rewritten). Versions are immutable. Bump the tag for later metadata-only updates.

Confirm:

bash
curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.beanhub/mcp"

Links

來源：README.md，提交 494ab90

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.0最新Sep 21, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分