Infomaniak MCP

🚀 Infomaniak MCP Server

A Model Context Protocol (MCP) server for interacting with the Infomaniak API. It enables AI assistants like Claude to manage Infomaniak services including domains, email, web hosting, kDrive, and more.

🚀 Quick Start

The Infomaniak MCP Server allows AI assistants such as Claude to interact with the Infomaniak API, enabling management of various Infomaniak services. To get started, you need to meet the prerequisites, obtain an API token, and then install and configure the server.

✨ Features

• 🌐 Domain Management: List domains and perform full DNS record CRUD operations.
• 📧 Email Services: Manage mailboxes, aliases, and mail configurations.
• 🖥️ Web Hosting: Manage sites, PHP versions, and MySQL databases.
• 💾 kDrive: Access and manage kDrive cloud storage.
• 🔒 Swiss Backup: View and manage backup products.
• 🖧 VPS & Servers: Control VPS instances and dedicated servers.
• 📜 SSL Certificates: View certificate information.
• 💰 Invoicing: Access billing and invoice data.
• 🔧 Generic API: Make custom API calls for advanced operations.

📋 Prerequisites

• Node.js 18 or higher.
• An Infomaniak account with API access.
• An API token from Infomaniak.

🔑 Getting Your API Token

1. Log in to your Infomaniak Manager.
2. Navigate to Account → API Tokens or visit token management.
3. Click "Create a token".
4. Select the appropriate scopes for your needs:
   • account - Account management.
   • domain - Domain management.
   • mail - Email services.
   • web - Web hosting.
   • drive - kDrive access.
   • swiss_backup - Backup services.
   • vps - VPS management.
   • dedicated - Dedicated servers.
   • certificate - SSL certificates.
   • invoicing - Billing access.
5. Copy and securely store your token.

📦 Installation

Using npm (recommended)

npm install -g infomaniak-mcp-server

From source

git clone https://github.com/YOUR_USERNAME/infomaniak-mcp-server.git
cd infomaniak-mcp-server
npm install
npm run build

⚙️ Configuration

Claude Desktop

Add to your Claude Desktop configuration file:

{
  "mcpServers": {
    "infomaniak": {
      "command": "npx",
      "args": ["-y", "infomaniak-mcp-server"],
      "env": {
        "INFOMANIAK_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

Or if installed globally or from source:

{
  "mcpServers": {
    "infomaniak": {
      "command": "node",
      "args": ["/path/to/infomaniak-mcp-server/build/index.js"],
      "env": {
        "INFOMANIAK_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

Environment Variables

🌐 HTTP Transport

The server supports HTTP transport with SSE streaming, enabling web-based MCP clients and remote connections.

Starting in HTTP Mode

# Using npx
MCP_TRANSPORT=http MCP_PORT=3000 INFOMANIAK_API_TOKEN=your-token npx infomaniak-mcp-server

# From source
MCP_TRANSPORT=http MCP_PORT=3000 INFOMANIAK_API_TOKEN=your-token node build/index.js

HTTP Endpoints

Session Modes

• Stateful (default): Maintains session state across requests. Each client gets a unique session ID returned in the Mcp-Session-Id header after initialization.
• Stateless: Each request is independent. Set MCP_STATELESS=true for serverless deployments.

Docker Deployment

FROM node:20-alpine
WORKDIR /app
RUN npm install -g infomaniak-mcp-server
ENV MCP_TRANSPORT=http
ENV MCP_PORT=3000
EXPOSE 3000
CMD ["infomaniak-mcp-server"]

# Build and run
docker build -t infomaniak-mcp .
docker run -p 3000:3000 -e INFOMANIAK_API_TOKEN=your-token infomaniak-mcp

Connecting from Web Clients

// Step 1: Initialize session
const initResponse = await fetch('http://localhost:3000/mcp', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Accept': 'application/json, text/event-stream'
  },
  body: JSON.stringify({
    jsonrpc: '2.0',
    method: 'initialize',
    params: { protocolVersion: '2025-03-26', capabilities: {}, clientInfo: { name: 'my-client', version: '1.0.0' } },
    id: 1
  })
});
const sessionId = initResponse.headers.get('Mcp-Session-Id');

// Step 2: Use session for subsequent requests
const response = await fetch('http://localhost:3000/mcp', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Accept': 'application/json, text/event-stream',
    'Mcp-Session-Id': sessionId
  },
  body: JSON.stringify({
    jsonrpc: '2.0',
    method: 'tools/list',
    id: 2
  })
});

💻 Usage Examples

Basic Usage

List all accounts

"List all my Infomaniak accounts"

Advanced Usage

Manage DNS Records

"Add an A record for www.example.com pointing to 192.168.1.100"
"Show all DNS records for mydomain.ch"
"Delete the TXT record with ID 12345 from example.com"

Create a Mailbox

"Create a new email address info@mydomain.com with password SecurePass123"

Check Infrastructure

"Show me the status of all my VPS instances"
"Reboot my VPS with ID 456"

Custom API Call

"Make a GET request to /1/account to see all account details"

🛠️ Available Tools

Account & Profile

Domain Management

Email Services

Web Hosting

Cloud Storage

Infrastructure

Certificates & Billing

Advanced

🔧 Development

Setup

git clone https://github.com/YOUR_USERNAME/infomaniak-mcp-server.git
cd infomaniak-mcp-server
npm install

Build

npm run build

Watch Mode

npm run dev

Test with MCP Inspector

INFOMANIAK_API_TOKEN=your-token npm run inspector

⚠️ API Rate Limits

⚠️ Important Note

The Infomaniak API has a rate limit of 60 requests per minute. Be mindful of request frequency when using automation.

🐛 Troubleshooting

"INFOMANIAK_API_TOKEN environment variable is required"

Ensure you've set the INFOMANIAK_API_TOKEN in your MCP client configuration.

"Infomaniak API Error (401)"

Your API token may be invalid or expired. Generate a new token from Infomaniak Manager.

"Infomaniak API Error (403)"

Your token doesn't have the required scope. Create a new token with appropriate permissions.

"Infomaniak API Error (429)"

Rate limit exceeded. Wait before making more requests.

🤝 Contributing

Contributions are welcome! Please read our Contributing Guide for details.

1. Fork the repository.
2. Create your feature branch (git checkout -b feature/amazing-feature).
3. Commit your changes (git commit -m 'feat: add amazing feature').
4. Push to the branch (git push origin feature/amazing-feature).
5. Open a Pull Request.

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🔗 Resources

• Infomaniak API Documentation
• Infomaniak Getting Started
• Model Context Protocol
• MCP TypeScript SDK

🙏 Acknowledgments

• Infomaniak for their comprehensive API.
• Anthropic for the Model Context Protocol.
• The open - source community.

Made with ❤️ for the Infomaniak and MCP community