OAuth compatibility under review
Manus
Manus documents custom MCP servers. Lazy Schedule browser sign-in still needs compatibility testing.
Before you start
The documented setup includes credential fields; it does not establish the OAuth flow we need. No API key or pasted session-token workaround is offered.
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.
Lazy Schedule MCP address
https://lazyschedule.com/mcpUse OAuth browser sign-in. This address contains no credentials and copying it does not grant access. Keep setup on hold until a compatible OAuth flow is confirmed.
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.