Recite MCP

io.github.rivradev由 GitHub 帳號 rivradev 發布v0.1.4更新於 Oct 25, 2026

Local MCP server for Recite receipt processing with ledger and memory tools.

概覽

AI 產生的概覽

面向 Recite 收據 API 的本機 MCP 伺服器,讓助理掃描收據、管理交易與專案,並維護本機帳本與記憶。

可以做什麼
從檔案、URL、base64 或原始文字掃描收據,並提交批次掃描、查詢狀態與結果。建立、列出、更新、刪除與匯入交易、專案、分類、供應商、規則與 Webhook。產生彙總、用量報告、匯出,以及含自動比對與建議的對帳連結。將收據處理寫入本機 CSV 帳本,彙總、匯出並記錄更正。在本機記憶中保存持久的助理指令,並檢查設定與健康狀態。
適用情境
適合讓助理把收據圖片或 PDF 轉成結構化記帳資料、對帳並匯出交易,或在 Recite 雲端服務之外同時維護本機優先的帳本。
執行需求
需要本機 Python 執行環境,可透過 uvx、pipx 或 pip 安裝。處理收據需要環境變數 RECITE_API_KEY 中的 Recite API 金鑰。安裝需連線 PyPI,請求需連線 Recite API。RECITE_HOME 為選用,用於指定本機資料目錄。
安裝前請注意
伺服器需要 Recite API 金鑰(RECITE_API_KEY),該金鑰會傳送給 Recite 服務,請勿放入共用設定。許多工具會建立、更新、刪除或匯入交易、專案、分類、供應商、規則與 Webhook,匯出也會在本機寫入檔案。收據內容與交易資料會傳送給第三方 Recite API,用量可能受方案限制。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Recite MCP,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

recite-mcp

mcp-name: io.github.rivradev/recite-mcp

recite-mcp is an MCP server for the Recite API. It provides the full documented Recite MCP surface for scans, transactions, imports, batch jobs, projects, summaries, webhooks, rules, usage, and exports, while preserving the local ledger/memory workflow for agents that want local-first bookkeeping.

Install

End users

Recommended:

bash
uvx recite-mcp

Alternative (pipx):

bash
pipx install recite-mcp

Alternative (pip):

bash
python -m pip install recite-mcp

Contributors

bash
python -m pip install -e .[dev]pytest -qpython -m recite_mcp.server

Required Environment

Get an API key at https://recite.rivra.dev/settings/api (includes 30 free scans per month), then set RECITE_API_KEY (required to process receipts; server can still start without it so validate_setup() can report what's missing):

bash
# Windows PowerShell$env:RECITE_API_KEY="re_live_xxx"
bash
# macOS/Linuxexport RECITE_API_KEY="re_live_xxx"

Optional home override:

bash
# Windows PowerShell$env:RECITE_HOME="C:\path\to\recite-home"
bash
# macOS/Linuxexport RECITE_HOME="$HOME/.config/recite"

MCP Client Config

Copy-paste this config:

json
{  "mcpServers": {    "recite": {      "command": "uvx",      "args": ["recite-mcp"],      "env": {        "RECITE_API_KEY": "re_live_xxx"      }    }  }}

If installed via pipx or pip, use:

json
{  "mcpServers": {    "recite": {      "command": "recite-mcp",      "args": [],      "env": {        "RECITE_API_KEY": "re_live_xxx"      }    }  }}

Troubleshooting

MCP Registry ownership validation failed

  • Symptom: Registry publish returns a PyPI ownership/README validation error.
  • Fix: keep this exact line in packaged README: mcp-name: io.github.rivradev/recite-mcp, then bump version and upload new PyPI release before publishing to Registry.

RECITE_API_KEY missing or invalid

  • Symptom: validate_setup() reports missing_api_key or API requests are rejected.
  • Fix: set RECITE_API_KEY in MCP client env config (preferred) or shell environment.

uvx command not found

  • Symptom: terminal says uvx is not recognized.
  • Fix: install uv first, or use one of the alternatives:
    • pipx install recite-mcp
    • python -m pip install recite-mcp

recite-mcp command not found after install

  • Symptom: command not recognized after pipx/pip install.
  • Fix:
    • For pipx: run pipx ensurepath, then reopen terminal.
    • For pip: run with module entrypoint: python -m recite_mcp.server

MCP client starts but tools are unavailable

  • Symptom: server appears configured but no tools/resources are listed.
  • Fix:
    • Confirm MCP config JSON is valid.
    • Confirm command and args match your install method (uvx vs recite-mcp).
    • Restart MCP client after config changes.

Can't download from PyPI (uvx/pip)

  • Symptom: install/run fails with network/proxy errors.
  • Fix: ensure your environment can reach PyPI (or configure your proxy / custom index). If you're on a locked-down network, you may need to allowlist PyPI or use an internal mirror.

Quick local validation (no MCP client)

  • Run recite-mcp --validate (or uvx recite-mcp --validate) to print local config/health JSON. Exit code is 0 if an API key is present, otherwise 1.

Main Features

API tools (41 total):

  • Scans — scan_receipt (file, URL, base64, or raw text; ephemeral mode), get_scan
  • Transactions — create, list (with filters), get, update, delete, import_transactions (JSON list, CSV text, or CSV file)
  • Batch scans — submit_batch_scans (1–20 items, async, webhook notification), get_batch_scan_status, get_batch_scan_results
  • Projects — list, create, update, delete
  • Summaries — get_summary (period, date range, group-by)
  • Webhooks — create, list, delete (transaction.created/updated/deleted, batch.completed)
  • Reconciliation — create_reconciliation_link, list_reconciliation_links, update_reconciliation_link, delete_reconciliation_link, run_auto_match, get_reconciliation_summary, get_reconciliation_recommendations, export_reconciliation
  • Rules — create, list, update, delete (vendor_category, default_project, processing_preference)
  • Categories — get_categories (17 built-in + custom), create_category, delete_category
  • Vendors — get_vendors, create_vendor, delete_vendor
  • Usage — get_usage (period, breakdown)
  • Exports — export_transactions (CSV/JSON, optional file save)

Local tools:

  • process_receipt — scan + ledger append in one step (optional rename, dry-run, category hint)
  • process_receipts_batch — scan a directory of images/PDFs (recursive, dry-run preview)
  • summarize_ledger, export_ledger, add_ledger_correction — local CSV ledger management
  • update_memory, list_memory — persistent agent instruction storage
  • get_config, validate_setup — configuration inspection and health check

Resources: recite://ledger, recite://memory, recite://health

Documentation

  • User guide: docs/user_guide.md

來源:README.md,提交 92436d3

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.4最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

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

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

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

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

    請在儲存庫或註冊中心條目中宣告授權條款。