"Automating Jira or Trello ticket creation using MCP" matching MCP servers:

Provides comprehensive access to Jira Cloud and Data Center instances for managing issues, epics, and attachments with AI-optimized data cleaning. It supports relationship tracking and dual transport modes via STDIO and Streamable HTTP.

Integrates Jira and GitLab to enable AI agents to seamlessly manage issues, create branches, and automate SRE workflows from issue detection to fix deployment. Features AI-powered analysis for intelligent code generation and comprehensive automation across both platforms.

An MCP server for issue-driven GitLab development, automating requirement analysis, issue creation, branching, coding, merge requests, and issue updates.

An MCP server that enables Claude to create and manage TestRail test cases directly from Jira or Azure DevOps user stories. It provides tools for section management and automated test case creation with built-in format enforcement and traceability links.

Enables seamless interaction with Azure DevOps for managing Git repositories, branches, and pull requests through natural language. It also supports automating and monitoring pipelines while providing secure, type-safe operations within MCP-compatible clients.

Mneme exposes a governed Decision Index so MCP clients can propose candidate architectural decisions and query decision state, applicability, and traceability. Proposals remain non-authoritative: accepting or activating protections stays under explicit human control.

Agent-readiness scorecard for any MCP server: protocol checks, 0-100 score and actionable findings.

Enables AI agents to deploy static files and get live HTTPS URLs instantly, with support for custom domains and data residency.

Enables coding agents to read Squally CI data, including test results, flakiness, and failure diagnostics.

Checks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.

Model Context Protocol (MCP) server for GitLab — exposes 1006 GitLab REST & GraphQL API operations as MCP tools (42 meta-tools / 57 enterprise), 24 resources, 38 prompts, and 17 completion types for AI assistants. Written in Go, single static binary, stdio and HTTP transport.

Connects AI coding assistants to Gaffer test history and coverage data to analyze project health, debug failures, and identify untested code areas. It enables tools to track test stability, cluster failures by root cause, and monitor code coverage trends across projects.

A security-focused MCP server for self-hosted n8n Community Edition, providing 44 bounded tools to manage workflows, nodes, executions, credentials, tags, and more via the n8n Public API.

Enables AI agents to deploy HTML and pull reviewer comments via the briefroom CLI without spawning shells.

Enables AI coding tools to scaffold, build, and deploy Node.js or Python apps to Varity with a single command, automatically provisioning databases and backend services.

MCP server with the watch_ci tool that polls GitHub Actions until a commit's CI run finishes, then returns the outcome and failed log tail in one call.

An MCP server for managing Modal — apps, containers, volumes, and secrets — and for deploying & running Modal apps directly from Claude Code and other MCP clients.

A Model Context Protocol server for checking package versions and metadata across multiple package managers including npm, PyPI, Maven, NuGet, RubyGems, Crates.io, and Go modules.

CP server for Harbor Registry — projects, repositories, artifacts, storage reports, cleanup candidates. Works with any Harbor 2.x instance.

MCP server for publishing HTML or Markdown to a live hosted URL via htmldrop. Provides tools to publish, list, and delete hosted sites, with remote OAuth and API token authentication.