WORKING MACHINES TROUBLESHOOTING
MCP error: missing authorization header
Opening a protected remote MCP URL directly in a browser returns a JSON-RPC error saying that the authorization header is missing. This normally means the protocol endpoint is reachable but the request did not come from an authorized MCP client.
Likely causes
- The MCP URL was opened as a normal web page.
- The client has not completed OAuth authorization.
- A saved access token expired or is bound to a different resource.
- The client configuration points to the protocol endpoint but never initiated login.
Check first
- Confirm the server URL is https://app.workingmachines.dev/mcp.
- Confirm the client supports remote Streamable HTTP MCP servers.
- Remove stale credentials for this server before retrying authorization.
- Start authorization from the MCP client rather than the browser address bar.
Resolution
- 01Add the Working Machines endpoint to the MCP client.
- 02Run the client connection or login command.
- 03Complete the Working Machines sign-in and consent screen in the browser.
- 04Return to the client and list or search the available tools.
Verify the fix
- The client reports the server as connected.
- Tool discovery returns a structured response.
- No bearer token or provider credential appears in the client configuration URL.
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.