Why this server?
Provides a Model Context Protocol server that enables programmatic interaction with DefectDojo, a vulnerability management tool, for managing findings, products, and engagements.
Why this server?
Wraps the Azure CLI, allowing LLMs to manage Azure resources, fix errors, and address security issues by generating and executing Azure CLI commands.
Why this server?
Enables integration with GitHub Enterprise API, allowing users to access repository information, manage issues, pull requests, workflows, and other GitHub features through Cursor.
Why this server?
Enables dynamic configuration of OpenTelemetry Collectors, allowing users to add, remove, and configure receivers, processors, and exporters through MCP tools.
Why this server?
Integrates GitLab merge request analysis with Confluence documentation, allowing users to fetch merge request details, analyze code changes, and store analysis results in Confluence pages.
Why this server?
An integration tool that enables AI assistants like Claude to directly access and interact with Bitbucket repositories, pull requests, and code without requiring copy/paste operations.
Why this server?
Provides a convenient API for interacting with Azure DevOps services, enabling AI assistants and other tools to manage work items, code repositories, boards, sprints, and more through a standardized interface.
Why this server?
Allows LLMs to interact with Azure CLI for listing, creating, updating, and deleting resources, as well as fixing errors and security issues based on logs and security assessments.
Why this server?
Enables IDE access to Supabase databases with SQL query execution, schema management, Auth admin operations, and built-in safety controls for preventing accidental destructive actions.