sweb-mcp
Related Servers
Alternatives to sweb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to manage Beget hosting services through 73 tools covering the full Beget REST API, including sites, domains, DNS records, MySQL databases, FTP accounts, cron jobs, backups, mail and account statistics. It allows provisioning, configuration and rollback operations via natural language.733MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query and manage a web hosting billing platform through its External API — clients, tickets, invoices, domains, orders, products, and system data. It defaults to read-only with per-domain opt-in for writes, two-step confirmation for billing and destructive actions, and automatic redaction of secrets, card data, and PII.1MIT
- AlicenseBqualityBmaintenanceEnables AI agents to autonomously govern cloud hosting infrastructure and billing workflows, including provisioning, invoices, wallet credits, support tickets, and catalog management through 35 tools with JSON:API response hydration.35MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage WHM hosting accounts and server administration tasks including account management, server stats, updates, SSL, backups, and email through a secure API.13ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Plesk hosting environments through a set of standardized tools for security, health monitoring, DNS, email, backups, and service management.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to administer domains, DNS zones and records, contacts/NSSET, and account credit across multiple WEDOS accounts, with read-only/test safeguards and a generic call fallback.MIT
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.