MCP Server Kubernetes vs Just Publish
A side-by-side look at the MCP Server Kubernetes and Just Publish MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Kubernetes for cloud platforms work as a local process; choose Just Publish for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Kubernetes when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
Choose Just Publish when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
deploy, get_site_files, update_site_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,607 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View MCP Server Kubernetes | View Just Publish |
Tools & capabilities
MCP Server Kubernetes tools
No tool names declared yet. Check the project README from the listing page.
Just Publish tools 3
deployPublish a new static site (HTML/CSS/JS/images), or fully replace an existing one. Returns the live URL, a `site_id`, and an `edit_token`.get_site_filesRead a published site's files so the assistant can make a targeted edit. Requires `site_id` + `edit_token`.update_site_fileChange one or a few files in place (merge). Requires `site_id` + `edit_token`.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server Kubernetes
{
"mcpServers": {
"flux159-mcp-server-kubernetes": {
"command": "npx",
"args": [
"-y",
"mcp-server-kubernetes"
]
}
}
}
Just Publish
{
"mcpServers": {
"just-publish-2": {
"url": "https://mcp.justpublish.ai/"
}
}
}
Frequently asked questions
MCP Server Kubernetes is categorized under Cloud Platforms and uses a local stdio subprocess. Just Publish belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick MCP Server Kubernetes for cloud platforms work and Just Publish for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Server Kubernetes has no declared pricing — check the project's own site. Just Publish has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add flux159-mcp-server-kubernetes and just-publish-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Kubernetes has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 1,607 GitHub stars. Just Publish has 49/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.