Workaround
To keep a headless environment, continue using the stdio version (npx freee-mcp).
The error
Starting OAuth flow...Reported in freee/freee-mcp issue #329: “opencodeからremote-mcp使えるようにしてください。”.
What fixed it
ヘッドレス環境を維持したい場合は、引き続きstdio版(npx freee-mcp)を利用してもらうのが早いと思います。
— a maintainer's comment on the issue (Japanese, quoted as written).
Source and dates
| Repository | freee/freee-mcp |
|---|---|
| Issue | opencodeからremote-mcp使えるようにしてください。 |
| Evidence | a maintainer's comment |
| Status | Workaround (a way around it, given in the evidence) |
| Fixed in | No version is named |
| Issue closed | 2026-03-31 |
| 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
lookup({ service_id: 'freee' }) on the KanseiLink MCP server (https://mcp.kansei-link.com/mcp) returns only the newest few fixes for freee as issue_facts; this one is not among them and is published on this page. Connection guide: freee service page.
Other freee MCP errors
- freee MCP: "401 company_not_found" — the fix from the official GitHub issue
- 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