GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Beschreibung vom Entwickler (englisches Original)
Manage Infomaniak DNS, mail and VPS apps through OAuth, with live official documentation.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://infomaniak-mcp.com/mcpFühre das in deinem Terminal aus
claude mcp add --transport http infomaniak https://infomaniak-mcp.com/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"infomaniak": {
"url": "https://infomaniak-mcp.com/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"infomaniak": {
"type": "http",
"url": "https://infomaniak-mcp.com/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://infomaniak-mcp.com/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Der Server verlangt eine Anmeldung, bevor er seine Tools auflistet.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 9. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto leonhoulier bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Antwort in 353 ms (HTTP 401)
Gibt OAuth-Anmeldung an, damit deine KI-App dich zum Einloggen weiterleiten kann
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.3.6) kam vor 10 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: GitHub, Desktop Commander, Cloudflare MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Use your AI coding tools with the Infomaniak services you already run. Independent, unofficial and open source. Built by Léon Houlier.
[Try the hosted pilot](https://infomaniak-mcp.com) · Plugin downloads · Contribute · API reference · Privacy · Cookie policy
https://infomaniak-mcp.com/mcp
For Claude Code:
claude mcp add --transport http infomaniak https://infomaniak-mcp.com/mcp
Then run /mcp in Claude Code and complete browser sign-in. For other clients, use the setup guides. Each customer enters their own Infomaniak token on a private page and approves one account. Never paste a token into chat or a GitHub issue. Native client onboarding is still being qualified.
Ask: “Show my Infomaniak services.”
| Capability | Hosted service today |
|---|---|
| Discovery | Approved account/product inventory and resource-name resolution |
| DNS | Records, audit, propagation and expiry; record create/update/delete in consented domains |
| Consented mailbox metadata, aliases and forwarding; supported settings changes | |
| VPS apps | Customer-owned runner, pinned stateless Dockerfile deployment, health, requested logs and retained-image rollback |
| Official documentation | Live help search in seven languages, live developer index, current guides and API references |
| Changes | Read/write offered during setup; read-only available; each exact write needs client confirmation when supported, with browser fallback |
The service does not expose mailbox content, generic HTTP execution, arbitrary shell commands, purchasing or general VPS lifecycle writes. Catalogue metadata is documentation, not executable coverage. Provider tokens are encrypted at rest; the operator holds the encryption key and can use them for API requests.
Not affiliated with or endorsed by Infomaniak.
Use https://infomaniak-mcp.com/mcp with the client's OAuth flow. Every customer connects their own Infomaniak token privately, chooses an account and selects resources. Customers do not need a local runtime or their own server. An optional VPS deployment needs a paired customer-owned runner. Existing grants never expand automatically; explicit read-only remains authoritative.
See the API and current capabilities, client qualification evidence and privacy policy. Native client qualification varies; an endpoint or local test pass is not proof of every client workflow.
The hosted service, plugin packages and runner are released from this source. See versioned releases for the source, plugin ZIPs and checksums. The runner is also available at Downloads.
A thin hosted plugin lives under plugins/infomaniak. It bundles private connection guidance and reusable Infomaniak workflows with the existing remote MCP. Portable Agent Plugins manifests target compatible hosts, with a Claude compatibility package alongside them. No provider token is stored in the plugin package.
Download the public plugin packages, or build them with node scripts/package-plugin.mjs. Claude Code can install from this repository:
claude plugin marketplace add leonhoulier/infomaniak-ai
claude plugin install infomaniak@infomaniak-mcp
Version 0.3.5 is published in the MCP Registry. The entry points to the hosted OAuth endpoint; customers do not need an npm package. Claude is submitted for review, Cursor has received the publisher application, and OpenAI has an uploaded draft. These are not approved directory listings. Repository installation and public downloads are available separately. See the distribution plan for current submission routes, native qualification, review materials and discovery priorities.
To try the browser experience privately, run npm run preview and open http://127.0.0.1:8790. It uses demo data by default. See testing the hosted experience.
Every customer uses their own credentials. With only INFOMANIAK_API_TOKEN (or its private _FILE source), the server starts a read-only discovery edition: accounts, products and the full public catalogue. No author account, backend, private policy or server hosting is needed for that starting point. It exposes six tools and cannot plan or execute writes.
A scoped policy enables resource-level reads and the controlled write lifecycle. The original backend configuration remains supported separately.
Requires Node.js 22.13+. No server hosting is required. From this checkout:
npm ci --ignore-scripts
npm run build node dist/server.js setup
Choose your client. Claude Code and Claude Desktop use their private plugin settings; VS Code uses a native password prompt. Codex and Cursor use hidden terminal entry with a private local credential file, outside your project. Setup explains where your token goes before asking for it. Never paste it into chat.
For Claude Desktop, build the extension with npm run package:desktop, then open artifacts/infomaniak-ai-0.2.0.mcpb. Dependencies are included; the bundle is unsigned and native installation still needs client validation.
Your first question:
Show my Infomaniak services. If I have several accounts, let me choose one.
Preview any connection with node dist/server.js setup --client vscode --dry-run. See the onboarding guide for each client, token permissions, rotation and removal. No npm or marketplace release is available yet.
The JSON API exposes scoped reads and plan, execute, cancel and reconciliation routes. The hosted beta limits writes to a disposable TXT name and uses encrypted plans with native client confirmation when form elicitation is negotiated, or browser approval otherwise. The separate policy edition retains its configured resource grants and human key. There is no API approval endpoint. See the write API reference.
The simple connection above provides account and product discovery. To inspect individual resources or enable reviewed changes, configure a separate scoped policy. The controlled edition uses Node's SQLite API.
Initialize a new private directory using your actual account ID. Replace the capitalized placeholders; omit product options you do not need:
node dist/admin.js init \
--directory "$HOME/.config/infomaniak-ai" \ --account ACCOUNT_ID \ --zone example.com \ --dns-source _infomaniak-ai-test \ --mail-hosting MAIL_HOSTING_ID \ --mailbox MAILBOX_NAME
This writes a private policy, a client connection token and a separate human approval key. Their values are never printed. All writes and writable resource grants start disabled. Existing installations are never overwritten.
Configure the provider token in the client's secret store or in INFOMANIAK_API_TOKEN. Alternatively set INFOMANIAK_API_TOKEN_FILE to an absolute regular secret-file path with mode 0600. Do not configure both sources, or paste credentials into a conversation.
For a generic MCP client, use command node with arguments:
/absolute/path/to/infomaniak-ai/dist/server.js
--config /absolute/path/to/private/access.local.json
The default local policy also starts the approval interface at localhost:8787/approvals. Its human key belongs in the browser/interactive human terminal, outside the AI client's configuration.
node dist/server.js --config /absolute/path/to/access.local.json --doctor
Doctor checks configuration and optional backend integrity, without provider calls.
The policy-driven edition exposes ten tools:
| Tool | Purpose |
|---|---|
infomaniak_status | Coverage, configured adapters and connection policy |
infomaniak_search | Relevant operations and reviewed schemas on demand |
infomaniak_catalogue | Paginated public metadata by product/method |
infomaniak_read | A reviewed read within account/resource grants |
infomaniak_plan | Persist a preview; no provider mutation or approval |
infomaniak_execute | Execute an independently approved exact plan once |
infomaniak_operation | Status or read-only reconciliation |
infomaniak_cancel | Cancel before execution starts |
infomaniak_docs_search | Current official help guides or live API index |
infomaniak_docs_read | Fetch a current official guide or API reference |
There is no MCP approval tool or generic HTTP/shell executor. Search can return disabled catalogue entries with the reason they cannot execute.
Reviewed operations carry Infomaniak-specific notes in search results: which ID is which, the . zone apex, MX priority inside the target, UTC expiry dates, what the forwarding flags mean. The skill has the full table.
Every edition includes live official documentation search and reading. Use infomaniak_docs_search with public topic terms (for example, VPS Lite SSH), then infomaniak_docs_read with a returned URL. Set source: "api" to search the live developer index rather than the bundled operation catalogue. Results include source URLs, retrieval times and explicit pagination.
When an API capability is missing, agents can follow the official Manager guide using their own authorized browser or computer tools. Documentation access does not control a browser or grant permission to change resources. See documentation access.
| Operation | What it checks |
|---|---|
domains.expiry | Registration expiry in UTC, days left, expired/expiring/ok |
dns.audit | SPF (missing, duplicate, +all, Infomaniak include), DMARC, DKIM delegation, MX, apex CNAME, low TTLs |
dns.propagation | Google, Cloudflare and Quad9 answers for one name, compared with the zone; a failed lookup is disagreement |
They read the stored zone and public resolvers. They are not mail delivery or signing tests.
Start with explicitly disposable resources. An operator must grant all of:
operations list.Nur der Anfang wird gezeigt; den Rest findest du im Repo