Best for
- Teams already using K8M to manage Kubernetes clusters who want unified MCP server management
- Users who need to connect MCP servers over SSE and want a visual on/off control
K
K8M MCP 服务器管理
Community
Visually manage MCP servers and their tools inside K8M
GitHub source repository ↗
44FMRS · D
This page is K8M's MCP server management UI; its scope is visual CRUD plus enable/disable control for servers and tools rather than shipping the MCP tools themselves. It is clearly scoped and straightforward, suitable for users already on K8M connecting over SSE, but the default credentials and automatic registration deserve security and permission attention.
This is the MCP runtime server management page in K8M, a lightweight, cross-platform Mini Kubernetes AI Dashboard. The page lets you add, edit, enable/disable, and delete MCP servers, and inspect the tools each server exposes along with their input parameters. Per the page notice, once an MCP server is enabled it is registered and used automatically during LLM conversations; only SSE-type servers are supported at this time. K8M itself can also act as an MCP Server for other LLM software, with multi-cluster permissions aligned to MCP calls.
Setup
- Deploy and start K8M as described in the repository (for example via docker-compose, default port 3618).
- Log in with the default username k8m and password k8m (change the password and enable two-factor authentication after going live).
- Open the MCP runtime page and click "Add Server".
- Fill in the server name and server URL (only SSE type is currently supported) and toggle "Enabled" as needed.
- After saving, you can enable or disable the server at any time from the list, and click "Tools" to view its tools and input parameters.
Fit and risk
Not for
- Users who need non-SSE MCP server types (the page states these are not supported)
- Users without a K8M deployment who just want to use a single MCP server standalone
Required permissions
- Access to the K8M admin console (login required)
- Server read/write and delete API permissions needed to manage MCP servers
- Once an MCP server is enabled, LLM-driven calls execute with the caller's own cluster permissions
Risks and side effects
- Enabled MCP servers are registered automatically in conversations and may be invoked by the model
- The server URL is user-supplied; pointing it at an untrusted remote service risks data exposure
- Deleting or bulk-deleting server configurations is not easily reversible
- The default credentials k8m/k8m create a clear unauthorized-access risk if not changed promptly
Troubleshooting
- If adding fails, first confirm the server type you entered is SSE
- If a server does not take effect in conversations, check whether its "Enabled" switch is on
- If no tools appear, click "Details" in the Tools column and verify the server URL is reachable
- If APIs return errors, verify your login session and admin permissions
Use cases
Register and manage multiple MCP servers centrally in K8M
Enable or disable an MCP server on demand
Inspect the tools and input parameters an MCP server provides
Automatically register and use enabled MCP servers during LLM conversations