"Connecting to a Local MySQL Database" matching MCP servers:

An MCP server that adds engineering discipline to AI-assisted development, enforcing evidence-gated TDD, security review, backup strategy, and deployment generation to turn AI-generated code into production-ready software.

Converts Jenkins declarative pipelines into GitHub Actions workflow YAML files, facilitating migration from Jenkins to GitHub Actions CI/CD.

A local MCP server that connects Claude Desktop, Claude Code, and Claude Chat to your Azure DevOps organization, enabling querying work items, reviewing pull requests, triggering pipelines, searching code, managing test plans, and updating wikis using plain language.

A multi-language testing automation server that enables AI assistants to discover, plan, and execute tests across six major programming languages. It provides comprehensive tools for repository scanning, automated test execution, and detailed coverage reporting.

Enables inspecting local Git repositories and automating delivery tasks such as status checks, diffs, commits, pull requests, and deployments using git and GitHub CLI.

Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link. Runs locally over stdio from the @drop2run/mcp npm package, or hosted at https://mcp.dropto.run/mcp for chats that connect by URL.

Connects AI tools to GitHub and local git repositories, enabling natural language management of issues, PRs, code analysis, and workflows.

Record an agent's MCP tool-call workflow once, replay it deterministically for zero tokens, and get a receipt — a snapshot-testing and deterministic-execution layer for Agent Skills.

Enables AI coding tools to validate local projects and publish or update applications to Bedengan App Hub via API, with automated checks and live deployment without manual approval.

Automates the full setup and deployment of Ballerina + Apache ActiveMQ integrations inside a WSO2 Integrator workspace, from broker validation to a runnable BI-low-code-ready project.

A Model Context Protocol server that monitors shadow-cljs builds and provides real-time build status updates for ClojureScript projects, allowing LLMs to verify build status after making code changes.

A read-only Model Context Protocol server that converts local Git changes and JUnit XML reports into traceable release evidence, risk findings, and a rollback checklist.

Publishes normalized release notices to a configured webhook via MCP, with built-in validation, deterministic dry-run mode, and a clear boundary for authority gates.

Analyzes database migrations for risks like lock contention and data loss before they run. Supports Flyway and Liquibase formats, providing risk scores and rollback generation.

An MCP server that scaffolds full-stack projects with consistent structure, Docker setup, CI/CD pipelines, and database configuration.

Enables deployment and management of applications on the Citizen platform from git repositories or local files. It allows AI assistants to monitor deployment logs, handle authentication, and automatically fix build errors using intelligent error analysis.

Enables coding agents to upload local .apk or .ipa builds and receive tester install links without leaving the editor.

Developers are constantly feeding context files to AI tools like Cursor, Windsurf, Copilot Workspace, and Claude Code. If your agent doesn't understand your real database schema, it writes code that fails in production. LintBase acts as the bridge. It connects directly to your database, reads the ground truth of your live documents, and generates structured context optimized for AI. 🤖 Stops AI

Autonomous coding pipeline exposed as an MCP server: plan, dispatch, review, and merge software stories through worktree-isolated agents. A frontier model (Claude) handles judgment — planning, review, risk adjudication — while a local model does the implementation, gated by TDD and a merge-time test rerun on the rebased branch.

Blocks unsafe PostgreSQL migrations before an AI agent writes or runs them. check_before_apply returns a pass/fail gate; reads the real Postgres parser, classifies the lock each statement takes, checks 112 safety rules. Runs offline, no database required.