Ga naar hoofdinhoud

Leaf status

Every advertised leaf and its current capabilities. All 24 leaves are MCP-addressable — discoverable through the openregister.integrations MCP tool's list-integrations action and operable through list / get (and link / create where the storage strategy supports writes). See the verification report for the live no-crash proof and tiers for what each tier means.

How to read this table

  • Tier — maturity tier (tiers). All leaves are now at Tier 2/3.
  • Link table — has an explicit object ↔ upstream binding store. Query-time leaves compute fresh on every call, so they have no link table by design (✗ = N/A, not missing).
  • Picker / Create — the leaf offers a dialog to link an existing upstream thing / create a new one. Query-time leaves are read-only by design.
  • MCP — addressable through openregister.integrations. ✓ = readable (list/get); ✓+ = also writable (link/create).

Always-available built-ins (5)

Core leaves that ride on Open Register itself — requiredApp: null, always present.

LeafBacking appTierLink tablePickerCreateMCP
FilesOpen Register (magic-column)3✗ (magic-column)✓+
NotesOpen Register3✓+
TagsOpen Register3✓+
TasksOpen Register (VTODO)3✓+
Audit trailOpen Register (query-time)3✗ (query-time)

Nextcloud-native leaves (17)

Each requires its backing Nextcloud app to be installed (three-stage gate — see required-app gating). When the app is absent the leaf is advertised but enabled: false.

LeafBacking appTierLink tablePickerCreateMCP
Calendarcalendar3✓+
Contactscontacts3✓+
Emailmail3
Talkspreed2✓+
Deckdeck3✓+
Bookmarksbookmarks2✓+
Collectivescollectives2✓+
Mapsmaps2✓+
Photosphotos2
Pollspolls2✓+
Formsforms2
Cospendcospend2✓+
Time trackertimemanager2✓+
Analyticsanalytics2
Flowworkflowengine2✓+
Activityactivity (query-time)3✗ (query-time)
SharesOpen Register (query-time)3✗ (query-time)
Flow and Activity have special handling

Flow is admin-gated (workflow rules are an administrative surface). Activity is read-only — its events are generated by Nextcloud core, so the leaf lists them but never writes. See Admin notes.

External leaves (2, OpenConnector-routed)

Routed through an OpenConnector source on every CRUD — no local store. They require a configured source before the picker and create paths work (see External integrations).

LeafBacking serviceTierLink tablePickerCreateMCP
xWikiopenconnector → xWiki3✗ (external)✓+
OpenProjectopenconnector → OpenProject3✗ (external)✓+

The MCP-enablement payoff

Of the 19 non-builtin leaves above, none of the backing Nextcloud apps ships its own MCP tool. Deck, Forms, Maps, Cospend, Polls, TimeManager, Collectives, Photos, Bookmarks, Calendar, Contacts, Mail, Talk, Analytics, the workflow engine — all are invisible to AI agents on their own. Through this registry, every one of them is now reachable from a single Open Register MCP tool. That is the Tier-4 value: MCP-invisible apps made MCP-addressable for free.