Gimme MCP
OfficialRelated Servers
Alternatives to Gimme MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to inspect and manage a Dokku host over SSH with structured tools, read-only defaults, and explicit guardrails for safe operations.10MIT
- AlicenseAqualityAmaintenanceEnables Codex or Claude users to deploy applications and Compose services, inspect logs/databases/backups, patch environment variables, and manage Cloudflare DNS records and HTTPS domains through natural-language conversations, running locally with user-supplied credentials and preview/read-only safeguards.9MIT
- FlicenseBqualityDmaintenanceEnables SSH-based deployment operations such as git pull, command execution, script upload/run, and SSH config management.4-
- AlicenseNot gradedqualityFmaintenanceEnables AI clients to operate remote VPS hosts through a jump-host gateway with a fixed whitelist of tools, allowing them to read logs, inspect and edit configuration files, manage services, and deploy or roll back versions. Production writes require a per-client time-limited lease, and all actions are audited, verified, and automatically reverted on failure.MIT
- AlicenseAqualityAmaintenanceSFTP deploys to shared hosting (cPanel, Plesk, any SFTP host) that an agent can undo. Every deploy backs up the files it replaces on the server first; restore puts them back and refuses if a live file was edited since. Deploy and restore only run a previewed plan. No delete, no-backup or prune tools.9303 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables remote administration of a Debian stage server over SSH, including monitoring, Docker Compose, PostgreSQL, logs, Nginx, firewall, and automation with 82 tools.-
TDQS
Scored across 12 tools
Each tool targets a distinct resource and action: host inspection, stack planning/provisioning, app registration, app resource planning/provisioning, deployment, releases, rollback, and service status. The plan/provision pairs are clearly separated by their plan/resource names and descriptions, so an agent should not confuse them.
Tool names follow a mostly consistent verb_noun snake_case pattern such as plan_stack, provision_stack, list_apps, deploy_app, and rollback_app. The only outlier is service_status, which uses a noun_noun form instead of a verb-first convention, but it is still readable and not confusing.
Twelve tools is well-scoped for a provisioning and deployment server. Each tool covers a meaningful step in the workflow, and none feel redundant or unnecessary.
The tool set covers the main lifecycle well: inspect, plan, provision, register, deploy, list releases, rollback, and check service status. The main gap is the lack of teardown or removal operations, such as unregistering an app or dropping provisioned resources, but most core workflows are fully supported.