"Information about 'Pusher' - Possible Meanings or Applications" 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 '{

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.

Detects breaking changes in a TypeScript library's public API and recommends the semver bump, comparing two npm releases, git refs or a working tree. Each finding is graded proven or review-only.

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 AI agents to deploy, manage, and configure web applications on sota.io, including project creation, deployment, environment variables, custom domains, and rollbacks.

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.

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.

Before you move to Python 3.15 (or 3.15t), find every dependency with no wheel for it on your platforms — and the bump that fixes it. CLI, GitHub Action, MCP server.

Lets any MCP-capable client connect to the public Codemagic REST API to list apps and teams, inspect build history, and optionally trigger or cancel builds and manage team settings. Runs locally over stdio with the user's own API token and configurable read-only, build, or administrative permission modes.

Aegis keeps Claude Code, Codex CLI and Antigravity on your project's rules via a zero-dependency Model Context Protocol (MCP) server (aegis-mcp), AGENTS.md / CLAUDE.md bootstrap, git pre-commit hooks, and CI governance (aegis check). It serves each agent just-in-time rules for the files it is about to edit, then enforces AST and repository invariants before commit and in pull requests.

Enables LLMs to migrate Docker Compose applications to Kubernetes, including inspection, planning, manifest generation, validation, deployment with approval, verification, and diagnosis.

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 provisioning a fixed Ubuntu host and deploying registered PHP applications via Deployer, with read-only planning and validated stack/application reconciliation.

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 AI coding agents to deploy and manage full multi-service applications on Constructor from a single request, covering image builds, service configuration, start/stop lifecycle, logs, and file syncing on research desks. It handles browser-based sign-in and token renewal automatically so agents can inspect deployments and report results without manual setup.

Turns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.

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.

A comprehensive MCP server for Dokploy that provides 14 action-based tools covering the full DevOps lifecycle with minimal token usage. It enables AI assistants to manage projects, applications, databases, domains, servers, and more through a unified interface.

A secure MCP server providing read-only access to Argo CD instances using browser session cookies, enabling querying of applications, projects, clusters, and repositories.

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.

Enables AI agents to manage self-hosted Coolify v4 instances, including listing applications, safely handling environment variables with masking and dry runs, deploying, restarting, and reading logs.

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 users to plan and create applications on a Coolify instance from container images, Git repositories, inline Dockerfiles, and repository-based Docker Compose, while validating ownership and returning deployment webhooks.

One MCP server to manage self-hosted Coolify instances: verify connectivity, discover servers, deploy applications, tail logs, diagnose incidents, and run emergency ops from any MCP client.

Enables retrieving comprehensive information about GitLab merge requests, including details, commits, diffs, discussions, approvals, and CI/CD status, through natural language.

Safety-first GitOps operations for ArgoCD via the Model Context Protocol. Enables listing, diagnosing, syncing, and managing ArgoCD applications with progressive disclosure and defense-in-depth security.

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.

An MCP (Model Context Protocol) server that integrates with the ArgoCD API, enabling AI assistants and large language models to manage ArgoCD applications and resources through natural language interactions.