mf-accounting-voucher-mcp

A local MCP server that complements features not supported by the official MCP server for マネーフォワード クラウド会計. It calls the REST API v3 directly and is used alongside the official MCP (remote).

Provided Tools

Note: Marking linked details as "excluded" is not available in the REST API, so this is not provided. Downloading voucher files is likewise not supported by the API. Features already provided by the official MCP (such as getJournals) are not reimplemented.

Voucher file binaries do not pass through the LLM. This server (a Node process) receives a local file path, reads it, base64-encodes it, and sends it to the API.

Related MCP server: freee-chat-mcp-server

Setup

1. Register an app in the App Portal

Create an app in the マネーフォワード App Portal and configure the following.

• Redirect URI: http://127.0.0.1:53682/callback

• Scopes:

  • mfc/accounting/voucher.write (registering and deleting vouchers)

  • mfc/accounting/journal.write (registering, updating, and deleting journal entries)

Note down the issued client ID / client secret.

2. Installation and build

pnpm install && pnpm run build

3. Environment variable configuration

export MF_CLIENT_ID="（クライアントID）"
export MF_CLIENT_SECRET="（クライアントシークレット）"

4. Initial authorization

pnpm run auth

A browser opens, so log in to マネーフォワード and authorize. The token is saved to ~/.mf-accounting-voucher-mcp/tokens.json (mode 600) and is automatically refreshed thereafter.

Registering with Claude Desktop / Cowork

Once registered, the MCP server starts automatically when the client launches. No manual startup is needed in daily use.

Recommended: Using the keychain (without writing secrets to the config file)

Only on the first run, register the credentials in the macOS keychain:

security add-generic-password -s mf-accounting-voucher-mcp -a client_id -w '（クライアントID）' -U
security add-generic-password -s mf-accounting-voucher-mcp -a client_secret -w '（クライアントシークレット）' -U

Register the startup script in mcpServers in claude_desktop_config.json (replace the path with your actual installation location):

{
  "mcpServers": {
    "mf-accounting-voucher-mcp": {
      "command": "/path/to/mf-accounting-voucher-mcp/scripts/mf-accounting-voucher-mcp.sh",
      "args": []
    }
  }
}

The initial OAuth authorization can also be run via the script (no environment variable configuration needed):

scripts/mf-accounting-voucher-mcp.sh auth

Alternative: Writing environment variables directly in the config file

{
  "mcpServers": {
    "mf-accounting-voucher-mcp": {
      "command": "node",
      "args": ["/path/to/mf-accounting-voucher-mcp/dist/index.js"],
      "env": {
        "MF_CLIENT_ID": "（クライアントID）",
        "MF_CLIENT_SECRET": "（クライアントシークレット）"
      }
    }
  }
}

Note that with this method, secrets remain in plain text in the config file.

Usage example

「この領収書（/Users/xxx/Downloads/receipt.pdf）を仕訳 XXXX に添付して」
→ post_vouchers が呼ばれ、添付結果（voucher_file_ids）が返る

「仕訳 XXXX の証憑 a60cd25d-... の添付を解除して」
→ delete_voucher

「仕訳 XXXX を削除して」
→ delete_journal（実行前に仕訳内容の提示と明示的な確認が入る）

The attachment result can be verified by retrieving the target journal entry with the official MCP's getJournalById and confirming it is reflected in voucher_file_ids.

Notes

• For the exact MF limits on file type, size, and count, refer to the official specification /specs/vouchers (this server's limits are a local safety valve)

• Switching business entities (offices) is done by re-running pnpm run auth

• delete_journal cannot be undone. The caller (LLM) is designed to obtain explicit user confirmation before executing