"Understanding Prompts or Prompt Engineering" matching MCP servers:

A modular MCP server that extends GitHub Copilot's capabilities through intelligent context compression and dynamic model routing for long-lived coding sessions.

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.

Enables code-review gating by converting a git diff into a typed verdict with safety probabilities, severity, and recommended actions for auto-merge or human review.

Deploys and manages projects on Swigs Cloud from any MCP client, turning folders or git repositories into live HTTPS sites in about two minutes.

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

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.

Checks whether software dependencies (npm packages, GitHub Actions, MCP servers, Docker images) are alive, dormant, abandoned, archived, or deleted using dated observations from lastseen.dev.

Enables agents and CI pipelines to audit MCP servers and agent tool-chains by statically scanning repositories, local checkouts, tools/list exports, or live endpoints for risks such as destructive actions without confirmation, mismatched safety annotations, injection surfaces, credential or PII exposure, and unguarded command, path, or URL sinks. All checks are read-only and never execute the scanned code or call tools/call.

Enables management of Railway.app infrastructure through natural language, including deploying services from GitHub repos or Docker images, managing environment variables, monitoring deployments, and configuring networking and volumes.

Lets MCP clients such as Claude or ChatGPT find the pull requests waiting on your review, read their details and changed files, check CI status, post comments, and submit approve, request-changes, or comment reviews. It runs locally over stdio with a personal token or as a remote server with its own OAuth 2.1 authorization server (PKCE, dynamic client registration, per-client consent, and refresh-token rotation) so GitHub is only used to sign the user in.

MCP server for agent-controlled deployment on Pier, exposing 14 tools mapped to Pier REST API endpoints for managing deployments via stdio or HTTP.

Enables AI coding assistants to distribute iOS and Android builds to BetaDrop testers, manage share links, track releases, and manage API tokens entirely through natural language prompts.

Enables AI assistants to manage and operate Venelx CI/CD pipelines through the Venelx REST API, including listing projects, triggering builds, checking status, tailing logs, accessing artifacts and workers, and diagnosing signing or GitHub access.

MCP server that runs Flyway repair + migrate across multiple database projects for QA or Development environments.

A local MCP server that exposes Blacksmith.sh's usage and cost data, enabling queries for CI spend through agents, alerts, or dashboards.

Enables real-time assessment of GitHub repository health by exposing tools and resources for repository metadata, open issues, recent commits, and GitHub Actions workflow runs, plus prompts for health reports and issue triage.

Enables managing GitHub Actions workflows through MCP, including listing and inspecting workflows, triggering workflow_dispatch and repository_dispatch events, and monitoring or canceling workflow runs.

MCP server for Codecov that provides tools to get commit coverage totals and prompts to suggest tests to write.

A specialized MCP server for QA engineering. It provides tools for user story analysis, test strategy, BDD/Gherkin scenarios, contract testing, integration tests, performance plans, security checklists, and CI/CD pipeline generation, accessible from any MCP-compatible IDE or client.

Self-hosted coding agent that runs Claude Code or Codex in your own infrastructure and works from Slack. Exposes codebase investigation, file edits, branch and PR creation, allowlisted command execution, CI status and an audit log as MCP tools, keeping every credential behind the tool layer instead of handing it to the model.