kodekloud-mcp
Related Servers
Alternatives to kodekloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to delegate coding tasks to local Codex or Claude Code CLIs, monitor their progress, read results, continue sessions, and browse the files in user-approved project workspaces. It exposes these capabilities over Streamable HTTP through a Cloudflare tunnel or locally over stdio, so a remote or cloud client can drive agents running on the user's own machine.28 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Argo CD applications through natural language, providing tools for cluster, project, application, and resource management via stdio and HTTP transports.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to inspect and operate a Jenkins instance — discovering jobs, views, nodes, and plugins; reviewing build chains, parameters, last-build status, console output, test reports, and artifacts; and triggering builds, stopping runs, or answering pipeline inputs. It connects over stdio, SSE, or streamable HTTP with optional credentials, read-only mode, and a credential-free health endpoint.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs like Claude to securely execute Kubernetes CLI tools (kubectl, helm, istioctl, argocd) across multiple clusters through dynamic kubeconfig support, allowing natural language Kubernetes management and operations.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents such as Claude Code, Cursor, Codex, and OpenCode to query local token usage, costs, quotas, projects, and models through six strictly read-only tools. All data stays on the local machine, drawn from passively parsed session logs rather than uploaded telemetry.MIT
- AlicenseAqualityBmaintenanceConnects AI agents to New Relic observability data through the NerdGraph GraphQL API, running locally over stdio with a standard User API key. Enables NRQL queries, entity and alert lookups, log and trace investigation, deployment correlation, and metric comparisons while staying read-only by default.14Apache 2.0
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: course progress, outline, enrolled courses, active labs, certifications, learning summary, and engineer-specific resources. However, get_course_progress, get_course_outline, and get_learning_summary all touch on course completion and next-lesson guidance, creating mild overlap. Descriptions help differentiate them, so misselection is unlikely but possible.
All tool names follow a consistent snake_case verb_noun pattern using get_ or list_. The convention is predictable throughout, with no mixing of styles or vague verbs. This makes the tool set easy to scan and understand.
Nine tools is well within the ideal range for a focused learning-platform MCP. Each tool covers a distinct area: courses, progress, labs, certifications, summaries, and KodeKloud Engineer tasks. No tool feels redundant or excessive for the scope.
The surface covers the main read-only areas learners care about: enrolled courses, progress, outlines, labs, certifications, study summaries, and engineer tasks/profile/history. Minor gaps exist around lab session control (e.g., starting or stopping labs) and task submission actions, but core monitoring and discovery workflows are well supported.