Developer · Local MCP server
No Crd
Dynamic pod spawner & proxy for ephemeral AI agent workspaces on Kubernetes without CRDs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nogoo9/no-crd- Version
- 0.18.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-12
- Updated
- 2026-08-12
- Publisher
- nogoo9 (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/nogoo9) · how
- Listed under
- Kubernetes MCP servers
- Repository
- github.com/nogoo9/no-crd
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: bunx | @nogoo9/no-crd | 0.18.0 | stdio |
How to connect No Crd
No Crd runs locally from a Node.js package published to the npm registry: @nogoo9/no-crd version 0.18.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @nogoo9/no-crd@0.18.0; the entry names bunx as the runtime. It reads these environment variables: KUBECONFIG, BASE_URL, STATELESS, TLS_CERT, TLS_KEY (secret), TLS_CA, NODE_TLS_REJECT_UNAUTHORIZED, REGISTRY_URL, TEMPLATES_DIR, BUILTIN_TEMPLATES, AUTH_ENABLED, JWT_VERIFICATION_REQUIRED, JWT_SECRET (secret), JWT_PUBLIC_KEY (secret), JWKS_URI, INTROSPECTION_ENDPOINT, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET (secret), JWT_AUDIENCE and AUTH_ISSUER; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"no-crd": {
"command": "npx",
"args": [
"-y",
"@nogoo9/no-crd@0.18.0"
],
"env": {
"KUBECONFIG": "<value>",
"BASE_URL": "<value>",
"STATELESS": "<value>",
"TLS_CERT": "<value>",
"TLS_KEY": "<secret>",
"TLS_CA": "<value>",
"NODE_TLS_REJECT_UNAUTHORIZED": "<value>",
"REGISTRY_URL": "<value>",
"TEMPLATES_DIR": "<value>",
"BUILTIN_TEMPLATES": "<value>",
"AUTH_ENABLED": "<value>",
"JWT_VERIFICATION_REQUIRED": "<value>",
"JWT_SECRET": "<secret>",
"JWT_PUBLIC_KEY": "<secret>",
"JWKS_URI": "<value>",
"INTROSPECTION_ENDPOINT": "<value>",
"OAUTH_CLIENT_ID": "<value>",
"OAUTH_CLIENT_SECRET": "<secret>",
"JWT_AUDIENCE": "<value>",
"AUTH_ISSUER": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from nogoo9 (GitHub)
| Server | Runs |
|---|---|
| MCP Server Cloud FsCloud replacement for mcp-server-filesystem - 20 tools for S3, Azure Blob, and GCS. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| NiroAI pentester for PRs - finds exploitable bugs and hands your developer agent the fix. | Local · stdio |
| Nis2 Incident Runbook LintReads your incident-response runbook and says which of the three Article 23 clocks it gets wrong. | Local · stdio |
| nittimProduction-safety audits for AI-generated code, with a fix for every finding. | Remote · HTTPLive check: ✓ handshake |
| nlqdb - analytical memory for AI agentsAnalytical memory for AI agents: a real Postgres queried in plain English over MCP. One command. | Remote · HTTPLive check: sign-in required |
| No-Code ExitsNo-code startups for sale, the deal-scoring method behind each pick, and exit stories. | Remote · HTTPLive check: ✓ handshake |
| No-Shell Agent Architect MCPTurns vague automation requests into tool stacks, prompts, QA checks, and human boundaries. | Remote · HTTPLive check: ✓ handshake |
| Nockchain MCPMoved to io.github.winter0x/nockchain-mcp. This entry is no longer updated. | Local · stdio |
| Node RuntimeThis package is intended for demonstration only. Maintained by JFrog Security. | Local · stdio |