AIquila — Nextcloud MCP Server
Connect your self-hosted Nextcloud to an agent so it can work across files, mail, calendar, contacts, maps, notes, tasks, and 120+ other tools.
Overview
io.github.elgorro/aiquila-mcp is an MCP server for the Operate phase that gives agents 120+ tools against a self-hosted Nextcloud instance.
What is this MCP server?
- 120+ MCP tools across Nextcloud apps (files, calendar, contacts, mail, maps, notes, tasks)
- stdio npm via npx aiquila-mcp or Docker OCI ghcr.io/elgorro/aiquila-mcp
- Requires NEXTCLOUD_URL, NEXTCLOUD_USER, NEXTCLOUD_PASSWORD (app password)
- Nextcloud app integration branded AIquila—version 0.3.7
- SVG app icon from elgorro/aiquila repository
- 120+ MCP tools advertised
- MCP server version 0.3.7
- 2 install paths (npm npx, Docker OCI)
Community signal: 19 GitHub stars.
What problem does it solve?
Your knowledge and comms live in Nextcloud, but agents cannot see calendars, mail, or files until you bridge the stack with a dedicated MCP server.
Who is it for?
Privacy-minded solo builders and small teams with an existing Nextcloud server who want one MCP pipe for files and productivity apps.
Skip if: Users on Google Workspace or Notion-only stacks, or anyone unwilling to issue app passwords and maintain a Nextcloud instance.
What do I get? / Deliverables
After configuring URL, user, and app password, your agent can invoke AIquila tools to read and mutate Nextcloud data you already trust.
- 120+ agent tools mapped to Nextcloud apps
- Unified access to files, mail, calendar, contacts, notes, and tasks
- Repeatable agent ops on private cloud data
Recommended MCP Servers
Journey fit
A personal or team Nextcloud instance is ongoing production infrastructure; agents need MCP access during Operate to read and act on live data without exporting everything manually. Infra fits self-hosted cloud stacks where URL, user, and app-password wiring is the core setup story.
How it compares
Self-hosted Nextcloud MCP with 120+ tools—not a single-app Gmail or Drive connector.
Common Questions / FAQ
Who is io.github.elgorro/aiquila-mcp for?
It is for Nextcloud administrators and developers who want coding agents to interact with files, mail, calendar, and dozens of other Nextcloud apps via MCP.
When should I use io.github.elgorro/aiquila-mcp?
Use it when your operational source of truth is Nextcloud and you need agent workflows across multiple apps without custom API glue per service.
How do I add io.github.elgorro/aiquila-mcp to my agent?
Run npx aiquila-mcp or the Docker image, set NEXTCLOUD_URL, NEXTCLOUD_USER, and NEXTCLOUD_PASSWORD in MCP config, and ensure the AIquila Nextcloud app is installed if required.