Repository navigation
MCP for Cloud 1.3.0
This release reorganizes the app into capability modules, following the architecture proposed by @marcjoancr in #14, and adds writing for Forms structure, Polls, Tables schema and sharing, Collectives, Calendar reminders, Deck completion and archiving, HTML mail drafts and task status. Existing permissions, the admin and personal pages, endpoints and client connections stay the same.
Database migration on update: this version includes Version001205Date20261106000000 for CIMD host trust and credential generations (#28), the first database migration since 1.1.0. Nextcloud runs the migration and the CimdHostsSeedStep post-migration repair step. The effective CIMD host allowlist is preserved. Credentials issued to hosts that remain allowed survive with client_gen = 1. Credentials from a host that was never allowed no longer authenticate or refresh; an administrator must allow the intended host and the client must sign in again.
Added
-
Calendar reminders (#24): optional
alarmson create/update, with up to five DISPLAY reminders relative to the master event start, 0–40320 minutes before it. Omission preserves existing update alarms; an explicit list replaces only valid DISPLAY/start alarms, including removal with[]. Other alarms and recurrence overrides remain. Plans show the change and receipts observe the server result, without claiming notification delivery. Existing grants and confirmation remain.calendar_list_eventsnow returns the DISPLAY reminders relative to the start managed by MCP underalarmswith the same keys accepted by create/update (minutesBeforeanddescription), and counts other reminders inotherAlarms; confidential events and read-only shares expose none. Existing negative, non-integer or greater than 40320 offsets remain visible and must be adjusted before reuse in create/update.calendar_update_eventnow reports a replaced reminder with the sameindexin the plan (alarmChange.after) and inalarmReceipt.requestedas inalarmReceipt.observed: its position among the event's reminders, counted from 0.calendar_create_eventwas not affected. -
Forms structure writes (#1): seven operations (
forms_add_question,forms_reorder_questions,forms_add_option,forms_reorder_options,forms_delete_question,forms_delete_option,forms_change_question_type) add/reorder/delete questions/options and change a question type under the existingforms.editand native EDIT permission. Checked native APIs are Forms 5.3.0, 5.3.7, 5.4.0 and 5.4.1. Question deletion is logical and can orphan answers; option deletion is irreversible; deleting an upload question can schedule native asynchronous folder cleanup whose completion is not observed. Type changes do not convert answers and refuse grid/datetime targets. Plans bind state; effects may be partial or uncertain, without retry/rollback. Administrators should review existingforms.editgrants, which include these operations. The existing Edit forms help lists them; there is no grant rewrite or layout change. -
Polls writing (#1): ten operations configure/change state, manage/reorder/remove/restore options, manage shares and send one individual invitation, under separate default-denied configure/options/options.remove/share/invite grants and native editing rights. Public sharing follows the actor's native policy and never returns tokens/URLs. No automatic vote or retry; an invitation marker does not prove delivery. Existing 1.2.5 presets, levels and labels are preserved.
-
Tables schema and sharing (#1): eight operations create/update tables, columns and views with
tables.schema, and share/revoke user/group access withtables.share. Both grants start denied; the Full level includes them. Initial native API ranges are[1.0.10,1.0.11)on NC32 and[2.2.2,2.2.3),[2.3.1,2.3.3)or exactly2.4.0on NC33–35, subject to shape checks. Existing reading/row-writing compatibility stays separate. No schema deletion, owner transfer or public link; native manage rights still apply. Partial/unverified outcomes, concurrent overwrite and duplicate creation remain possible without automatic retry/rollback or guaranteed Undo. Add an exact schema/sharing profile on Nextcloud 33–35 with native API introspection. Preserve view layouts/card sources; refusetables_update_viewandtables_create_columnwithview_idswhen their column changes would clear a card source. Additional official-source contracts cover read/row APIs and column parsers, while a SHA-pinned NC35 archive opt-in keeps the existing matrix pins. -
Collectives pages (#22): list/pages/read/search, create, edit Markdown, move and rename inside an existing collective. The independent read grant starts allowed; create/edit/move start denied, with native permissions and confirmed plans. Content search is refused before 4.4.0 while title search remains. The approved native API ranges are 4.0.0–<4.8.0 on NC32–33, 4.4.0–<4.8.0 on NC34 and 4.5.0–<4.8.0 on NC35, subject to shape checks. No page deletion, attachments, templates or sharing management; Text editing has no cross-service CAS guarantee. Collective creation and members are below.
-
Create a collective (#22): on NC33–35 only,
collectives_create_collectivecreates a collective with its own new team, owned by the user and with no other member, through Collectives itself. The newcollectives.collective.creategrant starts denied and is included only in the Full level. A name already used by a collective or team the user sees is refused before writing, guest accounts are refused, and an account Teams has not used yet is asked to open Collectives once. Limitation: a team of that name administered by the user that appears between confirmation and creation is adopted by Collectives and its members get access; the plan warns and the receipt reports it, and after a failure halfway adoption may be unknown. On NC35 Teams may add a team folder. No collective is deleted; nothing is retried, undone or repaired. -
Collective members (#22): on NC33–35 only,
collectives_list_members,collectives_add_member,collectives_set_member_levelandcollectives_remove_membermanage members through Teams, as the Collectives interface does. The newcollectives.membersgrant (listing included) starts denied and is included only in the Full level. Only collective admins change members, and Teams checks its own rules again. Accounts and groups of the server can be added; Teams sends no email of its own. Limitation: in a team that requires invitations, an account gets an invitation and a Nextcloud notification, unless it had already asked to join: then the request is accepted and it becomes a member at once; groups are refused. Levels are member, moderator and admin; ownership is never transferred, and the owner and the user's own membership are never changed or removed. Receipts read the team again and report Teams' internal records apart. -
HTML mail drafts (#30):
mail_create_draftaccepts optionalhtml: truewhile keeping plain text as the default. The confirmation shows the complete sanitized HTML, a whitespace-preserving text preview, removal counts, names of unwrapped elements and all link destinations. Images and active content are forbidden; unavailable sanitization or a nonempty body left without readable content is refused before saving. No signature is added and nothing is sent. -
Deck completion and archiving (#27):
deck_set_card_donecompletes/reopens anddeck_set_card_archivedarchives/unarchives through the native Deck service, using the existing deck.edit grant. Each requires preview and state-bound confirmation; received boards also require confirm_shared. Completion preserves the native Unix UTC timestamp and can move to the configured done column on Deck 1.19, as shown in the plan. Reopening does not return the card to the previous list, and an already completed card is a no-op, not a retry of a partial move. Unarchive before completing/reopening. Completing and archiving remain separate, non-atomic calls. -
Task status on create and edit:
statusaccepts NEEDS-ACTION, IN-PROCESS, COMPLETED and CANCELLED, following the Tasks app. Status alone completes at 100% with a timestamp (preserving an existing time when already completed), reopens 100% at 99%, and starts IN-PROCESS at 1% from zero or absent progress. CANCELLED preserves progress and the completion date and remains listed. Explicit progress takes precedence when consistent; contradictory pairs are refused before writing. Progress alone retains its previous behavior, including reopening cancelled tasks. Confirmation plans show status and completion-date changes in the plan timezone. Thanks to @mturgeonferland (#29), Marc-Olivier Turgeon-Ferland, for the code that served as the basis for status/progress support.
Changed
-
Permission catalog and presets (F00): Tables schema/share and Polls configure/options/options.remove/share/invite are independent, default-denied operations. In the permission matrix, Full now also covers Tables structure (
tables.schema) and sharing (tables.share), and creating collectives (collectives.collective.create) and managing members (collectives.members), as Full already did in every other app; its description in the level popover lists them. Nothing is granted automatically: a person or group saved with the earlier Full (rows or pages only) is shown as Custom until an administrator chooses Full again. Read now denies those operations, like the lower levels of the other apps; None still denies all. The layout, the bulk changes and Undo are unchanged. This also applies to a Tables Full selection saved in 1.2.5: existing rows-only grants are not expanded automatically. Polls presets keep their 1.2.5 operation sets and labels, preserving independent grants outside those sets. New grants use the existing matrix layout. -
Capability-module architecture: The code is reorganized into capability modules (
mcp/lib/Modules,mcp/lib/Mcp,mcp/lib/Access,mcp/lib/OAuth,mcp/lib/Platform) following the architecture proposed by Marc J. Cabrer Rosselló in #14. Thanks to @marcjoancr for the proposal; its code was not merged.
Fixed
-
Allowed client hosts field: in the OAuth clients section, the allowed client hosts field is now wide enough to read a list of a few hosts (up to 24em, never wider than the panel) instead of the core's 130px, which cut "claude.ai, chatgpt.com" short, and its label keeps the standard spacing from the field. This fixes a defect already present in 1.2.5.
-
Round focus ring on admin radios: in the level popover of the permissions screen and in the resource scope, the radio's focus and hover ring is a tight circle again instead of a tall ellipse. Nextcloud's core styles give every input a 36px height and the clickable-area minimum height, and the native radio drew its ring around that tall box; the radio keeps its size, position and the rest of the layout. This fixes a defect already present in 1.2.5.
-
Tables row receipts without a false difference note:
tables_create_rowandtables_update_rowno longer add "Tables returned a different value for at least one cell" when a whole number in a plain number column comes back as an integer (42) instead of the expected42.0, which Tables does on every supported release. Plain numbers are now compared by value; text and every other value are still compared exactly, so a rounded number, a changed text or a normalized option still gets the note. This fixes a defect already present in 1.2.5. -
Deck card board in write results:
deck_delete_cardanddeck_move_cardnow return the card'sboardIdandurlinstead ofnull; after a move it is the destination board.deck_edit_cardkeeps them when it confirms a failed update by reading the card again. This fixes a defect already present in 1.2.5. -
Filtered server log reads no longer time out:
logs_listandlogs_analyzeread the current log file in 64 KiB reverse blocks under a cooperative 1000 ms budget. Whenscan.timeBudgetReachedis true, continue withscan.nextOffset; lines over 16 MiB are reported inscan.oversizedwithout being decoded. This fixes a defect already present in 1.2.5. -
Reading the current file version:
files_version_readnow reads the current version listed byfiles_versions_listwhen the backend has no separate stored version file, instead of failing with a missing-file error. Other missing historical versions remain refused. This fixes a defect already present in 1.2.5. -
File version order:
files_versions_listnow returns versions newest first and applieslimitafter ordering, as its description states. This fixes a defect already present in 1.2.5. -
OAuth host withdrawal (#28): removing an allowed CIMD host revokes its pending consents, authorization codes, access tokens and refresh tokens. Re-adding the host requires a new sign-in and never restores old credentials. Authorization metadata now also advertises the
issresponse parameter already returned on success and redirectable errors (RFC 9207); consent keeps the issuer from the authorization request even if the router changes the/index.phpprefix. Default hosts, client metadata parsing and registration methods are unchanged. Zapia interoperability still requires a verified remote MCP connector, registration method and callback from Zapia; its public connector guide does not document these details (checked 2026-11-07). This fixes a defect already present in 1.2.5. -
Deck assignment to other members (#26): assigning another board member through
deck_edit_card,deck_create_cardordeck_create_boardno longer fails when that member's push notification cannot be prepared or sent. Deck notifies the assignee before it saves the assignment, and the Notifications app prepares and sends the push inside that call for a member with a push device; an error there ended the call before the assignment was saved, which is why assigning oneself and accounts without a push device worked. Each assignment is still made first exactly as before, so members whose push works get it at once. Only an assignment that failed this way is retried at the end of the call inside the notification manager'sdefer()/flush(): it is saved, the notification left by the failed attempt is first withdrawn through Deck's own helper, and the delivery error comes back as the existing warning "Saved; Deck reported an error afterwards". When the Notifications app does not confirm that the earlier notification is gone, the assignment is not retried and fails as before, so a member never gets the notification twice. Retries run after all other assignments because a failed push keeps Nextcloud's deferral and the Notifications queue from sending anything else in the same request. Reproduced on NC32/Deck 1.16.8 and NC35/Deck 1.19.0 with push devices registered through the Notifications app and an error raised while one member's push is prepared; Deck's own web route still fails in that case. Unreachable push services and HTTP errors are handled by the Notifications app and never aborted the assignment. The exact error on the reporting instance was not available; the fix covers any error raised in that step. This fixes a defect already present in 1.2.5. -
PDF text with characters outside the BMP on PHP 8.4+:
files_readand PDF mail attachments again return emoji and other characters beyond U+FFFF (for exampleAá😀) instead of??on PHP 8.4.27, 8.5.12 and later. Those patch releases stopped writing a lone UTF-16 surrogate as CESU-8 in mbstring, and smalot/pdfparser converts each half of a font's ToUnicode surrogate pair on its own, so the character was lost before the text reached the app; no upstream release changes this yet. After parsing, the app reads the font's ToUnicode map again in the parser's order, where a later definition of a code replaces the earlier one, and gives each code the parser loaded whose effective definition holds a valid surrogate pair its whole character, through the parser's public translation table. An incremental range with such a destination (<0001> <0002> <D83DDE00>) now gives consecutive characters (😀😁) on every PHP version instead of��, by incrementing the last byte of the destination as the PDF specification defines; a code whose last byte would pass FF, which the specification leaves undefined, keeps the parser's value. Other codes keep the parser's value, the library is unchanged, and text without surrogate pairs reads as before on PHP 8.2 and 8.3. This fixes a defect already present in 1.2.5.
Community feedback
- Tables, Forms, Polls and Mail support follows the request of @matt-ek in #1; this release adds Forms structure writes, Polls writing, Tables schema and sharing, and Tables 2.4.0.
- Collectives support follows the request of @Beluluz in #22.
- Calendar reminders (
alarms) follow the request of @Dunc80 in #24. - The Deck assignment fix follows the report of @Beluluz in #26.
- Deck completion and archiving follow the request of @Beluluz in #27.
- OAuth host withdrawal and the RFC 9207 issuer follow the feedback of @filipesaraiva in #28.
- HTML mail drafts follow the request of @Beluluz in #30.
- Task status on create and edit is based on the code of @mturgeonferland in PR #29. Thanks to @mturgeonferland (PR #29).
- The capability-module architecture follows the proposal of @marcjoancr in #14.
Feedback credits name who requested, reported or suggested a change; only PR #29 is credited as code.