# 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 authentication, so homelab users can connect many AI tools to Claude as. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/8922/mcp-octopus

## Description

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.

## Health score

46/100 (Fair), based on 3 of 4 factors.
- Maintained: 77 (last commit 2 days ago)
- Popular: 6 (1 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- Unraid: https://ca.unraid.net/apps/mcpopus-1r76tk80gdxres?q=mcpopus
- GitHub: https://github.com/Poag/mcpopus

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/8922/mcp-octopus), the self-hosted and open-source app directory.
