MCP Octopus

MCP Octopus is a self-hosted Model Context Protocol (MCP) host that serves a separate endpoint for each installed plugin, with built-in OAuth 2.1…

  • AI
  • Productivity
  • Tools & Utilities
MCP Octopus is a self-hosted Model Context Protocol (MCP) host that serves a separate endpoint for each installed plugin, with built-in OAuth 2.1 authentication, so homelab users can connect many AI tools to Claude as custom connectors.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

46/100 Fair

Maintained
77last commit 2 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
1
Open issues
0
Last commit
2026-11-19
License
MIT
Activity
rising

Checked 2 days ago - source: GitHub (Poag/mcpopus)

Resources & Compatibility

Requirements not published yet.

Checked 2 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Reverse proxy Put a reverse proxy in front of port 8080. Keep the admin port 8081 on your local network only. source
  • Setup, login, and adding plugins Run it behind your own reverse proxy. Account setup uses the built-in OAuth 2.1 server for a single owner (password plus authenticator code). Add connectors by installing plugins from git repositories in the admin UI; plugins can be reloaded at run time, so no image rebuild is needed. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which port should be proxied publicly for MCP Octopus?

Put a reverse proxy in front of port 8080. Keep the admin port 8081 on your LAN.

What OAuth support is built into MCP Octopus?

It includes an OAuth 2.1 authorization server for one owner. It supports password and TOTP, PKCE S256, dynamic client registration, and refresh rotation.

Can an MCP Octopus OAuth token be used across multiple plugins?

No. A token is bound to one plugin and rejected on every other.

What policies can be set per plugin?

Each plugin can be read-only by default. You can configure tool allow and deny lists, rate limit, output cap, and audit log.

Answers sourced from github.com

Community

No community discussions collected yet.