TatNet — website deployment

What TatNet — website deployment does

TatNet — website deployment MCP server exposes TatNet’s public API to MCP-compatible clients. It is designed for conversational deployment and resource management on TatNet, a Russian cloud platform. The service can publish static or SSR websites from files supplied in the conversation, create applications from Git repositories or Docker images, start new builds, inspect build results, and retrieve logs.

The server also provides tools for reading and changing application environment variables, listing and attaching domains, checking the current account and projects, and reading balance information when the connection has the required billing permission. Kafka operations are available as well, including region and cluster inspection, cluster creation, resuming stopped clusters, allowlist changes, and deletion.

How it works

Clients connect to https://mcp.tatnet.cloud/mcp using Streamable HTTP. Authentication uses TatNet OAuth or a scoped API key sent as a Bearer token. OAuth users select an account, projects, and access level during consent. The server forwards calls to TatNet’s /v1 API using the permissions of the connection; it does not maintain its own application database or independent authorization model.

deploy_files packages the supplied website files as a tar.gz archive and sends them to TatNet. It can create the application on the first deployment and reuses an existing application with the same name on later calls. Backend projects cannot be built from a local folder through this tool; they need a Git source or Docker image. For Docker applications, deploy_app can update the image before starting the build.

A completed build is not sufficient to confirm availability. Clients should verify both status=success and deploy_state=live. Repeated create or deployment calls use the application name to avoid creating duplicate resources.

Setup and configuration

Register the remote endpoint in an MCP client, for example:

claude mcp add --transport http tatnet https://mcp.tatnet.cloud/mcp

OAuth is suitable for clients that support remote MCP registration and consent flows. Clients that can set request headers may use a TatNet API key instead:

claude mcp add --transport http tatnet https://mcp.tatnet.cloud/mcp \
  --header "Authorization: Bearer tn_live_…"

The repository documents optional server settings including LISTEN, API_BASE_URL, PUBLIC_URL, EXTRA_PUBLIC_URLS, and METRICS_TOKEN. They configure the listener, TatNet API endpoint, public OAuth address, alternate public names, and metrics access respectively. The published service supplies defaults for these settings.

Tools and capabilities

TatNet — website deployment includes tools for:

• Account, project, balance, and application inspection.
• Static and SSR file deployment.
• Git- and Docker-based application creation and deployment.
• Build status, build history, and log retrieval.
• Environment variable listing, updates, and deletion. Secret values are never returned.
• Domain listing, addition, and removal, including DNS guidance.
• Kafka region, cluster, pricing, lifecycle, allowlist, and deletion operations.

Limitations and notes

Application deletion and balance top-ups are not available through MCP. Virtual machines, databases, DNS zones, and S3 operations require the TatNet CLI or API. The deploy_files tool excludes .env files from its archive, and build logs should be treated as untrusted content. Resource visibility and actions depend on the intersection of the connection or API-key policy with the user’s current TatNet role. Kafka pricing is supplied by the API; the MCP server does not calculate billing independently.