Nextcloud Organizer Mcp

io.github.Vando-sketchPublished by GitHub account Vando-sketchv0.2.1Updated Oct 24, 2026

Manage Nextcloud tasks, calendar events and notes from Claude over CalDAV and the Notes API.

VerifiedSTDIODesktop onlyProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Self-hosted MCP server that lets an assistant create and manage Nextcloud tasks, calendar events and notes over CalDAV and the Notes API.

What you can do
Create, update, batch-move and delete tasks with priorities, tags, reminders, subtasks and recurrence, and turn a task into a linked calendar time block. Create and manage calendar events, including recurring events, attendees and RSVP, free/busy, sharing, ICS import/export and trash. View a combined day agenda of events and due tasks. Create, search, append to and replace passages or single Markdown sections of notes.
When to use it
Useful when you run your own Nextcloud instance and want an assistant to plan tasks, schedule events and edit notes in plain language, keeping the data on your own server rather than a third-party calendar service.
Requirements
Python 3.10+ and a Nextcloud instance with the Calendar/Tasks and Notes apps. Environment variables NEXTCLOUD_BASE_URL (https unless local), NEXTCLOUD_USERNAME, NEXTCLOUD_APP_PASSWORD and PUBLIC_BASE_URL, plus MCP_OAUTH_PASSWORD unless reached locally only. The server listens on a local HTTP port and needs a TLS-terminating proxy or tunnel to be reachable by clients.
Before you install
Requires a Nextcloud app password (NEXTCLOUD_APP_PASSWORD), not the account password, and an OAuth consent password (MCP_OAUTH_PASSWORD); keep both secret. Tools write, change and delete tasks, events and notes in your real Nextcloud, so mistakes affect live data. The OAuth redirect allow-list defaults to claude.ai and claude.com. The server does not handle TLS itself and is a community project not affiliated with Nextcloud.

Installation

In SourceWeft

  1. Open Nextcloud Organizer Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[nextcloud-organizer-mcp logo]

nextcloud-organizer-mcp

Let Claude run your Nextcloud tasks, calendar and notes.
A self-hosted MCP server for CalDAV tasks, events and the Notes app.

[PyPI] [CI] [Python 3.10+] [MIT license]

[A scripted client creating a task, a recurring event and a time block, then reading the day's agenda]
Real tool calls against a real Nextcloud · watch as video

Ask in plain language, and your own Nextcloud changes. No copy-paste, no third-party calendar service: the data stays on your server and the tools talk to it over standard CalDAV and the Notes REST API.

Community project, not affiliated with or endorsed by Nextcloud GmbH. Formerly nextcloud-task-mcp.

What you can say

You sayWhat happens
"Add a high-priority task: finish the Q4 report by Thursday 5pm, remind me 2 hours before."create_task with due date, priority and a VALARM reminder
"Add a weekly team sync, Mondays 10:00."create_event with an RRULE
"Block Thursday 9-11 for the report."create_event_from_task — a linked time block, task and event stay connected
"What does my Thursday look like?"get_agenda — events (recurring ones expanded) and due tasks in one answer
"Start a note for the Q4 report, then update just the status section."create_note, update_note_section

What Claude wrote shows up in the normal Nextcloud apps, immediately:

[Nextcloud Calendar showing the 9-11 time block and the task deadline]

[Nextcloud Tasks showing the high-priority task with its tag and due date]

[Nextcloud Notes showing the note after a single-section update]

Features

  • Tasks (VTODO): priorities, tags, reminders, subtasks, recurrence with exception dates, four-state status, batch update/delete/move.
  • Calendars and events (VEVENT): recurring events, attendees and RSVP, free/busy, sharing, ICS import/export, birthdays, batch operations, trash bin.
  • Timeboxing: turn a task into a calendar block and keep both linked.
  • Notes: create, search, append, replace a passage or a single Markdown section.
  • Combined day agenda: events and due tasks together.
  • Safe by default: OAuth 2.1 with a password consent page, https:// enforced for Nextcloud, clean error messages instead of stack traces.
  • 51 tools in total, documented in the tool reference.

Compatibility

ClientStatus
Claude (claude.ai web) as a custom connectorSupported, connector and consent flow tested against claude.ai
Claude mobile and CoworkUse the same connector as web; not tested separately
Claude Desktop via mcp-remoteDocumented in the deployment guide
Other MCP clients and model providersNot tested yet, planned

The server speaks standard Streamable HTTP MCP with OAuth 2.1 (Dynamic Client Registration + PKCE), so other clients may work. The OAuth redirect allow-list defaults to claude.ai and claude.com; other clients need MCP_OAUTH_ALLOWED_REDIRECT_DOMAINS set. Reports from other clients are welcome.

Quick start

Requires Python 3.10+ and a Nextcloud with the Calendar/Tasks and Notes apps.

bash
uv tool install nextcloud-organizer-mcp   # or: pipx install nextcloud-organizer-mcp

Create an app password under Settings → Security → Devices & sessions (never your account password), then set:

bash
export NEXTCLOUD_BASE_URL=https://cloud.example.comexport NEXTCLOUD_USERNAME=your-usernameexport NEXTCLOUD_APP_PASSWORD=your-app-passwordexport PUBLIC_BASE_URL=https://your-host.ts.net   # the URL clients useexport MCP_OAUTH_PASSWORD=a-long-random-password  # required unless local
bash
nextcloud-organizer-mcp     # listens on 127.0.0.1:8000, path /mcp

From a checkout instead: uv sync && cp .env.example .env, edit .env, then uv run nextcloud-organizer-mcp. Every setting is documented in .env.example. NEXTCLOUD_BASE_URL must be https:// unless it points at a local address.

Then expose the server (the deployment guide uses Tailscale Funnel for TLS) and add it in Claude under Settings → Connectors → Add custom connector with the URL <PUBLIC_BASE_URL>/mcp. Leave Client ID and Secret blank and enter your MCP_OAUTH_PASSWORD on the consent page that opens. Details: Authentication.

How it works

Claude ── HTTPS + OAuth 2.1 ──► your server (this project) ── CalDAV / Notes API ──► Nextcloud
  • One CalDAV connection is opened at startup and reused for every request.
  • No tool or CalDAV logic runs until a request carries a valid access token.
  • The server binds to a local HTTP port and does not handle TLS itself.
  • Timestamps use MCP_DEFAULT_TIMEZONE (default Europe/Berlin); naive inputs are interpreted in it.

Documentation

License

MIT

Source: README.md at commit 618018f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts