Workaround
Installing freee-api-skill with `npx skills add freee/freee-mcp -g` lets the AI agent call the API correctly.
The error
401 company_not_foundReported in freee/freee-mcp issue #479: “Invoice API requires company_id but the tool schema does not indicate this to AI assistants”.
What fixed it
`npx skills add freee/freee-mcp -g` で freee-api-skill をインストールしたところ、AI Agent が自動的にスキルを発動し、レシピ（`recipes/invoice-operations.md`）から `company_id` 必須の情報を取得して、正しく API を呼び出せることを確認しました。
— the reporter's confirmation on the issue (Japanese, quoted as written).
Source and dates
| Repository | freee/freee-mcp |
|---|---|
| Issue | Invoice API requires company_id but the tool schema does not indicate this to AI assistants |
| Evidence | the reporter's confirmation |
| Status | Workaround (a way around it, given in the evidence) |
| Fixed in | No version is named |
| Issue closed | 2026-06-04 |
| Read from GitHub | 2026-11-07 |
| Approved by a person | 2026-11-07 |
This page records what the vendor's own GitHub repository says. The error text, the issue title and the quote are copied as written; the summary at the top is one sentence limited to the quote, and a person approved this fact on 2026-11-07. KanseiLink has not re-run the fix. Read the issue before applying it. Something changed? Write to contact@synapse-arrows.com.
For AI agents
The same fact is returned as issue_facts by lookup({ service_id: 'freee' }) on the KanseiLink MCP server (https://mcp.kansei-link.com/mcp), next to the other checked facts for freee. Connection guide: freee service page.
Other freee MCP errors
- freee MCP: "Couldn't reach the MCP server. You can check the server URL and verify the server is…" — the fix from the official GitHub issue
- freee MCP: "401 Unauthorized" — the fix from the official GitHub issue
- freee MCP: "MCP error -32602: Input validation error: Invalid arguments for tool freee_api_put: [" — fixed in v0.26.4
- freee MCP: "Starting OAuth flow..." — the fix from the official GitHub issue