freee MCP can perform GET, POST, PUT, PATCH, and DELETE requests against supported freee APIs after OAuth authorization., Write and delete operations can create, update, or remove accounting deals, expense applications, invoices, quotations, payment requests, HR records, attendance data, project time, sales records, IT assets, and e-signature documents., The server validates API paths against OpenAPI schemas and checks company ID consistency, but users must still confirm business, accounting, payroll, and legal actions before execution., OAuth tokens, client secrets, selected company IDs, and request payloads should be protected in configs, local storage, logs, and screenshots., Use the official Remote MCP URL only; do not connect clients to unofficial endpoints that claim to be freee.
Privacy notes
Tool calls can expose company IDs, user details, accounting transactions, bank and wallet metadata, invoices, receipts, expense applications, payroll and HR records, attendance data, employee profiles, project workloads, customer and partner data, IT assets, and e-signature documents., freee receives API requests, OAuth tokens, request parameters, uploaded files, and business data according to the user's freee account, API scopes, and selected company., Local mode stores OAuth configuration and tokens on the user's machine; remote mode authenticates through freee's hosted MCP flow., Generated reports, request errors, API responses, and skill references can enter MCP client context and model logs.
Author
freee
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 3 risk areas. Review closely: credentials & tokens, network access.
3 areas
SafetyCredentials & tokensfreee MCP can perform GET, POST, PUT, PATCH, and DELETE requests against supported freee APIs after OAuth authorization.
SafetyNetwork accessWrite and delete operations can create, update, or remove accounting deals, expense applications, invoices, quotations, payment requests, HR records, attendance data, project time, sales records, IT assets, and e-signature documents.
SafetyLocal filesThe server validates API paths against OpenAPI schemas and checks company ID consistency, but users must still confirm business, accounting, payroll, and legal actions before execution.
SafetyCredentials & tokensOAuth tokens, client secrets, selected company IDs, and request payloads should be protected in configs, local storage, logs, and screenshots.
SafetyNetwork accessUse the official Remote MCP URL only; do not connect clients to unofficial endpoints that claim to be freee.
PrivacyLocal filesTool calls can expose company IDs, user details, accounting transactions, bank and wallet metadata, invoices, receipts, expense applications, payroll and HR records, attendance data, employee profiles, project workloads, customer and partner data, IT assets, and e-signature documents.
PrivacyCredentials & tokensfreee receives API requests, OAuth tokens, request parameters, uploaded files, and business data according to the user's freee account, API scopes, and selected company.
PrivacyCredentials & tokensLocal mode stores OAuth configuration and tokens on the user's machine; remote mode authenticates through freee's hosted MCP flow.
PrivacyNetwork accessGenerated reports, request errors, API responses, and skill references can enter MCP client context and model logs.
Disclosure: Apache-2.0 official freee MCP server published as the `freee-mcp` npm package, with Remote MCP support and bundled API skill references. This entry is distinct from generic billing or finance entries because it covers freee's accounting, HR, invoices, project, sales, IT management, and freee Sign APIs.
Safety notes
freee MCP can perform GET, POST, PUT, PATCH, and DELETE requests against supported freee APIs after OAuth authorization.
Write and delete operations can create, update, or remove accounting deals, expense applications, invoices, quotations, payment requests, HR records, attendance data, project time, sales records, IT assets, and e-signature documents.
The server validates API paths against OpenAPI schemas and checks company ID consistency, but users must still confirm business, accounting, payroll, and legal actions before execution.
OAuth tokens, client secrets, selected company IDs, and request payloads should be protected in configs, local storage, logs, and screenshots.
Use the official Remote MCP URL only; do not connect clients to unofficial endpoints that claim to be freee.
Privacy notes
Tool calls can expose company IDs, user details, accounting transactions, bank and wallet metadata, invoices, receipts, expense applications, payroll and HR records, attendance data, employee profiles, project workloads, customer and partner data, IT assets, and e-signature documents.
freee receives API requests, OAuth tokens, request parameters, uploaded files, and business data according to the user's freee account, API scopes, and selected company.
Local mode stores OAuth configuration and tokens on the user's machine; remote mode authenticates through freee's hosted MCP flow.
Generated reports, request errors, API responses, and skill references can enter MCP client context and model logs.
Prerequisites
A freee account and permission to access the intended company, office, or organization data.
Review of freee API scopes for accounting, HR, invoices, project management, sales, IT management, and freee Sign.
For local setup, a registered freee application with OAuth client credentials and an approved callback URL.
Review of which company ID or office should be active before allowing API calls.
Optional installation of the bundled freee API skill references and recipes for safer endpoint selection.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
20 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
Apache-2.0 official freee MCP server published as the `freee-mcp` npm package, with Remote MCP support and bundled API skill references. This entry is distinct from generic billing or finance entries because it covers freee's accounting, HR, invoices, project, sales, IT management, and freee Sign APIs.
freee MCP Server is freee's official MCP integration for AI agents. It connects
Claude and other MCP clients to freee accounting, HR, invoices, project time,
sales, IT management, and freee Sign APIs through schema-validated API tools and
OAuth-backed authentication.
Use it when a business workflow needs Claude to inspect or operate on freee
data with the official Remote MCP endpoint or a local npm server. Pair it with
the bundled freee API skill references when the assistant needs endpoint
details, parameter guidance, recipes, or troubleshooting notes.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, npm metadata, license, package metadata, MCP config, MCP tool
registration, API client, OAuth implementation, and bundled skill metadata for
current setup and operating details.
Features
Connect to freee's official Remote MCP endpoint.
Run a local stdio server through the freee-mcp npm package.
Use OAuth 2.0 with PKCE and automatic token refresh.
Inspect authentication status and clear local authentication.
List companies, switch the active company, and retrieve the current user.
Call schema-validated freee API paths through GET, POST, PUT, PATCH, and
DELETE tools.
List available API paths for supported services.
Upload files for supported local-mode workflows.
Work with freee accounting data such as deals, journals, invoices, receipts,
payments, transfers, taxes, partners, sections, and reports.
Work with freee HR records such as employees, attendance, payroll statements,
paid leave, overtime, and year-end adjustment references.
Work with invoice, project management, sales management, IT management, and
freee Sign references through the bundled skill content.
Use company ID consistency checks to reduce cross-company request mistakes.
Installation
For the official Remote MCP path, add the freee endpoint in clients that support
remote MCP connectors:
Retrieve and summarize accounting transactions, invoices, receipts, and trial
balance data.
Create or update invoices, expense applications, deals, payment requests, or
manual journals after explicit user confirmation.
Review HR attendance, employee, payroll, and leave data for an authorized
company.
Inspect project workloads, sales orders, IT assets, SaaS account records, or
freee Sign document metadata.
Use bundled recipes and references to choose API paths and parameters before
executing a business operation.
Check the active company and current user before running company-scoped API
calls.
Safety and Privacy
freee MCP can operate on sensitive business systems. Treat every write or delete
operation as a real accounting, HR, sales, IT, or e-signature action. Confirm
the active company, service, API path, request body, and intended side effects
before allowing POST, PUT, PATCH, DELETE, file upload, or e-signature calls.
The data surface includes financial transactions, invoices, payroll, employees,
attendance, customer and partner records, receipts, projects, IT assets, and
legal documents. Keep OAuth tokens and client secrets private, avoid unofficial
Remote MCP endpoints, and assume API responses can enter the MCP client and
model context.
Duplicate Notes
Existing catalog entries cover billing, payments, and finance tools. This entry
covers the official freee/freee-mcp repository and freee-mcp package for
freee's accounting, HR, invoice, project, sales, IT management, and freee Sign
API workflows.
Show that freee MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/freee-mcp-server)
How it compares
freee MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.
MCP server for Anki flashcards that lets Claude review cards, manage decks, create and update notes, handle tags and media, inspect stats, and drive Anki desktop GUI workflows.
✓freee MCP can perform GET, POST, PUT, PATCH, and DELETE requests against supported freee APIs after OAuth authorization.
Write and delete operations can create, update, or remove accounting deals, expense applications, invoices, quotations, payment requests, HR records, attendance data, project time, sales records, IT assets, and e-signature documents.
The server validates API paths against OpenAPI schemas and checks company ID consistency, but users must still confirm business, accounting, payroll, and legal actions before execution.
OAuth tokens, client secrets, selected company IDs, and request payloads should be protected in configs, local storage, logs, and screenshots.
Use the official Remote MCP URL only; do not connect clients to unofficial endpoints that claim to be freee.
✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace.
The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance.
Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent.
API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager.
Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
✓AI Game Developer can create, move, copy, modify, and delete Unity assets, scenes, GameObjects, components, scripts, packages, and generated project files.
Tools include dynamic C# script execution, C# reflection method lookup and calls, package installation/removal, Unity test execution, editor state changes, play mode control, screenshots, and profiler access.
The MCP server supports streamable HTTP and stdio; HTTP deployments should require a bearer token and stay bound to trusted interfaces.
Server variables include optional authorization and webhook settings; webhook endpoints can receive tool, prompt, resource, connection, and authorization events.
Unity runtime connections can expose compiled game state or in-game behavior to an MCP client, not just editor-only project data.
Use source control, backups, tool filtering, and explicit review before allowing destructive tools such as asset deletion, package removal, script execution, or reflection calls.
✓Anki MCP Server can create, update, delete, move, tag, rate, and sync cards and notes through AnkiConnect.
Destructive tools include note deletion, media deletion, unused-tag clearing, deck moves, tag replacement, model styling changes, and review rating actions that affect scheduling.
The server supports read-only mode that blocks exposed write actions, but users should still review tool calls before enabling unrestricted study or collection-management workflows.
Media tools can store files from local paths, URLs, or base64 data and can retrieve media as base64 content.
GUI tools can open Anki windows, select cards, edit notes, show answers, and undo the last Anki action.
Remote tunnel or ngrok-style setups expose local Anki to cloud-hosted AI clients and require careful authentication, origin, and URL-sharing controls.
Privacy notes
✓Tool calls can expose company IDs, user details, accounting transactions, bank and wallet metadata, invoices, receipts, expense applications, payroll and HR records, attendance data, employee profiles, project workloads, customer and partner data, IT assets, and e-signature documents.
freee receives API requests, OAuth tokens, request parameters, uploaded files, and business data according to the user's freee account, API scopes, and selected company.
Local mode stores OAuth configuration and tokens on the user's machine; remote mode authenticates through freee's hosted MCP flow.
Generated reports, request errors, API responses, and skill references can enter MCP client context and model logs.
✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data.
Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry.
Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base.
Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
✓Tool calls may expose Unity project paths, asset names, scene hierarchy, serialized object data, scripts, logs, screenshots, profiler metrics, test output, package metadata, and runtime state.
MCP config files and Unity plugin config can contain server URLs, connection modes, bearer tokens, authorization settings, enabled tool IDs, and cloud or local endpoint details.
Optional webhooks can receive tool, prompt, resource, connection, authorization, and token-bearing request data.
Screenshots from Game View, Scene View, cameras, or isolated GameObjects may include proprietary artwork, level design, UI, debug overlays, or unreleased game content.
Generated skills and AI-client configuration files can reveal available tools, project structure, installed packages, and local workflow assumptions.
✓Tool calls can expose deck names, note fields, card contents, tags, review history, media filenames, base64 media, selected notes, collection stats, scheduling metadata, and AnkiConnect errors.
Flashcards may contain medical, language-learning, school, work, personal, customer, or confidential study material.
Sync can send Anki collection changes to AnkiWeb according to the user's Anki account and sync settings.
Local media file paths, URLs imported into cards, and GUI-selected note IDs can enter MCP client context and model logs.
Remote tunnel providers and hosted clients may process connection metadata or traffic according to their own policies.
Prerequisites
A freee account and permission to access the intended company, office, or organization data.
Review of freee API scopes for accounting, HR, invoices, project management, sales, IT management, and freee Sign.
For local setup, a registered freee application with OAuth client credentials and an approved callback URL.
Review of which company ID or office should be active before allowing API calls.
Agentset account or self-hosted Agentset deployment with a populated namespace.
Agentset API key with access to the namespace Claude should query.
Node.js 18.17 or newer for running the `@agentset/mcp` package.
Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
Unity project using Unity 2022.3 or newer for the current package metadata.
Unity Hub or a local Unity Editor installation.
Node.js 20.19 or newer, or Node.js 22.12 or newer, for `unity-mcp-cli`.
An MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, GitHub Copilot, Cline, or another supported client.
Anki Desktop installed and running.
The AnkiConnect add-on installed in Anki.
Node.js 22.12 or newer for the npm package path.
Review of which decks, cards, tags, media files, and note types the MCP client may access.
Install
npx freee-mcp configure
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.