chekkuFor AI agents

Let your AI make the checklist. You just tap through it.

Ask Grok, Claude, ChatGPT or any agent for a list and it hands you a Chekku link. Open it on your phone, check things off, share it with whoever is helping. No accounts, no API keys, and a one-time setup that takes about a minute.

MCP endpoint

https://www.chekku.app/api/mcp

Streamable HTTP, no auth

REST API

https://www.chekku.app/api/v1

Plain JSON over HTTP

Pick your app

Each one needs the MCP URL exactly once. After that, just ask for a list.

Grok connects to custom MCP servers from its Connectors page. Three clicks, no code.

Open grok.com/connectors.
Click New Connector, then Custom.
Paste the MCP URL below. There is no authentication to set up.

MCP URL

https://www.chekku.app/api/mcp

Building on the xAI API instead

"tools": [
  { "type": "mcp", "server_url": "https://www.chekku.app/api/mcp", "server_label": "chekku" }
]

Goes in the tools array of a Responses API request.

Then try: Make me a packing list for three days in Tokyo and send me the link.

Already have a list? Just paste the link.

No setup needed for reading.

Paste any Chekku link into an AI that can read the web and it sees the list as plain text: title, progress and every item. So “what's left on this list?” works on day one, even before the AI is connected. Connecting is only needed for creating and editing.

What a connected agent can do

The tools, in the words the agent sees them.

create_checklist	Creates a new shareable checklist and returns its URL. Give that URL to the user; anyone with it can open and edit the list. Use numbering "step" for procedures and "numeric" when the user asks for numbers; never write numbers into the item text.
get_checklist	Reads a checklist by id or URL: title, progress, and every item with its id, text, checked state, note and priority.
add_items	Adds one or more items to an existing checklist, at the end by default.
check_items	Marks items done (or not done with checked=false). Items can be named by text, so "check off milk" works without knowing ids.
update_item	Changes one item: its text, a note (comment) shown under it, its priority, or its checked state.
remove_items	Deletes items from a checklist. Items can be named by id or text.
update_checklist	Renames a list or changes its emoji, numbering style, sort mode, or accent color.
reset_checklist	Unchecks every item so the list can be reused, like the app's Clear All.
delete_checklist	Permanently deletes a checklist for everyone who has its link. Confirm with the user first.

How it stays safe on an open app

Chekku was already open. The API changes nothing about who can reach what.

The link is the key. List ids are unguessable, and holding one is the only capability there is. That is the same trust model as the web app, and the same as a Google Doc set to anyone with the link.
The server holds no master credentials. API requests reach the database with the same permissions as an anonymous browser tab, so the API can never do more than the app itself allows. Lists a signed-in owner made private stay private unless the request carries that owner's own sign-in token.
Nothing is listable. There is no endpoint that enumerates lists. An agent only ever sees a list it created or was handed.
Frozen copies stay frozen. Snapshots are read-only through the API, exactly as in the app. Deleting a list requires an explicit confirm, and rate limits keep runaway loops in check.