[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Nextcloud API and MCP server

> Yes. Every Nextcloud instance has WebDAV for files, CalDAV for calendars, CardDAV for contacts, an OCS Share API and a Deck API, and they accept an app password (checked 16 Oct 2026). Nextcloud has no standalone MCP server: the official one exists only inside the Context Agent app, which an admin sets up with Nextcloud Assistant, AppAPI and a Deploy Daemon.

Open-source file sync and collaboration platform you run yourself or rent from a hosting provider: files and shares, a calendar, contacts and Deck kanban boards in one instance.

## What is the Nextcloud API?

Cotlet's Nextcloud API exposes 15 endpoints for your own Nextcloud account: list files, search files, list shares, list calendars, list events, search contacts, list Deck boards, list Deck cards, upload file, create folder, share file, remove share, create calendar event, add contact and create Deck card. The list_files endpoint returns files and folders inside one folder, with size, type and last change. Each endpoint takes simple JSON inputs like path, limit or calendar and works both as an operation of the nextcloud_read or nextcloud_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 15 (8 read, 7 write)
- **Updated:** 2026-10-22

Yes. Cotlet is a hosted MCP server and REST API for Nextcloud with 15 endpoints (8 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Nextcloud have an official API?

Yes. Every Nextcloud instance has WebDAV for files, CalDAV for calendars, CardDAV for contacts, an OCS Share API and a Deck API, and they accept an app password (checked 16 Oct 2026). Nextcloud has no standalone MCP server: the official one exists only inside the Context Agent app, which an admin sets up with Nextcloud Assistant, AppAPI and a Deploy Daemon.

| Task | Nextcloud official | Cotlet |
|---|---|---|
| Upload a file | Yes: WebDAV PUT overwrites an existing file | Yes |
| Search files | Yes: WebDAV SEARCH inside one folder, by name, type, size or date | Yes |
| Share a file or folder | Yes: OCS Share API: public link, user, group, email | Yes |
| Create a calendar event | Yes: CalDAV | Yes |
| Add a contact | Yes: CardDAV | Yes |
| Create a Deck card | Yes: Deck REST API | Yes |
| Call these as MCP tools from your own agent | Partly: Only through Context Agent, installed by an admin | Yes |

Sources: [Nextcloud Admin Manual: Context Agent](https://docs.nextcloud.com/server/stable/admin_manual/ai/app_context_agent.html), [Nextcloud Developer Manual: WebDAV basic APIs](https://docs.nextcloud.com/server/stable/developer_manual/client_apis/WebDAV/basic.html), [Nextcloud Developer Manual: Share API](https://docs.nextcloud.com/server/stable/developer_manual/client_apis/OCS/ocs-share-api.html), [Nextcloud Deck: REST API](https://deck.readthedocs.io/en/latest/API/)

## For AI agents

```text
Yes. Every Nextcloud instance has WebDAV for files, CalDAV for calendars, CardDAV for contacts, an OCS Share API and a Deck API, and they accept an app password (checked 16 Oct 2026). Nextcloud has no standalone MCP server: the official one exists only inside the Context Agent app, which an admin sets up with Nextcloud Assistant, AppAPI and a Deploy Daemon.
Cotlet provides a hosted MCP server and REST API for Nextcloud: 15 tools (8 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=nextcloud, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    nextcloud_read, nextcloud_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/nextcloud, each operation at its own route, e.g. POST /api/v1/nextcloud/file/share
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_files, search_files, list_shares, list_calendars, list_events, search_contacts, list_deck_boards, list_deck_cards, upload_file, create_folder, share_file, remove_share, create_calendar_event, add_contact, create_deck_card
Confirm      upload_file, share_file, remove_share, create_calendar_event, add_contact, create_deck_card (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/nextcloud-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=nextcloud, requests Nextcloud in the Cotlet console and creates an API key there.
2. The user signs in to Nextcloud once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Nextcloud for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Nextcloud server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Nextcloud MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Nextcloud in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Nextcloud only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Nextcloud login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Nextcloud's terms; Cotlet is not affiliated with Nextcloud.
```

## What can an AI agent do in Nextcloud?

Cotlet is best for teams and freelancers on a Nextcloud reachable from the internet, often managed hosting, who want their AI agent to share files, create Deck cards and add events and contacts without running or fixing a server.

- **[Share a file with an expiring link](https://cotlet.dev/integrations/nextcloud-api-mcp-server/share-file-with-expiring-link.md)**: "Upload this report to /Clients/Acme in my Nextcloud, create a public link with a password that expires on 15 November, and give me the link to send." → `upload_file`, `share_file`
- **[Turn meeting notes into Deck cards](https://cotlet.dev/integrations/nextcloud-api-mcp-server/create-deck-cards-from-notes.md)**: "Read these meeting notes, find the action items and create a card for each in the Product board, in the To do stack, with the owner and due date in the description." → `list_deck_boards`, `list_deck_cards`, `create_deck_card`
- **[Audit public share links](https://cotlet.dev/integrations/nextcloud-api-mcp-server/audit-public-share-links.md)** (runs: weekly): "List every public link in my Nextcloud, tell me which have no password or no expiry date, and remove the ones I confirm." → `list_shares`, `list_files`, `remove_share`
- **Add calendar events from emails**: "Read this email and add the meeting to my Work calendar, unless something already overlaps." → `list_calendars`, `list_events`, `create_calendar_event`
- **Save contacts from email signatures**: "From these three emails, add each sender to my Business address book with name, company, phone and email, unless they are already there." → `search_contacts`, `add_contact`

## Can Nextcloud automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Nextcloud connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to audit public share links, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/nextcloud/shares. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/nextcloud/shares with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Nextcloud.

### list_files

Files and folders inside one folder, with size, type and last change. Access: read. REST: `GET /api/v1/nextcloud/files`. MCP: `nextcloud_read → list_files`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `path` | string | yes | Folder path, e.g. '/Clients/Acme'. Use '/' for the top level. |

Lists the direct contents of one folder of your Nextcloud, folders first. Each item has its path, size, MIME type and last modified time. Use the paths it returns in the other tools. Pass the root path to see the top level of your files.

Example response:

```json
{
  "items": [
    {
      "path": "/Clients/Acme/proposal-q3.pdf",
      "type": "file",
      "size": 388102,
      "mime": "application/pdf",
      "modified_at": "2026-09-18T14:20:00Z"
    },
    {
      "path": "/Clients/Acme/Contracts",
      "type": "folder",
      "size": 1204411,
      "mime": "httpd/unix-directory",
      "modified_at": "2026-10-02T09:05:00Z"
    }
  ]
}
```

### search_files

Search your files by name, type, size or last change inside one folder. Access: read. REST: `GET /api/v1/nextcloud/files/search`. MCP: `nextcloud_read → search_files`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `folder` | string | no | Folder to search in. Default: '/' (all your files). |
| `name_contains` | string | no | Part of the file name. |
| `mime_type` | string | no | MIME type or pattern, e.g. 'application/pdf' or 'image/%'. |
| `min_size_bytes` | integer | no | Only files larger than this. |
| `modified_since` | datetime | no | Only files changed after this time. |
| `limit` | integer | no | Maximum results. Default: 50. |

Runs a Nextcloud search inside one folder and everything below it, files only. Nextcloud searches within the folder you give, so for the whole account pass the root. Filters combine: a name part, a type such as text/% or application/pdf, a minimum size, a modified date. Results come newest first.

Example response:

```json
{
  "items": [
    {
      "path": "/Clients/Acme/proposal-q3.pdf",
      "size": 388102,
      "mime": "application/pdf",
      "modified_at": "2026-09-18T14:20:00Z",
      "file_id": 48213
    }
  ]
}
```

### list_shares

Shares you created, with type, permissions, password and expiry flags. Access: read. REST: `GET /api/v1/nextcloud/shares`. MCP: `nextcloud_read → list_shares`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `path` | string | no | Only shares of this file or folder. |
| `include_subfiles` | boolean | no | With a folder path, also shares of what is inside it. Default: false. |
| `type` | enum | no | all, link, user, group or email. Default: all. |

Lists the shares of your account, optionally for one file or folder and its contents. Each share has its type (link, user, group or email), the permissions you gave, whether it has a password and its expiry date. A public link returns its URL. Pass share_id from here to remove_share.

Example response:

```json
{
  "shares": [
    {
      "share_id": "412",
      "path": "/Clients/Acme/proposal-q3.pdf",
      "type": "link",
      "url": "https://cloud.example.com/s/Qm4Zr8LcVt1NxWe",
      "permissions": "read",
      "password_protected": false,
      "expires": null,
      "created_at": "2026-06-02T10:11:00Z"
    },
    {
      "share_id": "455",
      "path": "/Clients/Brightly/brief.docx",
      "type": "link",
      "url": "https://cloud.example.com/s/Hd7Pb2YaUs5GkTi",
      "permissions": "read",
      "password_protected": true,
      "expires": "2026-12-01",
      "created_at": "2026-10-09T08:40:00Z"
    }
  ]
}
```

### list_calendars

Your calendars with name, color and whether they are writable. Access: read. REST: `GET /api/v1/nextcloud/calendars`. MCP: `nextcloud_read → list_calendars`.

No parameters.

Lists the calendars of your account, including calendars others shared with you. Use the calendar value in list_events and create_calendar_event. Shared calendars can be read-only, and the writable flag says which.

Example response:

```json
{
  "calendars": [
    {
      "calendar": "work",
      "name": "Work",
      "color": "#0082C9",
      "writable": true
    },
    {
      "calendar": "holidays",
      "name": "Team holidays",
      "color": "#2E7D32",
      "writable": false
    }
  ]
}
```

### list_events

Events of one calendar between two dates, oldest first. Access: read. REST: `GET /api/v1/nextcloud/events`. MCP: `nextcloud_read → list_events`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `calendar` | string | yes | Calendar from list_calendars. |
| `from` | datetime | yes | Start of the range. |
| `to` | datetime | yes | End of the range. |

Returns the events of one calendar that fall in the time range, oldest first, with title, start, end, location and all-day flag. Use it before creating an event to find overlaps.

Example response:

```json
{
  "events": [
    {
      "event_id": "a41c0d7e-5b2f-4c1a-9e20-77d3f0b6c812",
      "title": "Acme kickoff",
      "start": "2026-10-21T10:00:00+02:00",
      "end": "2026-10-21T11:00:00+02:00",
      "location": "Video call",
      "all_day": false
    }
  ]
}
```

### search_contacts

Contacts by name, email or company, with phone numbers and addresses. Access: read. REST: `GET /api/v1/nextcloud/contacts/search`. MCP: `nextcloud_read → search_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of a name, email or company. |
| `address_book` | string | no | Address book name. Default: 'contacts'. |
| `limit` | integer | no | Maximum results. Default: 50. |

Searches your address books and returns matching contacts with name, company, emails and phone numbers. Use it before add_contact to avoid duplicates. An empty query lists the first contacts of the address book.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "c7f2e1a0-3b44-4d6e-8a19-2f5d9c0b7e31",
      "name": "Maria Silva",
      "company": "Brightly",
      "emails": [
        "maria@brightly.example"
      ],
      "phones": [
        "+351 21 000 0000"
      ],
      "address_book": "contacts"
    }
  ]
}
```

### list_deck_boards

Your Deck boards with their stacks (columns). Access: read. REST: `GET /api/v1/nextcloud/deck-boards`. MCP: `nextcloud_read → list_deck_boards`.

No parameters.

Lists the Deck boards you can open, each with its stacks in board order. Use the board_id and stack_id values in list_deck_cards and create_deck_card. Archived boards are left out.

Example response:

```json
{
  "boards": [
    {
      "board_id": 7,
      "title": "Product",
      "stacks": [
        {
          "stack_id": 20,
          "title": "Backlog"
        },
        {
          "stack_id": 21,
          "title": "To do"
        },
        {
          "stack_id": 22,
          "title": "Done"
        }
      ]
    }
  ]
}
```

### list_deck_cards

Cards in a board or one stack, with description, due date and status. Access: read. REST: `GET /api/v1/nextcloud/boards/{board_id}/deck-cards`. MCP: `nextcloud_read → list_deck_cards`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | integer | yes | Board ID from list_deck_boards. |
| `stack_id` | integer | no | Only cards in this stack. |

Returns the cards of one board, or of one stack when stack_id is set, in stack order, with title, description, due date, assigned users and archived flag. Use it to find an existing card before creating a new one.

Example response:

```json
{
  "cards": [
    {
      "card_id": 311,
      "stack_id": 21,
      "title": "Update changelog",
      "description": "",
      "due_date": "2026-10-18",
      "assigned": [
        "lena"
      ],
      "archived": false
    }
  ]
}
```

### upload_file

Write a file to your Nextcloud at a path. It does not replace an existing file unless you say so. Access: write, asks the user first. REST: `POST /api/v1/nextcloud/files`. MCP: `nextcloud_write → upload_file`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `path` | string | yes | Path inside your files, starting with a slash, e.g. '/Clients/Acme/proposal.pdf'. |
| `content` | string | yes | File content, as text or base64. |
| `encoding` | enum | no | text or base64. Default: text. |
| `overwrite` | boolean | no | Replace an existing file. Default: false. |

Writes a file at the path you give. Text goes in as content; for a binary file such as a PDF, send base64 and set encoding. If a file already exists at that path, the call fails unless overwrite is true, because Nextcloud replaces the old file otherwise. Missing parent folders are created. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "path": "/Clients/Acme/proposal-q4.pdf",
  "size": 421880,
  "status": "created",
  "file_id": 49027
}
```

### create_folder

Create a folder, with missing parent folders. Access: write. REST: `POST /api/v1/nextcloud/folders`. MCP: `nextcloud_write → create_folder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `path` | string | yes | Path inside your files, starting with a slash, e.g. '/Clients/Acme/proposal.pdf'. |

Creates a folder at the path, and any parent folders that are missing. If the folder already exists, nothing changes and the call says so. create_folder runs without asking first: it reaches no one and an empty folder is removed with one click in the Files app.

Example response:

```json
{
  "path": "/Clients/Acme/Contracts",
  "status": "created"
}
```

### share_file

Share a file or folder by public link, or with a user, group or email address. Access: write, asks the user first. REST: `POST /api/v1/nextcloud/file/share`. MCP: `nextcloud_write → share_file`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `path` | string | yes | Path inside your files, starting with a slash, e.g. '/Clients/Acme/proposal.pdf'. |
| `share_type` | enum | yes | link, user, group or email. |
| `share_with` | string | no | User name, group name or email address. Required unless share_type is link. |
| `permissions` | enum | no | read or edit. Default: read. |
| `password` | string | no | Password for a public link. |
| `expire_date` | date | no | Last day of the share, YYYY-MM-DD. |
| `note` | string | no | Note shown to the recipient. |

Creates a share for one file or folder. For a public link you can set a password, an expiry date (YYYY-MM-DD) and a note; permissions default to read only. For a user, group or email address, set share_with. The reply contains the link or the share ID. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "share_id": "460",
  "path": "/Clients/Acme/proposal-q4.pdf",
  "type": "link",
  "url": "https://cloud.example.com/s/Kp3xTq9WmB2Rz7a",
  "permissions": "read",
  "password_protected": true,
  "expires": "2026-11-15"
}
```

### remove_share

Remove a share, so a public link or access stops working. Access: write, asks the user first. REST: `DELETE /api/v1/nextcloud/shares/{share_id}`. MCP: `nextcloud_write → remove_share`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `share_id` | string | yes | Share ID from list_shares. |

Removes one share. A public link stops working at once, and a user or group loses the access this share gave. A person with another share on the same item keeps that access. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "share_id": "412",
  "status": "removed"
}
```

### create_calendar_event

Add an event to a calendar, with time, location and description. Access: write, asks the user first. REST: `POST /api/v1/nextcloud/calendar-events`. MCP: `nextcloud_write → create_calendar_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `calendar` | string | yes | Calendar from list_calendars. |
| `title` | string | yes | Event title. |
| `start` | datetime | yes | Start time with a time zone. |
| `end` | datetime | yes | End time with a time zone. |
| `all_day` | boolean | no | All-day event. Default: false. |
| `location` | string | no | Place or meeting link. |
| `description` | string | no | Event notes. |

Adds one event to a writable calendar. Give start and end with a time zone, or set all_day. Returns the event ID. Run list_events first to avoid an overlap. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "d09b6a3c-81e4-4f77-b2a5-6e1c3f7a9d44",
  "calendar": "work",
  "title": "Acme kickoff",
  "start": "2026-10-21T10:00:00+02:00",
  "end": "2026-10-21T11:00:00+02:00",
  "status": "created"
}
```

### add_contact

Add a contact to an address book with name, company, emails and phones. Access: write, asks the user first. REST: `POST /api/v1/nextcloud/contacts`. MCP: `nextcloud_write → add_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | no | Full name. |
| `company` | string | no | Company. |
| `emails` | array | no | Email addresses. |
| `phones` | array | no | Phone numbers. |
| `address_book` | string | no | Address book name. Default: 'contacts'. |

Creates one contact in an address book. A name or an email is required. Run search_contacts first, because adding a person who exists creates a second card. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "contact_id": "e18a52b4-9c07-4f3d-a6b1-0d2c7e5f8a63",
  "name": "Tom Becker",
  "address_book": "contacts",
  "status": "created"
}
```

### create_deck_card

Add a card to a Deck stack with a title, a markdown description and a due date. Access: write, asks the user first. REST: `POST /api/v1/nextcloud/boards/{board_id}/deck-cards`. MCP: `nextcloud_write → create_deck_card`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | integer | yes | Board ID from list_deck_boards. |
| `stack_id` | integer | yes | Stack ID from list_deck_boards. |
| `title` | string | yes | Card title, up to 255 characters. |
| `description` | string | no | Markdown description. |
| `due_date` | date | no | Due day, YYYY-MM-DD. |

Creates one card at the end of a stack. The title can have up to 255 characters, the description is markdown, and the due date is a day. Returns the card ID. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "card_id": 318,
  "board_id": 7,
  "stack_id": 21,
  "title": "Send pricing draft to finance",
  "due_date": "2026-10-23",
  "status": "created"
}
```

## How do I connect Nextcloud to Claude Code, Codex or Cursor?

Connecting Nextcloud takes three steps: sign up, sign in to Nextcloud once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Nextcloud to your agent.

1. **Create an account** Sign up and add Nextcloud in the console. Your API key is there too.

2. **Sign in to Nextcloud in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Nextcloud there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Nextcloud tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Upload this report to /Clients/Acme in my Nextcloud, create a public link with a password that expires on 15 November, and give me the link to send.
```

### Call Nextcloud from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/nextcloud with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/nextcloud/file/share \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"path":"/Clients/Acme/proposal-q4.pdf","share_type":"link","password":"Fj82-mint-ocean","expire_date":"2026-11-15"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "share_id": "460",
  "path": "/Clients/Acme/proposal-q4.pdf",
  "type": "link",
  "url": "https://cloud.example.com/s/Kp3xTq9WmB2Rz7a",
  "permissions": "read",
  "password_protected": true,
  "expires": "2026-11-15"
}
```

## Why use Cotlet for Nextcloud?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Nextcloud yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Nextcloud changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Nextcloud to Cotlet?

Yes. You sign in to Nextcloud yourself, in your own Cloud Browser, and we never save your password. Your agents only get Nextcloud once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Nextcloud integration?**

No, Cotlet is independent of Nextcloud. Nextcloud's own API is too limited for this work. Cotlet works through your own Nextcloud account, the way you use Nextcloud in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Nextcloud in your console: your agents lose access at once and you stay signed in. Signing out of Nextcloud in the browser works too, and Reset browser deletes the whole profile.

## Is there a Nextcloud MCP server on GitHub?

Yes. Community Nextcloud MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it an app password for each instance, and keep it running yourself; when Nextcloud or the maintainer changes something, you fix it. Cotlet hosts the same kind of server for you, and our team keeps it working. One difference: Cotlet connects from the internet, so your instance must be reachable from outside, as managed hosting usually is. An instance at home behind a VPN is better served by a local server.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, paste an app password and your instance address, add it to each MCP client | Sign up, enter your instance address and an app password once, add one MCP server or API key |
| When Nextcloud changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your app password | In a config file on your computer, readable by any program you run | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, deleted in your Nextcloud settings at any time |
| When the password stops working | Tools fail until you create a new app password and paste it in | Same trigger, but your agent gets a link to reconnect in one step |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on; works for an instance on a home network or VPN | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule; the instance must be reachable from the internet |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Nextcloud changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Nextcloud API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Nextcloud API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Nextcloud account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Nextcloud yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Nextcloud only after you enable it. When Nextcloud signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Nextcloud, sign out of Nextcloud in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Nextcloud's terms:** You use your own Nextcloud account and stay responsible for following Nextcloud's terms. Cotlet is independent and not affiliated with Nextcloud. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Nextcloud in the console and press Request access. Then you create your API key and connect Nextcloud there.

**Do I need to be technical?**

No. You sign in to Nextcloud once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Nextcloud to Cotlet?**

Yes. You sign in to Nextcloud yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Nextcloud once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Nextcloud sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Nextcloud cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Nextcloud's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Nextcloud sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Nextcloud login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Nextcloud offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Why not use the official Context Agent MCP server?**

You can, if you run the instance. Context Agent exposes an MCP server on your Nextcloud address, authenticated with an app password, and its tools include sharing, Deck, files, Talk and mail. It needs Nextcloud Assistant, AppAPI and a Deploy Daemon installed by an admin, Cotlet needs none of that on your instance.

**Does my Nextcloud need to be reachable from the internet?**

Yes. Cotlet calls your instance from the internet with an app password, so it works with managed Nextcloud and servers with a public address. An instance only on a home network or behind a VPN is not reachable from Cotlet.

**Do I have to switch off two-factor authentication?**

No. With two-factor authentication on, Nextcloud accepts only device-specific app passwords from clients, and Cotlet uses one. You create it in your avatar menu under Personal settings, Security, and you can revoke it there without changing your main password.

**Can my agent post or send messages in Nextcloud without asking me?**

No. Every call to upload_file, share_file, remove_share, create_calendar_event, add_contact or create_deck_card waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_folder runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Nextcloud API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/nextcloud from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.