All assistants

Setup preview · Authorization pending

OpenClaw

Connect from the OpenClaw installation that owns your agent.

Before you start

Installed-version OAuth and callback compatibility need testing. A successful sign-in is separate from working tools or background task dispatch.

No live Lazy Schedule connection has been verified for this provider yet. Additional-provider authorization is awaiting an MCP backend update; setup may stop at sign-in until its exact callback is supported.

Start in your assistant.

Your assistant starts the authorization request. It then sends you to Lazy Schedule to sign in and choose permissions, before returning you to the assistant.

  1. In OpenClaw Settings → MCP, add a Streamable HTTP server named lazyschedule with the address below.
  2. Configure OAuth for this server and use Sign in. If the UI cannot sign in, run the login command on the installation that owns this connector.
  3. After authorization, probe the server before using it with a task.

Lazy Schedule MCP address

https://lazyschedule.com/mcp

Use OAuth browser sign-in. This address contains no credentials and copying it does not grant access.

openclaw mcp login lazyschedule
openclaw mcp doctor lazyschedule --probe

Choose access. Check the connection.

Use your existing Lazy Schedule account. Start with read access to tasks or goals; enable changes only if you want them. Permissions approved here apply to categories of data, not one selected goal.

Return to your assistant and ask “Show my active goals in Lazy Schedule.” Compare its answer with your goals, then review the connection and granted permissions below.

Review actual account connections

If OAuth fails or the callback is rejected, start a fresh request or contact support with the provider name and error text. Never send passwords, tokens, or callback URLs. Do not substitute a browser session token.

Official provider documentationConnection help

Connecting allows the assistant to call permitted Lazy Schedule tools. It does not let Lazy Schedule wake that assistant or dispatch autonomous work to it. Application names are not proof of provider identity.