freee
by freee
Query and post accounting, payroll and invoicing data across freee's Japanese cloud business suite from your AI assistant. 13 tools, four of which are generic write proxies over roughly 490 freee API operations. OAuth 2.0 sign-in, permissions inherited from your freee login.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect freee via MCP
https://mcp.freee.co.jp/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect freee once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman Studiofreee Tools & Capabilities (13)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Beta, with no warranty. freee states the feature is provided as a beta version and disclaims any guarantee of completeness, accuracy, availability, usefulness, security or non-infringement of third-party rights, noting it may be updated at any time (freee, 2026).
- Outside freee's support service. freee states that external integrations using the MCP server fall outside the scope of its support, because they involve information and tools freee cannot handle. Bugs go to the repository's GitHub issues instead.
- The remote server does not cover freee Sign. freee's repository states Remote MCP support for its electronic-signature product is in preparation and only local operation is supported.
- Remote may lag the open-source version. freee aims for parity but states some operations may be unavailable remotely due to limits in the MCP specification.
- Some products need their own contract, client and permissions. freee's repository states that surveys, business registration, HR evaluation and tax filing each require the corresponding connection environment, OAuth client, contract plan and user permissions.
- No draft or confirmation stage is documented between an agent's decision to write and the request reaching freee.
- Responsibility for the AI tool is the customer's. freee states it is not involved in the selection, management or operation of the AI tool, and instructs customers to confirm that training opt-out is enabled in that tool.
- Documentation is Japanese only, which is a real barrier for an English-speaking finance team evaluating this connector.
- Rate limits are a known unknown. We observed
ratelimit-limit: 6000with a 60-second window on the MCP endpoint itself on 2026-09-09, but that governs our unauthenticated request. freee's public API documentation index does not state the limits that apply to authenticated freee API calls made through the connector, and we did not find them. - Tool safety is name-derived, not annotated. We hold no live safety annotations for any of the 13 tools.
Frequently asked questions
It can. The freee connector exposes generic write verbs rather than named accounting actions, so whether a call drafts or commits depends entirely on which freee API path the agent chooses. freee's documentation describes creating invoices and registering data conversationally and documents no connector-level draft stage, preview or confirmation prompt. Treat any write instruction as immediate (freee, 2026).
Exactly the permissions of the freee user who signed in, and no more. freee's help centre states that operations are possible only within the same scope as the logged-in user's permissions, and that actions beyond those permissions, such as retrieving data the user cannot view, will not occur. freee describes this as the same security standard as existing Public API applications (2026).
Yes. freee's help centre states the Agent Skills package must be installed so the AI uses freee correctly, and warns that without it correctly configured the connector may consume a large number of tokens. freee-mcp offers many operations, and the skill injects the API reference the agent needs rather than loading everything (freee, 2026).
freee publishes it as a beta. Its disclaimer states the feature is provided as a beta version with no warranty as to completeness, accuracy, availability, usefulness, security or non-infringement, and that it may be updated at any time. freee also places MCP-based external integrations outside the scope of its support service (2026).
Hosting. freee states the open-source version requires you to build a development environment on your own computer and complete several configuration steps, while the remote version is hosted by freee so you only add a URL. freee aims for functional parity but notes some operations may be unavailable remotely due to MCP specification limits (2026).
No. freee publishes its connector setup guide, FAQ and disclaimer in Japanese only, at support.freee.co.jp, and the open-source repository README is also Japanese. The Anthropic directory listing carries an English description, but every vendor-authored detail on this page was read from Japanese sources and translated (checked 2026-09-09).
Not yet. freee's repository states that Remote MCP support for freee Sign is in preparation and that only running the MCP server locally is supported, through a separate freee-sign-mcp command with its own tools. The remote endpoint documented on this page therefore does not cover contract signing (freee, 2026).
The request carried a company_id that is not the currently selected business. freee's repository states that when a request includes company_id in a parameter or body it must match the current business, and a mismatch returns an error. Check the current business with freee_get_current_company and change it with freee_set_current_company (2026).
Sources
- freee help centre, "freee-mcp（リモート版）を設定して利用する" (Setting up and using freee-mcp, remote version) (fetched 2026-09-09 via the Zendesk Help Center API route,
/api/v2/help_center/ja/articles/56390747520537.json, HTTP 200; the HTML route at the same id is bot-walled). Published in Japanese; all quotation here is our translation. Source of the eight business areas, both setup paths, the four-question FAQ, the mandatory Agent Skills step, and the compliance and disclaimer section. freee's article metadata gives a last-edited date of 2026-08-28. · retrieved 2026-09-09 - freee-mcp open-source repository README (fetched 2026-09-09, HTTP 200, 21,599 bytes, Japanese). Source of the 15-tool table with its stdio-only annotations, the roughly 490-operation count, the twelve product APIs, the OpenAPI path validation, the
company_idmatching rule, the freee Sign remote-support status, the per-product contract requirements, and the plugin install commands. Apache-2.0 licensed. · retrieved 2026-09-09 - freee-mcp releases (fetched 2026-09-09). Latest tag
v0.35.1, published 2026-09-08, shippingfreee-api-skill.zip. Corroborates that the skill package is a released artefact rather than a documentation aspiration. · retrieved 2026-09-09 freee-mcpon npm (fetched 2026-09-09). Version 0.35.1, licence Apache-2.0. · retrieved 2026-09-09- freee developer documentation index (fetched 2026-09-09, HTTP 200). Confirms the per-product API references exist; cited here to record that it does not publish the rate limits or plan gates for authenticated API calls, which is why those remain unknown on this page.
developer.freee.co.jp/robots.txtcarries an emptyDisallow:— all paths permitted. · retrieved 2026-09-09 - Live OAuth posture check against
https://mcp.freee.co.jp/mcp(2026-09-09). Anonymousinitializereturned HTTP 401 withWWW-Authenticate: Bearer error="invalid_token"and an RFC 9728resource_metadatapointer. That descriptor returned HTTP 200 declaring resource name "freee MCP Server" and scopesmcp:readandmcp:write; the authorization server metadata declares authorization code grant with PKCE S256 and dynamic client registration. A syntactically valid but invented bearer token was then sent to bothinitializeandtools/list, and both returned HTTP 401 "Malformed token" — a real auth boundary, not an open server. An invented sibling path under/.well-known/oauth-protected-resource/returned 404, confirming the descriptor is bound to this endpoint rather than being a pattern echo. No credentials were supplied and no tool was called. · retrieved 2026-09-09 - Anthropic Connectors Directory entry (snapshot fetched 2026-09-08, re-read 2026-09-09; the 13 tool names, the partner tier, the endpoint and the productivity category). · retrieved 2026-09-08
- Checked and found not relevant: freee help centre article 59725750174617, "対応アプリ・対応アク ションの一覧" (fetched 2026-09-09, HTTP 200, 17,273 characters). It is freee IT管理's catalogue of managed SaaS applications and contains zero mentions of MCP. Article 59397210099993, "Claude Enterpriseとの連携を追加する" (fetched 2026-09-09, HTTP 200), documents provisioning Claude Enterprise seats from freee IT管理 over SCIM — the opposite integration direction, and not this connector. · retrieved 2026-09-09
Server Info
- Category
- Productivity
- Developer
- freee
- Tools
- 13
- Domain
- mcp.freee.co.jp
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Productivity
Related Resources
Ready to connect freee?
Connect freee once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.