← upd.live

INDIVIDUAL MCP TOOL

assess_project

BEFORE deploying, research the project LOCALLY (you have the code + compute) and send upd.

upd.livenone authenticationAvailability not checked

Input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.
  • A tool name or description suggests sending messages.

Parent endpoint

upd.live

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.upd-live]
url = "https://mcp.upd.live/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "upd-live": {
      "type": "http",
      "url": "https://mcp.upd.live/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: upd-live
Remote MCP URL: https://mcp.upd.live/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": {
    "upd-live": {
      "url": "https://mcp.upd.live/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "upd-live": {
      "type": "http",
      "url": "https://mcp.upd.live/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "upd-live",
  "transport": "streamable-http",
  "url": "https://mcp.upd.live/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • prep_guide — Return the step-by-step guide your agent MUST follow to prepare a project and deploy it to upd.: confirm it meets the type's contract, fix what's missing, archive it, and the EXACT upload call (endpoint + auth + tar.gz).
  • deploy_local — Deploy a local project folder to a live URL on upd.
  • deploy_git — Deploy a PUBLIC git repository to a live URL on upd.
  • deployment_plan — Turn a 'ready' planRef (from assess_project) into a concrete plan to confirm with the user: power class, memory, whether it will be ephemeral (anon) or persistent (account), the expected URL pattern, and what will happen.
  • deployment_status — Check ONE of your deployments by id.
  • list_deployments — List your ACTIVE deployments (live + currently building), newest first, each as the standard object { id, name, status, url, source, isAnon, expiresAt, createdAt }.
  • destroy_deployment — Permanently take down ONE of your deployments (tears down its live app and frees a slot).
  • redeploy — Re-deploy ONE of your existing projects with the latest code, reusing the SAME app and url (never creates a second app).