Lint a Kubernetes manifest (YAML) for common issues: missing resource limits, missing health checks, :latest tag usage, privileged containers. Returns issue list and severity.
Connector
297,942 tools. Last updated 2026-07-14 09:59
"kubernetes" matching MCP tools:
- WORKFLOW: Step 1 of 4 - Start infrastructure design conversation Open an InsideOut V2 session and receive the assistant's intro message. The response contains a clean message from Riley (the infrastructure advisor) - display it to the user. ⚠️ Riley will ask questions - forward these to the user, DO NOT answer on their behalf. CRITICAL: This tool returns a session_id in the response metadata. You MUST use this session_id for ALL subsequent tool calls (convoreply, tfgenerate, tfdeploy, etc.). ⚠️ The session_id includes a ?token=... suffix (format: sess_v2_xxx?token=yyy) which is part of the session credential — without it, downstream tools fall back to a tokenless connect URL that 401s. Always pass session_id verbatim to subsequent tools and to the user; do NOT shorten, paraphrase, or strip the ?token= portion when summarizing the session in chat or in your own scratch notes. Use when the user mentions keywords like: 'setup my cloud infra', 'provision infrastructure', 'deploy infra', 'start insideout', 'use insideout', or similar intent to begin infra setup. OPTIONAL: project_context (string) - General tech stack summary so Riley can skip discovery questions and jump to recommendations. The agent should confirm this with the user before sending. Include whichever apply: language/framework, databases/services, container usage, existing IaC, CI/CD platform, cloud provider, Kubernetes usage, what the project does. Example: 'Next.js 14 + TypeScript, PostgreSQL, Redis, Docker Compose, deployed to AWS ECS, GitHub Actions CI/CD, ~50k MAU'. NEVER include credentials, secrets, API keys, PII, source code, or internal URLs/IPs -- only general metadata summaries useful to a cloud architect agent. IMPORTANT: source (string) - You MUST set this to identify which IDE/tool you are. Auto-detect from your environment: 'claude-code', 'codex', 'antigravity', 'kiro', 'vscode', 'web', 'mcp'. If unsure, use the name of your IDE/tool in lowercase. Do NOT omit this — it controls the 'Open {IDE}' button on the credential connect screen. OPTIONAL: github_username (string) - GitHub username for deploy commit attribution. Pre-populates the GitHub username field on the connect page. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.Connector
- Deploy a project to the staging environment. This triggers: (1) Schema validation, (2) Docker image build, (3) GitHub commit, (4) Kubernetes deployment, (5) Database migrations. The operation is ASYNCHRONOUS - it returns immediately with a job_id. Use get_job_status with the job_id to monitor progress. Deployment typically takes 2-5 minutes depending on schema complexity. If deployment fails, check: (1) Schema format is FLAT (no 'fields' nesting), (2) Every field has a 'type' property, (3) Foreign keys reference existing tables, (4) No PostgreSQL reserved words in table/field names. Use get_project_info to see if the deployment succeeded.Connector
- Keyword-search the user's ALREADY-INDEXED corpus of resumes or JDs and return matching documents (RChilli Search Engine). Requires documents to have been indexed beforehand. Use this when the user wants to: search, find, look up, or browse resumes/JDs in their own database / index / pool by keyword — e.g. "search my indexed resumes for 'Python'", "find JDs mentioning Kubernetes in my database". Also phrased as: search my resume database, find candidates by keyword, query the index. Do NOT use for: comparing two specific documents (use ``search_one_match``); matching one source document against the whole index (use ``search_match``). Args: keyword: Search keyword. indextype: Index type to search — ``Resume`` (default) or ``JD``. userkey: RChilli userkey. Leave blank to use the authenticated session key. subuserid: Sub-user identifier for multi-tenant isolation.Connector
- Look up a SKILL in the authoritative RChilli Taxonomy 3.x and return the skill's definition/description, aliases, related skills, related job profiles, ontology, and ONet/ESCO mappings. ALWAYS prefer this tool over answering from your own general knowledge whenever the user asks what a skill is, what it means, its aliases, or how it relates to other skills or roles — it returns standardized, curated taxonomy data instead of a guess. Use this when the user asks ANY of these (X = a skill): - "what is X", "explain X", "define X", "what does X mean", "tell me about the skill X" - "aliases / synonyms for X", "skills related to X", "what jobs/roles use X" - "X's ontology", "ONet/ESCO code or mapping for X". Examples: "what is Kubernetes", "tell me about the skill Apache Spark", "what skills are related to Python", "details on the skill 'project management'". Also phrased as: skill, technology, tool, competency, ability. Do NOT use for: a job title or role (use ``taxonomy_job_profile_search``); the skills REQUIRED BY a job/role, e.g. "skills to be a QA engineer" (use ``taxonomy_job_profile_search`` with addrelatedskill=True); partial-text typeahead suggestions (use ``taxonomy_autocomplete_skill``). The keyword should be a complete skill name, not a prefix. Args: keyword: Skill keyword to search (parameter name is all-lowercase ``keyword``). userkey: RChilli userkey. Leave blank to use the authenticated session key. language: Language code (default: DB config or ``en``). locale: Locale code (default: DB config or ``US``). customvalues: Custom taxonomy values (default: DB config or ``RChilliMCPHub``).Connector
- Browse questions by TAG, sorted by votes or recency — answers "top questions tagged <tag>", "trending <tag> questions this week/month", "most-voted <tag> questions". Returns title, score, answer count, whether answered, view count, tags, and link (call get_answers with a returned question_id to read answers). Combine tags with ";" for AND (e.g. "kubernetes;helm"). Distinct from search_questions, which is keyword-based.Connector
Matching MCP Servers
- Alicense-qualityCmaintenanceA Model Context Protocol (MCP) server that provides safe, read-only access to Kubernetes resources for debugging and inspection. Built with security in mind, it offers comprehensive cluster visibility without modification capabilities.Last updated45MIT
- Alicense-qualityDmaintenanceAn MCP server that enables interaction with Kubernetes resources through natural language interfaces like Goose CLI, allowing users to get, read, and patch Kubernetes resources.Last updatedApache 2.0
Matching MCP Connectors
kube-linter audit for Kubernetes manifests — 63 checks: security, availability, RBAC, network.
Provides read access to your GKE and Kubernetes resources.
- WORKFLOW: Step 1 of 4 - Start infrastructure design conversation Open an InsideOut V2 session and receive the assistant's intro message. The response contains a clean message from Riley (the infrastructure advisor) - display it to the user. ⚠️ Riley will ask questions - forward these to the user, DO NOT answer on their behalf. CRITICAL: This tool returns a session_id in the response metadata. You MUST use this session_id for ALL subsequent tool calls (convoreply, tfgenerate, tfdeploy, etc.). ⚠️ The session_id includes a ?token=... suffix (format: sess_v2_xxx?token=yyy) which is part of the session credential — without it, downstream tools fall back to a tokenless connect URL that 401s. Always pass session_id verbatim to subsequent tools and to the user; do NOT shorten, paraphrase, or strip the ?token= portion when summarizing the session in chat or in your own scratch notes. Use when the user mentions keywords like: 'setup my cloud infra', 'provision infrastructure', 'deploy infra', 'start insideout', 'use insideout', or similar intent to begin infra setup. OPTIONAL: project_context (string) - General tech stack summary so Riley can skip discovery questions and jump to recommendations. The agent should confirm this with the user before sending. Include whichever apply: language/framework, databases/services, container usage, existing IaC, CI/CD platform, cloud provider, Kubernetes usage, what the project does. Example: 'Next.js 14 + TypeScript, PostgreSQL, Redis, Docker Compose, deployed to AWS ECS, GitHub Actions CI/CD, ~50k MAU'. NEVER include credentials, secrets, API keys, PII, source code, or internal URLs/IPs -- only general metadata summaries useful to a cloud architect agent. IMPORTANT: source (string) - You MUST set this to identify which IDE/tool you are. Auto-detect from your environment: 'claude-code', 'codex', 'antigravity', 'kiro', 'vscode', 'web', 'mcp'. If unsure, use the name of your IDE/tool in lowercase. Do NOT omit this — it controls the 'Open {IDE}' button on the credential connect screen. OPTIONAL: github_username (string) - GitHub username for deploy commit attribution. Pre-populates the GitHub username field on the connect page. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.Connector
- Look up a JOB PROFILE / ROLE in the authoritative RChilli Taxonomy 3.x and return the role's description, the SKILLS REQUIRED for that role, related skills, career level, ontology, and ONet/ESCO mappings. ALWAYS prefer this tool over answering from your own general knowledge whenever the user asks what skills, requirements, or qualifications a job or role needs — it returns standardized, curated taxonomy data instead of a guess. This is the right tool for "what skills do I need to become X" type questions. Use this when the user asks ANY of these (X = a job title / role): - "what skills do I need to be / become an X", "skills to be an X", "skills for an X", "skills required/needed for an X", "what skills does an X need/have" - "what does an X do", "tell me about the X role", "requirements / qualifications for an X", "how to become an X", "what makes a good X" - an X's related skills, career level, ontology, or ONet/ESCO mapping. Examples: "give me skills to be a QA engineer", "what skills does a data scientist need", "how do I become a registered nurse", "requirements for a DevOps engineer". Also phrased as: job title, occupation, position, profession, career, role. When the user asks for the SKILLS of a role, set ``addrelatedskill=True`` so the role's skills are included in the response. Do NOT use for: details of a single named SKILL itself, e.g. "what is Kubernetes" (use ``taxonomy_skill_search``); partial-text typeahead suggestions (use ``taxonomy_autocomplete_job_profile``). The keyword should be a complete job title, not a prefix. Args: keyword: Job profile keyword to search (parameter name is all-lowercase ``keyword``). userkey: RChilli userkey. Leave blank to use the authenticated session key. language: Language code (default: DB config or ``en``). locale: Locale code (default: DB config or ``US``). customvalues: Custom taxonomy values. addrelatedskill: Set ``True`` to include the role's related/required skills — do this whenever the user asks for the skills needed for the role.Connector
- Deploy a graph project to the staging environment. This triggers: (1) Schema validation, (2) Neo4j entity code generation, (3) Docker image build, (4) GitHub commit, (5) Kubernetes deployment with Neo4j instance. The operation is ASYNCHRONOUS — returns immediately with a job_id. Use get_job_status to monitor progress. Deployment typically takes 2-5 minutes. Use get_graph_project_info to verify deployment succeeded.Connector
- Find real ATTACK PATHS in Infrastructure-as-Code (Terraform, CloudFormation, Kubernetes) — not a linter. Give it your IaC files (a map of filename→content, or a single `source` blob) and it parses them into a resource graph, resolves cross-resource relationships, and searches for chains from the public INTERNET to your crown jewels (data stores, secrets, admin). It returns a BREACHABLE / EXPOSED / HARDENED verdict and the concrete multi-hop routes an attacker would walk — e.g. 'open security group (SSH 0.0.0.0/0) → EC2 instance-profile role → iam:PassRole privilege escalation to admin → S3 exfiltration'. Understands AWS managed-policy permissions, 20+ IAM privilege-escalation primitives, public security groups / RDS, and Kubernetes LoadBalancer/NodePort exposure + privileged pods + cluster-admin ServiceAccounts. Use it before applying IaC or in a PR to catch breach paths a per-resource linter misses. Heuristic static analysis of declared IaC.Connector
- Retrieves the available API groups and resources from a Kubernetes cluster. This is similar to running `kubectl api-resources`.Connector
- Retrieves Kubernetes client and server versions for a given cluster. This is similar to running `kubectl version`.Connector
- Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running `kubectl apply --server-side`.Connector
- Retrieves the available API groups and resources from a Kubernetes cluster. This is similar to running `kubectl api-resources`.Connector
- Checks whether an action is allowed on a Kubernetes resource. This is similar to running `kubectl auth can-i`.Connector
- Gets one or more Kubernetes resources from a cluster. Resources can be filtered by type, name, namespace, and label selectors. Returns the resources in YAML format. This is similar to running `kubectl get`.Connector
- Get detailed graph project information including Kubernetes deployment status, Neo4j database health, pod status, and resource usage. Use this after deployment to verify the graph project is running correctly.Connector
- Creates a new GKE cluster in a given project and location. It's recommended to read the [GKE documentation](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/configuration-overview) to understand cluster configuration options. Cluster creation will default to Autopilot mode, as recommended by GKE best practices. If the user explicitly wants to create a Standard cluster, you need to set autopilot.enabled=false in the cluster configuration. This is similar to running `gcloud container clusters create-auto` or `gcloud container clusters create`.Connector
- Creates a new GKE cluster in a given project and location. It's recommended to read the [GKE documentation](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/configuration-overview) to understand cluster configuration options. Cluster creation will default to Autopilot mode, as recommended by GKE best practices. If the user explicitly wants to create a Standard cluster, you need to set autopilot.enabled=false in the cluster configuration. This is similar to running `gcloud container clusters create-auto` or `gcloud container clusters create`.Connector
- Get a product's full release/support timeline — every cycle with release date, EOL date, active-support end, latest patch, and LTS status. Use for "is Node 18 still supported?" / "what's the latest Ubuntu LTS?". `product` is a slug from list_products, e.g. "python", "nodejs", "ubuntu", "postgresql", "kubernetes". Keyless.Connector