GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
제작자가 쓴 설명(영어 원문)
Manage Infomaniak DNS, mail and VPS apps through OAuth, with live official documentation.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://infomaniak-mcp.com/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http infomaniak https://infomaniak-mcp.com/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"infomaniak": {
"url": "https://infomaniak-mcp.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"infomaniak": {
"type": "http",
"url": "https://infomaniak-mcp.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://infomaniak-mcp.com/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
서버가 도구 목록을 보여 주기 전에 로그인을 요구해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 9일 점검
레지스트리 이름이 GitHub 계정 leonhoulier 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
353ms 만에 응답(HTTP 401)
OAuth 로그인을 지원한다고 밝혀서, AI 앱이 로그인 화면으로 안내해 줘요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.3.6)은 10일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: GitHub, Desktop Commander, Cloudflare MCP
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요