i3deploy

com.i3deployPublished by i3deploy.comOfficial publisherv1.0.0Updated Oct 25, 2026

Deploy & release tracking with native MCP — ask Claude what's in production and cut the release.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A remote MCP server for i3deploy that lets an assistant check what is in production and cut a release through deployment and release tracking.

What you can do
Ask what is currently deployed in production and review release state through the assistant's conversation. Cut a release as part of the same workflow. Deployment and release tracking are exposed natively over MCP rather than through a separate dashboard.
When to use it
Useful when you want to query production deployment status or trigger a release from inside an assistant conversation instead of switching to a deployment tool. Suited to teams already using i3deploy for releases.
Requirements
A remote MCP endpoint at mcp.i3deploy.com, reachable over streamable HTTP. OAuth authentication is required, so an i3deploy account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
The server can cut releases, which changes production state; confirm what will be released before approving. OAuth grants access to your i3deploy account, so review the scopes requested. Deployment and release data is sent to the i3deploy service.

Installation

In SourceWeft

  1. Open i3deploy 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/com.i3deploy%2Fi3deploy/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": {
    "i3deploy": {
      "type": "http",
      "url": "https://mcp.i3deploy.com/mcp"
    }
  }
}

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.0LatestSep 16, 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.