Timeweb Cloud MCP: full API coverage

Timeweb MCP Server

An MCP server with full Timeweb Cloud API coverage: servers, databases, Kubernetes, S3, domains and DNS, SSH keys, floating IPs and billing

MCP serverRussian stack

webkoth/mcp-timewebAuthor:Minas Sarkisyan

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/webkoth-mcp-timeweb

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio --env 'TIMEWEB_CLOUD_TOKEN=<your TIMEWEB_CLOUD_TOKEN>' timeweb -- npx -y timeweb-mcp-server

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "timeweb": {
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "timeweb": {
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"timeweb","type":"stdio","command":"npx","args":["-y","timeweb-mcp-server"],"env":{"TIMEWEB_CLOUD_TOKEN":"<your TIMEWEB_CLOUD_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "timeweb": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add timeweb --env 'TIMEWEB_CLOUD_TOKEN=<your TIMEWEB_CLOUD_TOKEN>' -- npx -y timeweb-mcp-server

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.timeweb]
command = "npx"
args = ["-y", "timeweb-mcp-server"]
env = { TIMEWEB_CLOUD_TOKEN = "<your TIMEWEB_CLOUD_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "timeweb": {
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "timeweb": {
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "timeweb": {
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "timeweb": {
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "timeweb": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "timeweb-mcp-server"
      ],
      "environment": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "timeweb": {
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "timeweb": {
      "command": "npx",
      "args": [
        "-y",
        "timeweb-mcp-server"
      ],
      "env": {
        "TIMEWEB_CLOUD_TOKEN": "<your TIMEWEB_CLOUD_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TIMEWEB_CLOUD_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 6ee4234.

Text for your agent

Get a token from the API keys page in the Timeweb Cloud panel and add a timeweb server to .mcp.json with command npx, args -y timeweb-mcp-server and the TIMEWEB_CLOUD_TOKEN variable.

Other ways from the author

npx timeweb-mcp-server

The recommended install method with no repo clone.

This is third-party code. Review the repository files before installing.

What it does

A TypeScript server, published to npm as timeweb-mcp-server, provides tools covering nearly all of the Timeweb Cloud API: creating, deleting, starting, stopping and rebooting cloud servers, PostgreSQL, MySQL, MongoDB, Redis and ClickHouse database clusters, Kubernetes clusters with kubeconfig retrieval, S3-compatible storage, domains and DNS records, SSH keys and binding them to servers, floating IPs with bind and unbind, balance and service pricing, plus reference data for server, database and S3 presets, OS images, datacenter locations and Kubernetes versions. It installs via npx with no repo clone, authorized with a single TIMEWEB_CLOUD_TOKEN from the Timeweb Cloud panel.

Who it is for. For developers and devops engineers who want to manage their whole Timeweb Cloud infrastructure from one MCP server in Claude Code.

Good fit when

You want one MCP for your whole Timeweb Cloud infrastructure: servers, databases, Kubernetes, S3, domains
You want a one-command npx install with no building from source
You want balance and pricing access alongside resource management

Not a fit when

You need a read-only mode: the README describes no toggle, and delete and create tools are available right away with one token
You need separate domain registration, renewal or transfer operations: domains and DNS here are about records, not the registration flow itself
You need the narrowest possible access: one TIMEWEB_CLOUD_TOKEN grants access to every API section at once

Example request

Show my Timeweb Cloud servers, account balance, and create a new A record for the api subdomain

Limitations

One TIMEWEB_CLOUD_TOKEN grants access to every section at once; the README describes no narrower tokens or a read-only mode. There are no dedicated domain-registration tools, only managing already-attached domains and DNS records. The author maintains this as a personal project, not on behalf of Timeweb.

How to disable. Remove the timeweb entry from .mcp.json and revoke the TIMEWEB_CLOUD_TOKEN in the Timeweb Cloud panel.

MCP

Transport: stdio
Authentication: API key

Environment variables
Environment variables
TIMEWEB_CLOUD_TOKEN required, secret	API token from the Timeweb Cloud panel, API keys section

Security check

Tools delete servers, databases, Kubernetes clusters and S3 storage in a single call
One token grants full access to every section at once; issue a separate token per task if the panel allows it

README in short

The README lists full API coverage by section: servers, databases, Kubernetes, S3, domains and DNS, SSH keys, floating IPs, account, configuration presets, gives npx or global installation, a Claude Code config via .mcp.json, and mentions a separate Claude Code plugin, tw-deploy, built on top of this server.

FAQ

Can access be limited to read-only?

The README describes no such option; one token opens access to every tool, including deleting servers and databases.

Is there a ready Claude Code plugin on top of this server?

Yes, the author mentions a tw-deploy plugin in a separate claude-code-plugins repository.

Netdata MCP

Editors’ pick

An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant

MCP serverMedium riskNo VPN needed80.7K

GitHub MCP Server

Editors’ pick

GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent

MCP serverHigh risk33.3K

Agent Skills for Google products

Agent Skills for Google products and technologies

Editors’ pick

Official Google skill collection for working with Google Cloud, BigQuery, GKE, ads and analytics from an agent

SkillHigh risk20.5K

Open source MCP servers for AWS

Official

AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring

MCP serverHigh risk9.7K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Netdata MCP

GitHub MCP Server

Agent Skills for Google products

Open source MCP servers for AWS