# API REST/JSON for Nextcloud and MCP (SSE) support

**URL:** <https://help.nextcloud.com/t/api-rest-json-for-nextcloud-and-mcp-sse-support/224539>\
**Category:** 🏷️ General\
**Tags:** api, caldav, feature, carddav\
**Created:** [May 9, 2025, 11:09am UTC](https://help.nextcloud.com/t/api-rest-json-for-nextcloud-and-mcp-sse-support/224539 "2025-05-09T11:09:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Harokku\_Kyaputen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/harokku_kyaputen/32/69450_2.png) [@Harokku\_Kyaputen](https://help.nextcloud.com/u/Harokku_Kyaputen)\
**Post date:** [May 9, 2025, 11:09am UTC](https://help.nextcloud.com/t/api-rest-json-for-nextcloud-and-mcp-sse-support/224539/1 "2025-05-09T11:09:03Z")

</div>

### I have no support/technical question and have seen the support category. (Be aware that direct support questions will be deleted.)

on

### Which general topic do you have

I am proud to introduce a powerful extension for Nextcloud that revolutionizes how applications interact with its core calendaring and contact services.

Our custom-developed solution exposes Nextcloud’s CalDAV and CardDAV interfaces as modern, developer-friendly REST/JSON APIs, enabling seamless integration with virtually any application, regardless of platform or language.

No more dealing with legacy protocols — developers can now access, create, or update calendar events and contact records using simple HTTP requests and standard JSON payloads.

But that’s not all.

This platform also supports MCP (Message-Centric Protocol) mode using Server-Sent Events (SSE), making it natively compatible with intelligent agents and AI-driven automation tools. Real-time updates, continuous event streams, and smart synchronization capabilities are now at your fingertips

> **[GitHub - easyservices/api-sabre-nx-2: REST/JSON Bridge and MCP SSE for Nextcloud CalDAV...](https://github.com/easyservices/api-sabre-nx-2)**
>
> REST/JSON Bridge and MCP SSE for Nextcloud CalDAV and CardDAV

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [May 12, 2025, 8:10am UTC](https://help.nextcloud.com/t/api-rest-json-for-nextcloud-and-mcp-sse-support/224539/2 "2025-05-12T08:10:20Z")

</div>

Hello @Harokku_Kyaputen,

welcome to the Nextcloud community! 🤝

sounds good. It would be great you publish this app as native NC app without..

> All API endpoints require HTTP Basic Authentication with your Nextcloud credentials.

sounds problematic.

---

<div class="post-metadata">

**Author:** ![Harokku\_Kyaputen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/harokku_kyaputen/32/69450_2.png) [@Harokku\_Kyaputen](https://help.nextcloud.com/u/Harokku_Kyaputen)\
**Post date:** [May 12, 2025, 11:30am UTC](https://help.nextcloud.com/t/api-rest-json-for-nextcloud-and-mcp-sse-support/224539/3 "2025-05-12T11:30:18Z")

</div>

For now it is a design decision as I wanted to be “release independant” from nextcloud (but still glued to the underlying Sabre server) and I did not want to use AppAPI that did not meet my requirements (as it is more app driven than API driven).