About UnRemind.me
UnRemind.me is a remote reminder service for people who want tasks to appear when their situation fits, rather than at a fixed time. It also lets AI agents handle delegated tasks with scoped permissions and reviewable audit logs.
Key features
- 01Reminders matched to context tags
- 02Delegate tasks to AI agents
- 03Scoped agent permissions and audit logs
- 04Four prompts for planning and resuming work
Use cases
- 01Find tasks suited to current time and equipment
- 02Plan a day around due work and calendar conflicts
- 03Turn text into a tagged reminder
MCP support
Exposes 16 tools and four prompts at https://unremind.me/mcp over Streamable HTTP. Access uses bearer tokens, with per-agent permissions and audit logs.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://unremind.me/mcp?src=mcp-registryclaude mcp add --transport http esfih-unremind-me https://unremind.me/mcp?src=mcp-registry{"mcpServers":{"esfih-unremind-me":{"type":"http","url":"https://unremind.me/mcp?src=mcp-registry"}}}Open in Cursor{"servers":{"esfih-unremind-me":{"type":"http","url":"https://unremind.me/mcp?src=mcp-registry"}}}Open in VS Code{"mcpServers":{"esfih-unremind-me":{"type":"http","url":"https://unremind.me/mcp?src=mcp-registry"}}}{"mcpServers":{"esfih-unremind-me":{"serverUrl":"https://unremind.me/mcp?src=mcp-registry"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://unremind.me/mcp?src=mcp-registryAuth requiredTools
Details
From the project READMEUnRemind.me MCP Server
Remote MCP server for UnRemind.me — context-aware reminders that surface when your situation matches, instead of firing at a fixed time.
An "Unreminder" carries context tags — where you are, what device you have, whether you're online, who's around, how much time and energy you have — and surfaces when your current context matches. Tasks can also be delegated to AI agents, each with scoped access rights and an audit log the owner reviews.
Endpoint · https://unremind.me/mcp
Transport · Streamable HTTP (JSON-RPC 2.0) · Auth · Bearer token ·
Tools · 16 · Prompts · 4
Connect
- Install UnRemind.me (Android or the web app) and sign in.
- In the app: Settings → AI agents → MCP access → Create token. The token is shown once.
- Add the server to your MCP client:
{
"mcpServers": {
"unremind": {
"type": "streamable-http",
"url": "https://unremind.me/mcp",
"headers": { "Authorization": "Bearer unr_YOUR_TOKEN" }
}
}
}
Verified with Claude and ChatGPT custom connectors (desktop and mobile). Full walkthrough: https://unremind.me/mcp/
Each token is a separate agent in the app, with its own access rights, its own audit log, and an optional expiry. Revoke any of them from the same screen without affecting the others.
Tools
See TOOLS.md for all 16 with descriptions. Every tool carries
MCP behavioural annotations (readOnlyHint, destructiveHint,
idempotentHint, openWorldHint) so a client knows which are safe to call
without confirming and which must not be blindly retried.
Prompts
Four user-invocable prompts, available from your MCP client's prompt menu:
| Prompt | |
|---|---|
| What can I do right now? | Give it your available minutes and what you have with you; it finds the tasks that actually fit |
| Plan my day | Reviews overdue/due-soon work and checks real calendar conflicts before proposing times |
| Capture this as an Unreminder | Turns raw text into a well-tagged task |
| Resume where I left off | For an agent starting a session: orient, then continue instead of starting cold |
Where to start
orient is the one to call first — it returns who the user is, how they want
to be worked with, what you were last doing, and what needs attention. One
call instead of guessing.
Discovery documents
| Capability manifest | https://unremind.me/.well-known/ai-capabilities.json |
| Auth metadata (RFC 9728) | https://unremind.me/.well-known/oauth-protected-resource |
| LLM-facing site map | https://unremind.me/llms.txt |
| Health / liveness | https://unremind.me/health |
A 401 from the endpoint carries
WWW-Authenticate: Bearer resource_metadata="…", so a compliant client can
discover the auth model without being told.
Deep links
Every entity has both an app link and an https twin:
unremind://u/{id} # opens the app
https://unremind.me/u/{id} # always resolves
Print both when referring a person to something — you can't tell whether they're reading on the device that holds the app or on a desktop where a custom scheme resolves to nothing.
Design notes for agent authors
create_unremindersubmits for approval; it does not silently appear in the user's list. Writes that a person will act on go through them.- Context tags describe what a task requires to be doable (
Computermeans the task needs a computer) — never what the user currently has. save_progressnotes are yours, not a source of truth. The user edits tasks in the app between sessions; always re-read the live task before acting on a recollection.
Status
Production. Server unremind-mcp v2.0.0. Liveness at
https://unremind.me/health (200 healthy / 503 degraded), checked
continuously.
Issues and questions: open an issue or mailto:[email protected].
License
MIT for this repository's contents. The UnRemind.me service itself is governed by its Terms and Privacy Policy.
Two servers
UnRemind.me exposes two MCP servers with different auth models. They cross-reference each other, so an agent that finds either learns of the other.
| Endpoint | Auth | For | |
|---|---|---|---|
| UnRemind.me | https://unremind.me/mcp | bearer token | Manage your own reminders — 16 tools, 4 prompts |
| UnRemind.me Submit | https://unremind.me/mcp/submit | none | Send a reminder to someone else with a public page — 2 tools, 1 prompt |
Listed on
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.