sweb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SWEB_GROUPS | No | Filter for API groups, for example vps,domains,vh/mail. Empty means all groups. | all |
| SWEB_ACCOUNT | No | Default account name from the accounts file. Empty means the first account. | |
| SWEB_API_URL | No | SpaceWeb API URL. | api.sweb.ru |
| SWEB_TIMEOUT | No | API request timeout in seconds. | 30 |
| SWEB_READONLY | No | Set to 1 to allow only read methods. | 1 |
| SWEB_OVERRIDES | No | JSON object for manual safety-class overrides, for example {"/vps:reboot":"write"}. | |
| SWEB_SPECS_DIR | No | Directory containing API specs. In Docker this is set via ENV and should not be placed in .env. | specs/ |
| SWEB_MAX_RETRIES | No | Maximum number of retries for eligible failures. | 3 |
| SWEB_BACKOFF_BASE | No | Base delay in seconds for exponential backoff. | 0.5 |
| SWEB_MIN_INTERVAL | No | Pause between API request starts in seconds, used to avoid rate limits. | 0.2 |
| SWEB_ACCOUNTS_FILE | Yes | The single source of credentials: a JSON file mapping account names to either {"login": "...", "password": "..."} or "login:password". | |
| SWEB_MAX_CONCURRENCY | No | Maximum number of concurrent API requests. | 4 |
| SWEB_ALLOW_DESTRUCTIVE | No | Set to 1 to allow destructive/paid methods. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Multi-provider cloud MCP (timeweb, selectel, tilda). Discovery-first:
cloud_search(query, provider=...) -> ranked operations;
cloud_describe(provider, tool) -> full parameter/body schema;
cloud_call(provider, tool, args) -> execute (read runs freely; write needs confirm=true; destructive/paid also need CLOUD_READONLY=0 + CLOUD_ALLOW_DESTRUCTIVE=1). Wide overview: cloud_catalog(provider) writes a greppable file with every operation. Errors: '[code] message'.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cloud_searchA | Find API operations across providers by a free-form query (RU or EN); returns the best matches with their tool names, methods and parameters |
| cloud_describeC | Full parameter and body schema of one operation |
| cloud_callC | Execute an operation. Flat args are routed to path/query/header/body by the operation schema; 'confirm': true is required for write/destructive/paid |
| cloud_providersB | Providers, their products, operation counts and credential state |
| cloud_catalogC | Write a greppable catalog file (rules + one line per operation) for a provider |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools form a clear discovery pipeline: search finds operations, describe returns one operation's schema, call executes it, providers lists backends, catalog dumps to a file. The only mild overlap is between cloud_search and cloud_catalog, since both surface operation information, though 'writes a local file' differentiates the latter.
All five tools share the cloud_ namespace prefix with short, readable suffixes. There is a minor deviation where the first three use action verbs (search, describe, call) while the last two are nouns (providers, catalog), but the pattern remains predictable.
Five tools is a lean, well-scoped surface for a generic multi-provider API proxy where breadth lives in the catalog rather than in tool count. Each tool maps to a distinct step in the workflow and no tool seems redundant.
The read-inspect-execute lifecycle is covered, but there is no tool to set or refresh credentials (cloud_providers only reports credential state), and no obvious way to browse/paginate a provider's operations without a free-form query. These gaps will force agents into dead ends when auth is missing or when they want to enumerate the surface.