Configure one endpoint. Start from your agent.

What this generator does

The generator formats the public Working Machines remote MCP endpoint for the configuration shape expected by the selected client. It does not test authorization, create an account, choose a provider connection, or grant permission to run an action. Those decisions remain in the client and the Working Machines consent flow.

A direct visit to the MCP URL can return a missing authorization header error. That is expected for a protected protocol endpoint. Add the configuration to a compatible client and start its MCP login flow so OAuth discovery, browser consent, and token exchange happen in the intended order.

Before the first action

• Confirm that the client shows the expected Working Machines endpoint and account.
• Use discovery to find the smallest relevant action set instead of loading an entire catalog into context.
• Inspect the action schema and select the intended named provider connection.
• Request confirmation before financial, destructive, externally visible, or difficult-to-reverse work.
• Count work as completed only after the provider returns a successful structured result.