freee-mcp

freee-mcp is an MCP server plus “Agent Skills” for automating freee accounting, HR/payroll, invoicing, time/attendance management, and sales via an AI agent. It supports OAuth 2.0 with PKCE, provides tools for authentication and company (事業所) switching, and validates request paths/parameters against an OpenAPI schema before calling the freee APIs.

Evaluated Mar 30, 2026 (21d ago)
Homepage ↗ Repo ↗ Automation mcp freee oauth pkce agent-skills accounting hr invoicing time-management sales typescript
⚙ Agent Friendliness
68
/ 100
Can an agent use this?
🔒 Security
70
/ 100
Is it safe for agents?
⚡ Reliability
36
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
85
Documentation
75
Error Messages
0
Auth Simplicity
70
Rate Limits
40

🔒 Security

TLS Enforcement
80
Auth Strength
85
Scope Granularity
45
Dep. Hygiene
65
Secret Handling
70

Uses OAuth 2.0 + PKCE and mentions request validation against an OpenAPI schema; also uses helmet and rate-limit middleware per manifest dependencies. Specific practices for secret storage/log redaction and exact scope granularity are not detailed in the provided README, so scores reflect partial visibility.

⚡ Reliability

Uptime/SLA
0
Version Stability
60
Breaking Changes
40
Error Recovery
45
AF Security Reliability

Best When

You want a model/agent to safely call freee APIs with enforced request validation, using the remote MCP endpoint or a local MCP process, and you can provide OAuth credentials.

Avoid When

You cannot manage OAuth consent/credentials or you need webhooks or push-based event handling (not indicated here).

Use Cases

  • Enable an AI agent to fetch and operate freee data (e.g., deals, invoices, expenses) using MCP tools
  • Create/preview records (e.g., invoices, expenses) by referencing prior data for consistency
  • Support multi-site (事業所) workflows with dynamic company switching
  • Build agent workflows that require structured API calling and schema-validated requests

Not For

  • Direct human manual usage without an agent/MCP client
  • Use-cases needing real-time notifications/webhooks from freee-mcp
  • Use-cases requiring a conventional public REST API/SDK for your application code (the primary interface is MCP + skills)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: OAuth 2.0 + PKCE (interactive configure / freee_authenticate tool) Token auto refresh (as described)
OAuth: Yes Scopes: No

Authentication is described as OAuth 2.0 + PKCE with a configure wizard and tools like freee_authenticate/freee_auth_status/freee_clear_auth. The README does not enumerate specific OAuth scopes in detail.

Pricing

Free tier: No
Requires CC: No

No pricing information is provided in the supplied content; this appears to be an open-source integration layer.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • For operations that include company_id: you must ensure the company_id matches the currently selected 事業所; mismatches trigger errors.
  • Some tools are stdio-only (freee_authenticate/freee_file_upload), so the MCP client integration must support that transport.
  • Remote MCP URL is provided as the official endpoint; using a different URL is explicitly warned against.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for freee-mcp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered