Plinth
Server Details
App hosting your agent runs: git, deploys, staging/production, Postgres. Owner approves risky steps.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 36.2% over 23 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 72 tools
The namespace.action scheme (db.*, cron.*, domains.*, env.secrets.*) makes most tools clearly distinguishable, and descriptions reinforce the boundaries. A few pairs overlap semantically—analytics.get vs metrics.get (traffic vs request perf), deploy/promote/rollback, and logs.query vs requests.query—where an agent could plausibly misselect.
Overwhelmingly consistent namespace.snake_case pattern (project.create, cron.pause, webhooks.test, db.query), which is easy to parse. Minor deviations: a handful of bare unnamespaced verbs (deploy, promote, rollback, whoami) and a namespace singular/plural mismatch (approval.status/approval.cancel vs approvals.list).
72 tools is far above the comfortable range and is heavy even for a full deployment platform, forcing agents to sift across ~20 namespaces. Most tools do earn their place given the breadth (deploy, db, domains, cron, git, billing, support), but the sheer surface is excessive.
Coverage is remarkably complete across every subdomain: full project lifecycle (create/delete/get/list/upgrade/downgrade), envs, secrets, db (query/migrate/snapshot/restore), cron CRUD, domains buy/connect/verify/remove, git, deploy/rollback, logs/metrics/requests, webhooks, billing, and approvals. Only trivial gaps remain (e.g. no account deletion, no explicit env.create/delete).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
72 tool updates
- First observed
account.create - First observed
account.status - First observed
agents.list - First observed
agents.revoke - First observed
analytics.get - First observed
approval.cancel - First observed
approval.status - First observed
approvals.list - First observed
billing.card - First observed
billing.status - First observed
code.list - First observed
code.read - First observed
code.write - First observed
console.signin - First observed
cron.add - First observed
cron.list - First observed
cron.pause - First observed
cron.remove - First observed
cron.resume - First observed
cron.run - First observed
cron.runs - First observed
db.connection - First observed
db.migrate - First observed
db.migrations - First observed
db.query - First observed
db.restore - First observed
db.snapshot - First observed
db.snapshots - First observed
deploy - First observed
deploy.cancel - First observed
deploy.status - First observed
domains.buy - First observed
domains.connect - First observed
domains.list - First observed
domains.orders - First observed
domains.remove - First observed
domains.search - First observed
domains.verify - First observed
env.exec - First observed
env.list - First observed
env.restart - First observed
env.secrets.import - First observed
env.secrets.list - First observed
env.secrets.set - First observed
env.secrets.unset - First observed
env.status - First observed
git.branches - First observed
git.log - First observed
git.remote - First observed
git.revert - First observed
http.probe - First observed
logs.query - First observed
metrics.get - First observed
policy.set - First observed
project.create - First observed
project.delete - First observed
project.downgrade - First observed
project.get - First observed
project.list - First observed
project.upgrade - First observed
promote - First observed
requests.query - First observed
rollback - First observed
seo.setup - First observed
support.list - First observed
support.send - First observed
token.rotate - First observed
webhooks.add - First observed
webhooks.list - First observed
webhooks.remove - First observed
webhooks.test - First observed
whoami
Related MCP Connectors
Deploy and run web apps from your agent: live URL, Postgres, S3 storage, a version per commit.
Your agent ships the app. Alerts, logs, project memory and approval-gated deletes come with it.
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build and deploy an app from a GitHub repository to a managed live server and then operate it — logs, captured errors, health checks, managed Postgres, secrets, custom domains, email authentication, and Stripe checkout links. It also exposes safe, read/write-labelled tools so agents can rebuild, start/stop, and inspect projects without ever editing source code.MIT
- AlicenseBqualityBmaintenanceEnables AI agents to deploy and roll back applications, read build and runtime logs, diagnose broken apps, and run commands inside containers. It also manages environment variables, PostgreSQL databases, domains, cron jobs, marketplace services, and backups on a PaaS platform, with safety annotations so clients can confirm destructive actions.589 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to check repository deploy readiness, deploy apps to your own cloud (AWS, Google Cloud, Azure, DigitalOcean), and migrate apps from platforms like Heroku, Railway, Render, or Vercel with rollback.MIT
- AlicenseAqualityBmaintenanceDeploy internal apps built with AI behind your company login, each with its own database, file storage and secrets. Tools to deploy, read live logs, set who can open an app, assign roles and save secrets.12MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.