Deployment.io

io.github.deployment-ioPublished by GitHub account deployment-iov1.0.1Updated Oct 24, 2026

Deploy apps on your cloud. Create environments, configure infrastructure, and monitor jobs.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A remote MCP server that lets an assistant list, create and edit Deployment.io environments, inspect runners, and check deployment job and approval status.

What you can do
List environments in your organization with status, region and classification, and list available runners and regions for provisioning new environments on shared or custom AWS runners. Create new environments and rename existing ones. Check the status of deployment jobs and approval requests, including job logs. All actions run under your organization's role-based permissions, with production changes gated behind human approval.
When to use it
Useful when you manage Deployment.io infrastructure and want to drive environment setup and deployment monitoring from an AI assistant in natural language, for example provisioning an environment or checking whether a deployment job or approval request has completed.
Requirements
A remote endpoint at api.deployment.io over streamable HTTP. A Deployment.io account and OAuth 2.0 authentication with Dynamic Client Registration; the client opens a browser window on first tool use. No API keys or tokens are configured manually.
Before you install
The server can create and rename environments, which changes infrastructure; production changes are described as requiring human approval. Access is limited by OAuth scopes and organization RBAC, so consent carefully to the permissions requested. Authentication is delegated to your Deployment.io account through a browser flow.

Installation

In SourceWeft

  1. Open Deployment.io in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.deployment-io%2Fdeployment-io/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "deployment-io": {
      "type": "http",
      "url": "https://api.deployment.io/v1/mcp"
    }
  }
}

README

Deployment.io — Cursor Plugin

Deploy and manage apps to your cloud directly from Cursor. This plugin connects Cursor's AI agent to Deployment.io via the Model Context Protocol (MCP).

What it does

This plugin lets you manage your Deployment.io infrastructure through natural language:

  • List environments — view all your environments with status, region, and classification
  • Create environments — provision new environments on shared or custom AWS runners
  • Edit environments — rename and reconfigure existing environments
  • Monitor jobs — check deployment job status and logs
  • Approval workflows — manage approval requests for production changes

Setup

  1. Install the plugin from the Cursor Marketplace
  2. Cursor will prompt you to authenticate with your Deployment.io account via OAuth
  3. Start using natural language to manage your infrastructure

Authentication

This plugin uses OAuth 2.0 with Dynamic Client Registration. When you first use a Deployment.io tool, Cursor will open a browser window to authenticate with your Deployment.io account. No API keys or tokens need to be configured manually.

Available tools

ToolDescription
list_environmentsList all environments in your organization
list_runnersList available deployment runners and regions
create_environmentCreate a new environment
edit_environmentRename an environment
get_job_statusCheck the status of a deployment job
get_approval_statusCheck the status of an approval request

Security

  • All actions respect your organization's RBAC permissions
  • Production environments require human approval before changes
  • Agent keys are scoped to specific permissions via OAuth consent
  • Three-layer access control: OAuth scopes, RBAC entity permissions, classification-based approval gates

Links

License

MIT

Source: README.md at commit d4f1df9

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% 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
  • Documentation15 pts
  • License10 pts