Setup preview · Authorization pending
Town AI
Add Lazy Schedule tools to a Town routine.
Before you start
Town’s exact OAuth callback must be accepted by the authorization service. Saving a server does not confirm a working connection.
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.
- In Town, open Settings → MCP → Add Server.
- Name the server Lazy Schedule and enter the URL below. Follow Town’s browser authorization flow.
- After signing in, enable the server only for the routine that needs its tools.
Lazy Schedule MCP address
https://lazyschedule.com/mcpUse 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 connectionsIf 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.