Timeweb Cloud MCP Server

Timeweb Cloud's official remote MCP: account servers, databases, Kubernetes, domains, mail, S3 and billing, with mandatory confirmation for changes

MCP server OfficialEditors’ pickRussian stack

timeweb-cloud/mcpAuthor:Timeweb Cloud

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/timeweb-cloud-mcp-server

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 http timeweb-cloud https://api.timeweb.cloud/api/v1/mcp/search --header 'Authorization: Bearer <your AUTHORIZATION>'

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

{
  "mcpServers": {
    "timeweb-cloud": {
      "type": "http",
      "url": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

Keys and settings

AUTHORIZATIONsecret, 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-cloud": {
      "url": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

AUTHORIZATIONsecret, 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-cloud","type":"http","url":"https://api.timeweb.cloud/api/v1/mcp/search","headers":{"Authorization":"Bearer <your AUTHORIZATION>"}}'

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

{
  "servers": {
    "timeweb-cloud": {
      "type": "http",
      "url": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

Keys and settings

AUTHORIZATIONsecret, 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 ~/.codex/config.toml, for all projects

[mcp_servers.timeweb-cloud]
url = "https://api.timeweb.cloud/api/v1/mcp/search"
http_headers = { Authorization = "Bearer <your AUTHORIZATION>" }

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

Keys and settings

AUTHORIZATIONsecret, 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-cloud": {
      "httpUrl": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

Keys and settings

AUTHORIZATIONsecret, 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-cloud": {
      "serverUrl": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

AUTHORIZATIONsecret, 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-cloud": {
      "type": "streamableHttp",
      "url": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

AUTHORIZATIONsecret, 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-cloud": {
      "type": "streamable-http",
      "url": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

Keys and settings

AUTHORIZATIONsecret, 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-cloud": {
      "type": "remote",
      "url": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

Keys and settings

AUTHORIZATIONsecret, 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-cloud": {
      "url": "https://api.timeweb.cloud/api/v1/mcp/search",
      "headers": {
        "Authorization": "Bearer <your AUTHORIZATION>"
      }
    }
  }
}

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

Keys and settings

AUTHORIZATIONsecret, required

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

Checked against the repository on Sep 25, 2026, commit a9471a4.

Text for your agent

Add an HTTP MCP server named timeweb-cloud at https://api.timeweb.cloud/api/v1/mcp/search with an Authorization: Bearer header using my token from the API and Terraform section of the control panel. Ask for confirmation before any WRITE or BILLABLE operation.

Other ways from the author

claude mcp add --transport http timeweb-cloud \
  https://api.timeweb.cloud/api/v1/mcp/search \
  --header "Authorization: Bearer ВАШ_ТОКЕН"

Issue the token in the control panel, API and Terraform section. Check the connection with claude mcp list.

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

What it does

The server runs on Timeweb Cloud's side, and the agent connects over HTTP with a token from the control panel. Instead of a long tool list, the client sees only three: search_tools finds the right operation by task description, get_tool_definition returns the argument schema, execute_tool runs it. Through them the agent reaches account servers, databases, Kubernetes, applications, domains, mail, S3, networks, IPs, projects, AI agents and knowledge bases. Any operation marked WRITE or BILLABLE runs in two steps: the first call changes nothing and returns a confirm_token valid for 300 seconds, the second call with that token confirms the action. There are no delete tools in the list at all.

Who it is for. For Timeweb Cloud account owners who want to manage infrastructure from a conversation with an agent instead of the control panel.

Good fit when

You need an agent to create or configure a server, database or Kubernetes cluster
You need to check the status of account applications, domains or mailboxes
You want a safe way to give an agent cloud access with confirmation for every billable or write action

Not a fit when

You need to delete a resource: the server cannot delete anything, that only happens in the control panel
You need a full-access token but are not ready for the agent to see the whole account: issue a scoped key instead

Example request

Show all my Timeweb cloud servers and their status, don't change anything

Limitations

The token works within the issued API key's permissions; to limit what the agent can do, issue a separate scoped key. Deleting resources through the server is not possible. One-click setup exists only for VS Code and Cursor; Claude Code, Claude Desktop, Windsurf and Zed need manual configuration.

How to disable. Remove the server from your MCP client config, for example with claude mcp remove timeweb-cloud, and revoke the API token in the control panel if needed.

MCP

Transport: http
Authentication: API key

Environment variables
Environment variables
TIMEWEB_API_TOKEN required, secret	An API token from the control panel's API and Terraform section, sent in the Authorization: Bearer header.

Security check

The agent can create and modify servers, databases, domains, mail and other account resources
Some operations are marked BILLABLE and cause charges, even though they require confirmation
The token grants access within its key's permissions, so a separate scoped key for the agent is worth issuing

README in short

The README describes the three-tool search, schema and execute architecture, gives the endpoint and auth header, connection instructions for VS Code, VS Code Insiders, Cursor and Claude Code plus a manual config for other clients, and walks through the confirmation protocol for write and billable operations with an error status table.

FAQ

Can the agent accidentally charge money or break something?

Any WRITE or BILLABLE operation needs a second call with a confirm_token that lives 300 seconds and must match the original arguments. Without confirmation nothing runs.

Can I limit what the agent sees?

Yes, issue a separate scoped API key in the control panel: the server checks the key's permissions and rejects forbidden operation categories.

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