"How to query a MySQL database" matching MCP servers:

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

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.

Enables AI assistants to summarize Playwright test runs, identify flaky tests, heuristically triage failures, generate Playwright test stubs, and retrieve recent GitHub CI status through MCP tool calls.

Enables scanning Python repos for dead code and automatically drafting a branch + PR for the safe subset (unused single-name imports) after running the repo's full test suite. All other findings are reported without modification, and a human always merges.

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.

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.

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 Model Context Protocol server that enables AI assistants to interact with Azure DevOps services, allowing users to query work items with plans to support creating/updating items, managing pipelines, handling pull requests, and administering sprints and branch policies.

Enables AI agents to deploy, manage, and configure web applications on sota.io, including project creation, deployment, environment variables, custom domains, and rollbacks.

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 AI agents to query summit registration and forum analytics, review code changes for risks, run fixed quality gates, and perform audited, permission-controlled commits and deployments with minimal access and human approval.

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.

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

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.

Zero-config data quality monitoring as MCP tools. Profiles a warehouse (Postgres, BigQuery, Snowflake, MySQL, DuckDB), detects anomalies, and gates CI — read-only with the connection resolved server-side, never via the model.

Enables AI assistants to interact with TrafficMorph for load-testing and CI-failure triage, including run management, profile lifecycle, and domain verification through natural language.

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

Enables AI assistants to query and manage Azure DevOps projects, boards, work items, repos, pull requests, and pipelines while enforcing governance boundaries such as access modes, project scoping, protected projects, delete gating, and typed confirmations.