aiquila

AIquila provides an MCP Server that bridges Claude AI with your self-hosted Nextcloud instance. Once running, Claude can browse and manage your Nextcloud data through natural conversation, including files, notes, tasks, bookmarks, and recipes. This enables Claude to read from and write to your Nextcloud repository without exposing your data to the public web, giving you the benefits of Claude’s AI capabilities while keeping control on your own server. The MCP server focuses on secure access and context sharing, so Claude can leverage your Nextcloud context during chats and tool-assisted tasks.

To use the server, authenticate with your Nextcloud instance and Claude API, then interact with Claude as you normally would in a chat. The MCP layer handles contextual access to Nextcloud resources, translating conversational intents into file operations, note creation, task management, and query actions against your stored data. Ensure your Claude API key and Nextcloud credentials are configured in the environment, and Docker or your hosting environment can reach your Nextcloud URL for seamless integration.

Prerequisites:

• Node.js (LTS version recommended) installed on the host where you will run the MCP Server
• Git installed to clone the repository
• Access to a Claude API key and a Nextcloud instance with appropriate permissions

Step-by-step installation:

1. Clone the MCP server repository:

git clone https://github.com/elgorro/aiquila.git
cd aiquila

2. Install dependencies:

npm install

3. Configure environment variables. Create a local environment file or set vars in your hosting environment. Example (adjust values):

NEXTCLOUD_URL=https://cloud.example.com
CLAUDE_API_KEY=your-claude-api-key
CLAUDE_MODEL=claude-2
NEXTCLOUD_USERNAME=your-username
NEXTCLOUD_PASSWORD=your-password

4. Start the MCP Server:

node server.js

5. Verify accessibility. The MCP server should start and listen for MCP requests from Claude clients. If you’re deploying behind a reverse proxy, ensure the appropriate routes are forwarded.

Optional: For production, consider running under a process manager (pm2, systemd) and securing traffic with TLS. Ensure environment variables are supplied by your hosting environment and not committed to source control.

Notes and tips:

• Claude API access is required; ensure your API key has the necessary permissions for model operations.
• The MCP server acts as a gatekeeper between Claude and Nextcloud. Ensure Nextcloud user credentials have permissions to read/write the needed resources.
• If Nextcloud is behind a firewall, whitelist the MCP server’s outbound IPs to allow Claude interactions.
• Monitor for rate limits on Claude or Nextcloud requests and implement retry/backoff as needed in your deployment.
• Use environment variable-based configuration in production to avoid leaking secrets. Consider mounting a .env file or using secret management provided by your hosting platform.