Plinth
dev.tryplinthPublished by tryplinth.devOfficial publisherv1.0.0Updated Oct 24, 2026
App hosting your agent runs: git, deploys, staging/production, Postgres. Owner approves risky steps.
Overview
Plinth is a remote app-hosting service that lets an assistant manage git, deploys, staging/production environments, and Postgres for your applications.
- What you can do
- Plinth is a hosted platform that an assistant connects to over a remote endpoint. According to the registry description, it covers git, deploys, staging and production environments, and Postgres, so an assistant can work with application hosting tasks through the service. The description also notes that the owner approves risky steps, indicating that sensitive operations are gated behind owner approval. No individual tools are listed in the manifest.
- When to use it
- Consider it when you want an assistant to help operate hosted applications, such as managing repositories, pushing deployments, moving between staging and production, or working with a Postgres database. It is aimed at teams that want agent-driven hosting work with owner approval on risky actions.
- Requirements
- A remote MCP endpoint at using streamable HTTP. OAuth authentication is required. No packages, environment variables, or headers are declared.
Installation
In SourceWeft
- Open Plinth in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.tryplinth%2Fplinth/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"plinth": {
"type": "http",
"url": "https://tryplinth.dev/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 15, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.