Workaround
If you still see the "Couldn't reach the MCP server" error, remove the existing freee MCP connector entry in Claude.ai Settings → Connectors.
The error
Couldn't reach the MCP server. You can check the server URL and verify the server is running.Reported in freee/freee-mcp issue #439: “Cannot connect to remote MCP server - "Couldn't reach the MCP server"”.
What fixed it
If you're still seeing "Couldn't reach the MCP server," please:
1. Open Claude.ai → **Settings → Connectors**.
2. **Remove** the existing freee MCP connector entry.
— a maintainer's comment on the issue.
Source and dates
| Repository | freee/freee-mcp |
|---|---|
| Issue | Cannot connect to remote MCP server - "Couldn't reach the MCP server" |
| Evidence | a maintainer's comment |
| Status | Workaround (a way around it, given in the evidence) |
| Fixed in | No version is named |
| Issue closed | 2026-06-01 |
| 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: "401 company_not_found" — 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