Agentda

Agent-native task management: your AI agent is the interface.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • My Agenda: The user's prioritized task overview: follow-ups due today, overdue tasks, tasks due today, delegated tasks (waiting on others), and remaining open tasks. Snoozed tasks are hidden. First st
  • Create Task: Creates a new task (the creator becomes the owner). IMPORTANT: If you are proposing this task on your own initiative (e.g. a to-do you spotted in the conversation), get the user's explici
  • Update Task: Changes fields (title, description, due date), sets the status (open / in_progress / waiting / done — done completes the task, open on a completed task reopens it) and/or adds a comment.

What data it sees

Do you need an account

No: the server works without sign-in

Agent-native task management: your AI agent is the interface. Create, prioritize and snooze tasks in conversation, delegate to workspace members or to any email address (guests get an email link, no account needed), and answer status questions from each task's complete, immutable history.

How to connect

How to connect Agentda to Claude

The server address to paste into Claude settings:

https://agentda--maurer.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Agentda to ChatGPT

The server address to paste into ChatGPT settings:

https://agentda--maurer.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Agentda to Cursor

The server address to paste into Cursor settings:

https://agentda--maurer.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (16)

Raw names from tools/list. Only developers need these.

my_agendaThe user's prioritized task overview: follow-ups due today, overdue tasks, tasks due today, delegated tasks (waiting on others), and remaining open tasks. Snoozed tasks are hidden. First stop for “what's on my plate?”.
create_taskCreates a new task (the creator becomes the owner). IMPORTANT: If you are proposing this task on your own initiative (e.g. a to-do you spotted in the conversation), get the user's explicit confirmation FIRST and set initiated_by to 'agent_confirmed'. Resolve people for CC via list_people beforehand.
update_taskChanges fields (title, description, due date), sets the status (open / in_progress / waiting / done — done completes the task, open on a completed task reopens it) and/or adds a comment. Every change is recorded as an event in the history.
complete_taskCompletes a task, optionally with an outcome comment (recommended — the outcome becomes part of the history and helps everyone involved).
delegate_taskDelegates a task to a registered user OR to any email address (unknown addresses automatically become guests: they receive an email with a link to a minimal task page and need no account). reason is required: be concrete — what needs to be done and why this person; it appears in the notification and the history. If acting on your own initiative, get the user's confirmation first (initiated_by = 'agent_confirmed'). Resolve workspace members via list_people.
respond_to_delegationResponds to a delegation: accept, reject (reason required), or return an already accepted task to the owner (return). On reject/return, responsibility falls back to the owner, who is notified.
snooze_taskSets a follow-up: the task disappears from the agenda until the given date, then resurfaces prominently (including a notification). Without snooze_until, an existing follow-up is cleared.
manage_accessManages visibility: add/remove CC (stay informed, read access + notifications) or share the task with specific people (read access). Resolve people via list_people beforehand. Every change is an event in the history.
task_detailsShows all details of a task: status, due date, description, participants, links, delegation state, and the most recent events. Read-only — first choice when a specific task is being asked about. For the full timeline use task_history.
task_historyReturns the complete, chronological history of a task: who created, changed, commented, delegated what and when. Ideal for getting context without asking anyone.
search_tasksFull-text search across titles, descriptions, and comments — only within tasks visible to the user.
link_taskAdds a typed external reference to a task (support ticket, project item, or URL) with cached metadata. No sync — for live data query the source system directly (e.g. via its MCP server).
attach_fileAttaches a file (screenshot, log, document; max 4 MB): returns a one-time upload URL — then upload the file via HTTP PUT (e.g. curl --upload-file). The upload response confirms storage; participants are notified. NEVER send file contents as base64 through the conversation.
remove_attachmentRemoves an attachment (allowed for the task owner or whoever attached the file). The removal is an event in the history.
list_peopleResolves people for delegation, CC, or sharing: name or (partial) email → user. Always call BEFORE delegate_task/manage_access when only a name is known.
admin_tenantWorkspace admins only: view/approve/deactivate members (open tasks fall back to their owners), toggle auto-join and invitation emails, view billing/trial status. Action 'status' shows the overview.