Search for:
Why this server?
Executes tox commands to run Python tests within a project, aligning with the 'test cases' part of the query.
Why this server?
Allows LLMs to generate Azure CLI commands for resource deployment and updates, which relates to 'deploy in jenkins' if the deployment process uses Azure DevOps.
Why this server?
Can interpret golang code and judge it under DDD and Clean Architecture paradigms, implicitly relating to code quality and testability in a Jenkins pipeline.
Why this server?
Provides tools to check build statuses, trigger builds, and retrieve build logs in Jenkins, directly addressing the 'deploy in jenkins' requirement.
Why this server?
Executes system commands, which might be useful for setting up and running tests or deployments, relating to 'create test cases and deploy in jenkins'.
Why this server?
Executes whitelisted shell commands, useful for running deployment scripts in Jenkins jobs.
Why this server?
Allows penetration testing, which might involve creating specific test cases as part of a security assessment.
Why this server?
Proxy service that connects MCP clients to remote MCP servers, allowing users to use server keys from MCP.so to access remote resources without running their own server.
Why this server?
Provides a standardized interface for executing tests from various frameworks.
Why this server?
A tool to convert HTTP APIs into MCP tools. Through simple interface operation, you can quickly configure an mcp-server.