GreenNode MCP Server
OfficialProvides tools for managing Kubernetes resources (clusters, workloads, etc.) within the GreenNode (VNG Cloud) infrastructure, enabling AI assistants to perform cluster operations and resource management.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GreenNode MCP Serverlist all virtual servers in project pro-xxxx"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GreenNode MCP
A monorepo of MCP (Model Context Protocol) servers for GreenNode products,
organized as a uv workspace.
Each product is an independent project under src/, sharing the greennode
Python namespace.
Servers
Project | Package | Description |
| Shared core (config/profile loading, IAM auth, HTTP client with retry/401, validators, discovery cache) — product servers import it instead of copying plumbing. | |
| 39 tools + 3 prompts for managing VKS (GreenNode Kubernetes Service): clusters, node groups, resource discovery (name→ID), quota, on-demand creation guides, and in-cluster Kubernetes resources. EKS-style |
More servers will be added as sibling projects under src/.
Related MCP server: VergeOS MCP Server
Layout
greennode-mcp/
├── pyproject.toml # uv workspace root (members = ["src/*"])
├── src/
│ ├── mcp-core/ # shared core (greennode.mcp_core)
│ └── vks-mcp-server/ # one product = one independent project
│ ├── pyproject.toml
│ ├── greennode/
│ │ └── vks_mcp_server/
│ └── tests/
└── docs/Getting started
# Install all workspace members into a shared environment
uv sync
# Run a specific server
uv run vks-mcp-serverAdding a new product server
uv run python scripts/new_server.py <product> # e.g. vdbScaffolds src/<product>-mcp-server/ from templates/new-server (working
example tool + tests + Dockerfile, conventions baked in), registers it with
release-please, and prints the remaining steps. CI (lint/test/build) discovers
the new package automatically. Agent guidance lives in .claude/skills/
(new-mcp-server, release-mcp) and the tiered CLAUDE.md files (repo root =
monorepo conventions; each package has its own).
See each project's own README for configuration and usage.
Note: Create/update tools use typed Pydantic request bodies (structured DTOs) for better code-mode support and self-documenting schemas.
Diagnostics: --auth-debug (temporary, opt-in)
--auth-debug (env GRN_MCP_AUTH_DEBUG=1) makes the HTTP transport log a
redacted summary of every inbound request and expose an unauthenticated
GET /whoami that echoes the same summary. It is meant for measuring what an
upstream (e.g. the MCP Gateway) actually sends — token scheme, JWT header
(alg/kid), allow-listed claims (iss/aud/sub/scope/...), and any
X-GreenNode-* / X-Forwarded-* identity headers.
It never verifies signatures and never logs the full token (only a
6-char prefix + length). It is off by default and must not be enabled in
production. It is orthogonal to --auth-mode and can be combined with any mode.
Development
# Run a product's tests
cd src/vks-mcp-server && uv run pytest tests/ -vConventions for adding tools and new servers live in CLAUDE.md.
License
Apache-2.0. See LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vngcloud/greennode-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server