Is io.github.seayniclabs/homelab-infra-mcp safe to use?

io.github.seayniclabs/homelab-infra-mcp has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under MIT.

How do I install io.github.seayniclabs/homelab-infra-mcp?

io.github.seayniclabs/homelab-infra-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.seayniclabs/homelab-infra-mcp?

io.github.seayniclabs/homelab-infra-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.seayniclabs/homelab-infra-mcp actively maintained?

io.github.seayniclabs/homelab-infra-mcp is actively maintained - last commit was 11 days ago.

io.github.seayniclabs/homelab-infra-mcp

homelab-infra-mcp

Homelab: Nginx Proxy Manager, Docker and Cloudflare DNS, with approval for every change.

GitHub PyPI

No known CVEs

MIT license

Actively maintained

Last commit 11d ago

Works with most clients

Transport: stdio, sse, http

0 tools

Grade F

MCPpedia last refreshed this data 22h ago

Edit this pageView history

io.github.seayniclabs/homelab-infra-mcp is an MCP server that homelab: Nginx Proxy Manager, Docker and Cloudflare DNS, with approval for every change. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 59/100 on MCPpedia's security, maintenance and efficiency rubric.

Developer Tools Cloud

Step 1

Install in your client

Config is the same across clients - only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "homelab": {
      "env": {
        "HOMELAB_DNS_ZONE_ID": "your-zone-id",
        "HOMELAB_PROXY_EMAIL": "admin@example.com",
        "HOMELAB_DNS_API_TOKEN": "your-cloudflare-token",
        "HOMELAB_PROXY_PASSWORD": "change-me"
      },
      "args": [
        "homelab-infra-mcp==2.1.1"
      ],
      "command": "uvx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-seayniclabs-homelab-infra-mcp)](https://mcppedia.org/s/io-github-seayniclabs-homelab-infra-mcp)

Read me

What io.github.seayniclabs/homelab-infra-mcp does

Homelab: Nginx Proxy Manager, Docker and Cloudflare DNS, with approval for every change.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.

uvx 'homelab-infra-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories - click any category to see the underlying evidence.

Score breakdown

59/100across 5 weighted dimensions

How we score →

0255075100

−41

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked homelab-infra-mcp against OSV.dev.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience - it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.seayniclabs/homelab-infra-mcp safe to use?: io.github.seayniclabs/homelab-infra-mcp has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under MIT.
How do I install io.github.seayniclabs/homelab-infra-mcp?: io.github.seayniclabs/homelab-infra-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.seayniclabs/homelab-infra-mcp?: io.github.seayniclabs/homelab-infra-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.seayniclabs/homelab-infra-mcp actively maintained?: io.github.seayniclabs/homelab-infra-mcp is actively maintained - last commit was 11 days ago.

Similar servers

Others in developer-tools / cloud

View all →

XcodeBuildMCP97

XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.

6.6k 2

Supabase MCP Server96

Manage Supabase projects — databases, auth, storage, and edge functions

3.0k 4

Mcp Gitlab96

MCP server for using the GitLab API

2.1k 12

Codebase Memory Mcp95

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

48.6k 6

MCP Security Weekly

Get CVE alerts and security updates for io.github.seayniclabs/homelab-infra-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Developer Tools Cloud

Step 1

Install in your client

Config is the same across clients - only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "homelab": {
      "env": {
        "HOMELAB_DNS_ZONE_ID": "your-zone-id",
        "HOMELAB_PROXY_EMAIL": "admin@example.com",
        "HOMELAB_DNS_API_TOKEN": "your-cloudflare-token",
        "HOMELAB_PROXY_PASSWORD": "change-me"
      },
      "args": [
        "homelab-infra-mcp==2.1.1"
      ],
      "command": "uvx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-seayniclabs-homelab-infra-mcp)](https://mcppedia.org/s/io-github-seayniclabs-homelab-infra-mcp)

Read me

What io.github.seayniclabs/homelab-infra-mcp does

Homelab: Nginx Proxy Manager, Docker and Cloudflare DNS, with approval for every change.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.

uvx 'homelab-infra-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

Homelab

Made by Seaynic Labs. Need tools like this built around your own systems? We do that.

Homelab is an MCP server that lets an AI assistant manage Nginx Proxy Manager proxy hosts, Docker containers and Cloudflare DNS records from one place. It covers the path from a container to a public web address. One call, expose_service, checks the container, adds the DNS record and the proxy host, and shows the plan before anything changes. Four more optional modules cover Uptime Kuma, Cloudflare Tunnel, AdGuard Home and Authentik.

It is a bundle: one server made of modules, plus skills that teach the assistant the workflows. You switch on the modules you use. New modules arrive switched off, so an update never changes what your assistant can do until you choose to.

Audience: self-hosters running a homelab.

Module	What it does	Status
`proxy`	Nginx Proxy Manager: proxy hosts, redirections, SSL certificates, access lists	On by default
`docker`	Containers, images and volumes through the local Docker socket or Portainer	On by default
`dns`	Cloudflare DNS zones and records, and BIND export	On by default
`home_assistant`	Entities, automations, scripts and system info in Home Assistant	Off by default, turn on with `HOMELAB_HOME_ASSISTANT_ENABLED=true`
`uptime`	Uptime Kuma monitors: list and read status (read only)	Off by default, turn on with `HOMELAB_UPTIME_ENABLED=true`
`tunnel`	Cloudflare Tunnel routes: list, add and remove	Off by default, turn on with `HOMELAB_TUNNEL_ENABLED=true`
`dns_filter`	AdGuard Home: filter status, query log and filter rules	Off by default, turn on with `HOMELAB_DNS_FILTER_ENABLED=true`
`sso`	Authentik: list applications, create a proxy provider and application for one host	Off by default, turn on with `HOMELAB_SSO_ENABLED=true`

The core tools are always on: homelab_modules, homelab_health, expose_service, teardown_service, service_status, infrastructure_overview and diagnose_service.

Homelab works with any MCP client: Claude Desktop, Claude Code, Cursor, VS Code, Sonique, Hermes, OpenClaw and others. It runs on your own machine and keeps no data of its own. It talks only to the services you configure.

Install

Homelab needs Python 3.11 or newer. With uv there is nothing to install ahead of time. Pin the version so updates arrive only when you choose them:

uvx homelab-infra-mcp==2.1.1 --version

Or with pip:

pip install homelab-infra-mcp==2.1.1

Upgrading from 2.0? Version 2.1 has no breaking changes. The four new modules are off by default. Read the 2.1.0 section of CHANGELOG.md.

Upgrading from 1.x? Version 2.0 changed the tool names and the environment variable names. Read the migration table in CHANGELOG.md first.

Quick install

Add the server to your MCP client (see Add it to your MCP client), set the variables for the modules you use, and restart the client. Then ask the assistant to call homelab_modules. The response lists each module, whether it is on, and which settings are missing.

Doctor

Run homelab-infra --doctor in a terminal before you start, and after any settings change:

homelab-infra --doctor

The doctor checks each enabled module's settings and reachability, the Docker socket access, and the TLS check. It prints a FIX line for each problem and exits with status 1 when something needs fixing.

Settings

Set these as environment variables in your MCP client's config, or put them in a config file (see below). You only need the settings for the modules you use. Homelab starts without any of them and tells you what is missing when you call a tool.

Variable	Module	What it is
`HOMEL

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories - click any category to see the underlying evidence.

Score breakdown

59/100across 5 weighted dimensions

How we score →

0255075100

−41

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked homelab-infra-mcp against OSV.dev.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience - it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.seayniclabs/homelab-infra-mcp safe to use?: io.github.seayniclabs/homelab-infra-mcp has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under MIT.
How do I install io.github.seayniclabs/homelab-infra-mcp?: io.github.seayniclabs/homelab-infra-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.seayniclabs/homelab-infra-mcp?: io.github.seayniclabs/homelab-infra-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.seayniclabs/homelab-infra-mcp actively maintained?: io.github.seayniclabs/homelab-infra-mcp is actively maintained - last commit was 11 days ago.