Freee MCP Server

Model Context Protocol (MCP) server for freee API integration. The freee mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.

What it actually does

freee会計、人事労務、請求書、工数管理、販売、IT管理、サイン（電子契約）を AI Agent から操作できるようにする freee 公式の MCP サーバーと Agent Skills です。

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• freee_api_get — データ取得
• freee_api_post — 新規作成
• freee_api_put — 更新
• freee_api_delete — 削除
• freee_api_patch — 部分更新
• freee_api_list_paths — エンドポイント一覧
• Contributors — The Contributors tool exposed by this server

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the freee mcp mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Freee MCP's toolset — freee_api_get, freee_api_post, freee_api_put and 4 more — is a fair guide to whether it matches your workflow. It is maintained by him0; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Freee MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.