Local and cloud models
Your models.
Your permissions.
Choose a cloud assistant or a local model with a compatible client. Connect your Lazy Schedule account and decide what it can read or change.
Local model processing can stay on your device, depending on your client’s setup. Lazy Schedule remains a hosted service. Cloud assistants receive shared information under their provider’s policies.
Connect your account. Choose what to share. Keep your goals moving.
ChatGPT and its logo belong to OpenAI. Claude and its logo belong to Anthropic.
Building a personal agent? See supported capabilities and Personal Agent Protocol status.
Building with a local agent? Explore the Connector developer preview or prepare your own agent. Live computer pairing is upcoming.
One connection. Your own account.
MCP is an open standard that lets an assistant use tools in another app. Start with a Lazy Schedule account and use this server address when your assistant asks for one.
MCP server URL
https://lazyschedule.com/mcpSign in with OAuth in your browser. No Lazy Schedule API key needed.
Connect in
Claude Code.
Our Claude Code plugin passed Anthropic’s review. You can install it directly from Fornaq’s marketplace.
Plugin source & installationInstall the Lazy Schedule plugin
Open Claude Code and run these commands, one at a time:
/plugin marketplace add Fornaq/claude-plugins /plugin install lazy-schedule@fornaq /reload-pluginsConnect your account
Run
/mcp, select Lazy Schedule, and authenticate. Complete the browser sign-in and select the permission categories you want to grant.Start with your goals
Ask: “Show my active goals in Lazy Schedule.” For guided setup, run
/lazy-schedule:setup.
Using Claude on the web or desktop?
The plugin instructions above are for Claude Code. On an individual Claude account, open Customize → Connectors → + → Add custom connector, enter https://lazyschedule.com/mcp, and add it. Select Connect to complete browser sign-in, then enable the connector in your chat. Team and Enterprise users need an owner to add the connector first. Availability depends on your plan and organization. Cowork has not been tested with this plugin.
Your goals.
Now in ChatGPT.
The Lazy Schedule plugin is approved and available in ChatGPT. Open the listing to get started with your existing account.
Get Lazy Schedule in ChatGPTOpen the Lazy Schedule listing
Find Lazy Schedule in ChatGPT and follow the connection steps shown there.
Sign in and choose your permissions
Use your existing Lazy Schedule account. Review which categories of information and actions you want to allow before approving the connection.
Start with a small next step
Try: “Show my active goals in Lazy Schedule,” or “I’m behind on my goal. Help me choose one small step for today.” Review any requested changes before confirming.
Availability can depend on your account and workspace settings. Manage or disconnect access in Connected apps. If sign-in stops, see connection help.
Use Ollama.
Connect with Goose.
Ollama runs your model. An MCP client such as the open-source Goose app connects it to Lazy Schedule.
Ollama + Goose guideSet up your local model
Install Ollama and Goose. Download a model that supports tool calling and keep Ollama running.
Choose Ollama in Goose
Open Settings → Configure Provider → Ollama. For a local model, use
http://localhost:11434as the API host and select your downloaded model.Add the remote MCP connection
In Goose, open Extensions → Add custom extension. Name it “Lazy Schedule,” choose Streamable HTTP, and enter this URL:
https://lazyschedule.com/mcpAdd the extension and follow the browser OAuth sign-in to choose your Lazy Schedule permissions.
Check the connection
Enable the extension in a new chat and ask: “Show my active goals in Lazy Schedule.” If authentication does not open, update your client and check that it supports remote MCP with OAuth.
This setup follows the providers’ documentation and has not yet been tested end to end with Lazy Schedule. A local model still sends authorized tool requests to Lazy Schedule’s hosted service; this is not an offline connection.
Goose extension documentationConnect your
goals to Grok.
Add Lazy Schedule as a custom MCP connector using the same server address.
Grok connector guideAdd a custom connector
Open Grok’s Connectors page and choose New Connector → Custom.
Paste the MCP link
Enter the Lazy Schedule server URL:
https://lazyschedule.com/mcpSign in and start a conversation
Complete the Lazy Schedule browser sign-in and choose your permissions. Once Grok discovers the tools, try: “Show my active goals in Lazy Schedule.”
On Grok Business and Enterprise, an administrator must first provision the connector for the team. These steps follow Grok’s documentation; the Lazy Schedule connection has not yet been tested end to end in Grok.
A next step.
Right in Slack.
Bring your personal tasks and goals into a conversation with Slackbot. Each person connects their own Lazy Schedule account and chooses what it can access.
Slack setup documentationAvailable for custom workspace setup. Connection setup and goal creation have worked in our sandbox; session renewal is still being validated. If a connection stops working, follow the recovery steps below.
Ask your workspace administrator
Your workspace needs access to Slackbot MCP and an approved Lazy Schedule app. This preview uses a custom app; there is no one-click public installation here.
Connect your own account
Open Slackbot’s app management, select LazySchedule, and connect. Finish browser sign-in with the same Lazy Schedule account you use on the website, then review the requested permissions.
Try a small request
Ask: “Show my goals in Lazy Schedule.” Review any tool approvals Slack requests. To create or change a goal, you also need the matching Lazy Schedule permission.
Administrator setup
In your Slack app’s settings, open MCP Servers. Add LazySchedule using this server URL and Dynamic Client Registration, then save and install the app in your workspace.
https://lazyschedule.com/mcpIf requested, use https://lazyschedule.com/mcp/oauth/userinfo for the identity URL and $.sub for the account identifier. Workspace installation and each person’s Lazy Schedule authorization are separate steps.
More ways to connect
Choose your assistant.
These additional connections are in preview. Explore the setup and current limits for each. A catalog entry does not connect your account or grant access.
Setup preview · Authorization pending
Perplexity Computer
Use a custom remote connector from your Perplexity account.
Setup preview · Authorization pending
Poke
Add Lazy Schedule as a custom integration in Poke.
Setup preview · Authorization pending
Town AI
Add Lazy Schedule tools to a Town routine.
Setup preview · Authorization pending
OpenClaw
Connect from the OpenClaw installation that owns your agent.
Setup preview · Authorization pending
Google Gemini
Use a custom connected app in Gemini chat or Spark.
OAuth compatibility under review
ZeroClaw
Remote MCP transport is documented; compatible browser authorization is not yet confirmed.
OAuth compatibility under review
Manus
Manus documents custom MCP servers. Lazy Schedule browser sign-in still needs compatibility testing.
Adapter needed
Carly
Carly exposes its own MCP server for other assistants to call.
Integration research needed
Saner.AI
The product is identified; a supported integration interface is not verified.
Integration research needed
Tomo AI
The product is identified; direct account linking is still being researched.
Product link needed
Muse
The official product link is still needed.
Product link needed
Slashy
The official product link is still needed.
Product link needed
Instinct
The official product link is still needed.
Product link needed
Crevio
The official product link is still needed.
Pick up where
you left off.
A sign-in or connection problem shouldn’t leave you guessing. Your tasks and goals remain in Lazy Schedule.
Review connected appsSign-in finished, but the app is not connected
Signing in identifies you; connecting also requires approving access and returning to your assistant. Finish all three steps, then check that the assistant offers Lazy Schedule tools. An installed app alone does not confirm account access.
“Invalid account-linking session” or an expired request
Close the old sign-in tab. Start a fresh connection from the assistant and finish it in the same browser, using the account shown on the permission screen. Don’t refresh or reuse an old callback URL.
“Server unreachable,” disconnected, or expired
First check your task or goal in Lazy Schedule before repeating a change: the action may have finished even if its reply was lost. If the app shows disconnected or expired in Connected apps, start a fresh connection from your assistant and review access again.
If the assistant still shows connected but requests keep failing, disconnect the affected Lazy Schedule connection there and reconnect. This does not delete your tasks or goals. A revoked connection needs a new authorization.
Connected, but an action needs approval
Your assistant may ask you to approve individual tools even after you connect. Reading, creating, updating, and deleting have separate permissions in Lazy Schedule. Grant only the access you need; if you declined a required permission, start a new connection to review your selection.
Still stuck? Contact support with the assistant name, time of the error, and the message shown. Do not send passwords, access tokens, or sign-in callback URLs.
Open standards. Open possibilities.
Open-source builders
are welcome here.
We welcome open-source assistants, local models, and community-built integrations. Our Claude plugin is MIT-licensed: inspect it, fork it, or contribute improvements. MCP gives compatible clients a shared way to connect.
Building another client? Support remote Streamable HTTP, OAuth discovery, and browser consent. Your integration uses the permissions the account owner grants and the same server access rules.
Slack setup guidance checked September 21, 2026. Slackbot remains a preview; successful setup does not guarantee every action or session renewal. ChatGPT listing updated September 29, 2026. Claude Code, Grok, and Ollama setup guidance was checked September 15, 2026.