Developer · Remote MCP server
The Deployer
Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.thedploy/deployer- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-14
- Updated
- 2026-09-14
- Publisher
- com.thedploy
- Namespace
- Namespace verified by the MCP Registry via the domain thedploy.com · how
- Website
- thedploy.com
- Repository
- github.com/Avinash147-1193/thedeployer-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.thedploy.com/api/v1/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- thedeployer 0.1.1 · protocol 2025-06-18
- Tools discovered
- 6:
check_repo,plan_deploy,status,logs,redeploy,request_done_for_you - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | thedeployer-mcp | 0.1.1 | stdio |
How to connect The Deployer
The Deployer is a remote MCP server: there is nothing to install. Its endpoint is https://app.thedploy.com/api/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: thedeployer-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y thedeployer-mcp@0.1.1. It reads the environment variable THEDEPLOYER_API_KEY (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"deployer": {
"command": "npx",
"args": [
"-y",
"thedeployer-mcp@0.1.1"
],
"env": {
"THEDEPLOYER_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Thalovant MCPConnect MCP clients to Thalovant control-plane and hub runtime APIs over stdio or Streamable HTTP. | Local · stdio, HTTP |
| The Aggregate - LLM benchmark aggregateFused LLM rankings: one IRT/Elo scale across ~5,000 public benchmark leaderboards, updated daily. | Remote · HTTPLive check: ✓ handshake |
| The Context CompanyAI agent observability for production traces, natural-language insights, and improvement loops. | Remote · HTTPLive check: sign-in required |
| The Deploy LogAI deployments that shipped and are available now, each sourced to the publisher's own page. | Remote · HTTPLive check: ✓ handshake |
| the drainPlain-text security bulletin board for AI agents: read, search, post, reply. No auth to read. | Remote · HTTPLive check: ✓ handshake |
| The Front Desk Review4,764 products, 626 categories: sourced prices, dated price history, independent-test coverage. | Remote · HTTPLive check: ✓ handshake |
| The Last CEOMake your coding agent better and earn: verified code, paid per use, on a real agent economy. | Remote · HTTPLive check: sign-in required |
| The Remote SuiteAppreciate teammates, celebrate milestones, and run workspace ops from MCP clients via OAuth. | Remote · HTTPLive check: ✗ no handshake |