WORKING MACHINES TROUBLESHOOTING
Claude Code cannot find an MCP server
Claude Code does not show Working Machines in its MCP server list or cannot access it from the project or user scope where the server was expected.
Likely causes
- The server was added in a different configuration scope.
- The remote HTTP transport or URL was entered incorrectly.
- The current project does not load the expected MCP configuration.
- Authorization has not completed for the active user environment.
Check first
- List configured MCP servers from the same Claude Code environment.
- Check whether the server belongs to local, project, or user scope.
- Confirm the endpoint is the hosted HTTPS /mcp URL.
- Review the client output for a transport or OAuth discovery error.
Resolution
- 01Add Working Machines again in the intended Claude Code scope.
- 02Use the remote HTTP transport supported by the current Claude Code version.
- 03Restart the active session so it reloads MCP configuration.
- 04Complete authorization and begin with a read-only discovery request.
Verify the fix
- Working Machines appears in the active server list.
- The client can inspect its advertised tools.
- A provider write is not attempted until the connection identity is confirmed.
What to include in a support report
Record the client name and version, the MCP endpoint hostname, the time of the failed attempt, and the exact error text. Include the affected provider and action when relevant, but remove authorization headers, cookies, OAuth codes, API keys, and provider data. This evidence distinguishes configuration, authorization, connection, and provider-permission failures without exposing credentials.