How to Connect Money Forward Cloud MCP to an AI Agent
Auth setup
Easiest: https://beta.mcp.developers.biz.moneyforward.com/mcp/ca/v3 (Remote MCP available to all plans since March 2026). Manual: register at developer.moneyforward.com, get client_id/secret.
Key facts
| Base URL | https://accounting.moneyforward.com/api/v3/ |
| API version | v3 |
| Auth | OAuth 2.0 Authorization Code flow. Register app at MF Developer Portal. Or use official MCP server: https://beta.mcp.developers.biz.moneyforward.com/mcp/ca/v3 (handles auth). |
| Token URL | https://accounting.moneyforward.com/oauth/token |
| Scopes | mfc/accounting/read,mfc/accounting/write |
| Request body | application/json |
| Pagination | page-based: 'page' and 'per_page' params (max 100). Response includes total_count and total_pages. |
| Rate limit | 300 requests/5 minutes per token. HTTP 429 with Retry-After. |
| Error format | JSON: {"error_messages":["..."],"errors":{"field":["message"]}} |
Key endpoints
| Method | Path | Description |
GET | /offices | List offices (事業所) — get office_id first |
GET | /journals | List journal entries (仕訳) |
POST | /journals | Create journal entry |
GET | /deal_categories | List account items for deals |
GET | /trial_balance | Get trial balance (試算表) |
Quickstart
GET /api/v3/offices HTTP/1.1
Host: accounting.moneyforward.com
Authorization: Bearer {access_token}
Response: {"offices":[{"id":123,"display_name":"テスト事務所"}]}
Agent pitfalls & tips
- office_id is required for most endpoints — always call GET /offices first (same pattern as freee's company_id).
- Journal entries (仕訳): debit/credit sides must balance. Use deal_categories to get valid account item IDs.
- AI categorization: POST /auto_journal_entries for automatic ML-powered expense categorization.
- Amount fields are integers in JPY, no decimals.
- MCP server (March 2026) supports all plans — Remote MCP is the easiest integration path.
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-07-06. Specs change — verify against the official docs before production use.
Frequently Asked Questions
What is Money Forward Cloud MCP's AEO score?
▼
Money Forward Cloud MCP has an AEO score of 1.00 and is rated AAA (Best-in-class agent integration). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Money Forward Cloud MCP AI-agent-ready?
▼
Money Forward Cloud MCP is currently ✓ verified for AI agent use. It offers an official MCP (Model Context Protocol) server, which means AI agents can connect directly. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Money Forward Cloud MCP compare to other Accounting & Finance services?
▼
In the Accounting & Finance category, Money Forward Cloud MCP is rated AAA. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Money Forward Cloud MCP compares.
How can I integrate Money Forward Cloud MCP with an AI agent?
▼
The fastest way to integrate Money Forward Cloud MCP with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Money Forward Cloud MCP?
▼
OAuth 2.0 Authorization Code flow. Register app at MF Developer Portal. Or use official MCP server: https://beta.mcp.developers.biz.moneyforward.com/mcp/ca/v3 (handles auth). Setup: Easiest: https://beta.mcp.developers.biz.moneyforward.com/mcp/ca/v3 (Remote MCP available to all plans since March 2026). Manual: register at developer.moneyforward.com, get client_id/secret.
What are Money Forward Cloud MCP's API rate limits?
▼
300 requests/5 minutes per token. HTTP 429 with Retry-After.