Glento Now Speaks MCP: Connect It to Your AI Assistant
When we opened up the Glento API, we said an assistant connection was coming so you could ask what is urgent without leaving the conversation you were already in.
That is live today. Glento is now an MCP server. Point an assistant at one address, sign in once, and your matrix is something it can read and act on.
What an assistant can do with it
Six things, which are the same six things you can do yourself.
- See what is on your plate, filtered by quadrant or by status.
- Read a single task, notes and all.
- Add one, with a quadrant, priority, tags, notes, a due date and a start date.
- Change one, including moving it between quadrants.
- Complete one.
- Delete one.
What that turns into in practice is less mechanical than the list sounds. "What is in Do First this week." "Take everything I just said and file it, urgent ones first." "Close out the three things I finished this morning." The assistant does the sorting and the typing. You keep the judgment calls.
It is a Pro feature, for the same reason the API is: an assistant reads the synced copy of your tasks, and syncing is what Pro pays for. Without sync your tasks only ever exist on your device, which is the default and the point. What you get on each plan has the breakdown.
Which assistants
Anything that speaks MCP over HTTP, which by now is most of them. Setup steps for each are on the integrations page:
- Claude, web and desktop, and Claude Code
- Cursor
- ChatGPT, in developer mode
- VS Code, Windsurf and Zed
- Gemini CLI
- OpenClaw and Hermes Agent
If yours is not on that list and it supports remote MCP servers, it will still work. Give it the address, and it will discover what Glento can do on its own. That is the part of MCP worth caring about: nobody has to build a Glento plugin for every assistant, including assistants that do not exist yet.
Connecting
There is one address and no API key.
You paste the address into your assistant, it sends you to Glento, you sign in and approve, and you are done. You see exactly what is being asked for before anything is granted, and the connection stops the moment you remove it in the assistant. There is no long-lived secret sitting in a config file with the keys to your account.
Per-assistant instructions, including the exact command or config line where one exists, are on the integrations page.
Two things to know
Days carry a timezone. A due date is a day in your life, not a moment on a clock, so anything setting a due date or a start date has to say which timezone that day belongs to. Assistants handle this without being told, but it is why a task lands on the day you meant rather than the day a server happened to be having.
Repeating tasks are handled carefully. An assistant can read and edit a repeating task like any other, but it will not change the repeat itself or complete a task that belongs to a series. A half-applied change to a recurring series is worse than one you make in the app yourself.
What has not changed
Glento still works offline, still stores your tasks on your device first, and still does not require an account to use the core app. An assistant sees your tasks because you connected it and for as long as you leave it connected. Nothing here changes what happens if you do not.
If you would rather not talk to a computer about it
The same six operations are available through Zapier, currently in open beta, for wiring Glento to email, forms and calendars without an assistant in the middle. And they are available as a plain REST API if you would rather write the code yourself.
Connected something interesting, or hit something that did not work? Tell us. The list of what gets built next is mostly written by people who wrote in.
