INDIVIDUAL MCP TOOL
check_repo
Checks whether a public GitHub, GitLab or Bitbucket repository will deploy: the services it found, what's missing (each with its fix), the environment variables it needs, and what it would cost a month on DigitalOcean, AWS, Google Cloud and Azure.
LIVE ENDPOINT
https://app.thedploy.com/api/v1/mcp
Connect to this endpoint to inspect the live schema for check_repo and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.thedeployer]
url = "https://app.thedploy.com/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"thedeployer": {
"type": "http",
"url": "https://app.thedploy.com/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: thedeployer
Remote MCP URL: https://app.thedploy.com/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"thedeployer": {
"url": "https://app.thedploy.com/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"thedeployer": {
"type": "http",
"url": "https://app.thedploy.com/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "thedeployer",
"transport": "streamable-http",
"url": "https://app.thedploy.com/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
plan_deploy— Plans deploying a repository with the user's account on The Deployer: checks the repository like check_repo, then adds the user's connected cloud and git accounts, any project they already have for it, and the next steps, with links.status— Lists the user's projects on The Deployer, or one project: whether each is live, its live addresses, and its latest deployment and where that is.logs— Shows the log of a project's latest deployment, or of a given deployment, newest lines last, with secrets removed.redeploy— Puts the latest code on a live project's branch online: pulls it and restarts the app, like Pull & Restart in The Deployer.request_done_for_you— Asks The Deployer's team to do it for the user: launch (put an app online in the user's own cloud account) or move (move an app from another host, such as Heroku, into it).