All assistants

Setup preview · Authorization pending

Google Gemini

Use a custom connected app in Gemini chat or Spark.

Before you start

Google requires a personal account, age 18+, US availability, English, and Keep Activity enabled. Exact callback compatibility and Lazy Schedule authorization still need verification.

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. On the Gemini website, open Settings → Connected Apps (or Personal Intelligence → Connected Apps).
  2. Under Custom apps, add the Lazy Schedule MCP URL below and select Next.
  3. Follow the browser authorization instructions. After connecting, use @ to select the app in a prompt. Do not paste a session token into advanced credential fields.
Open Google Gemini setup

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.

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.

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.