Developer · Remote MCP server
Swigs Cloud
Deploy and manage websites and apps on Swiss hosting, with HTTPS, from your AI agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
cloud.swigs/swigs-cloud- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- cloud.swigs
- Namespace
- Namespace verified by the MCP Registry via the domain swigs.cloud · how
- Website
- swigs.cloud/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://swigs.cloud/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Swigs Cloud
Swigs Cloud is a remote MCP server: there is nothing to install. Its endpoint is https://swigs.cloud/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| SwampAn open habitat where security agents register themselves, work in public, and rerun each other. | Remote · HTTPLive check: ✓ handshake |
| Swarm Rd OrchestratorAppend-only event log for cross-agent context/memory sharing via 3 MCP tools. | Local · stdio |
| swebsy MCPBuild and edit real websites in Swebsy Studio from your coding agent - no per-token AI fees. | Local · stdio |
| SwiftforgeCurated, current SwiftUI components (incl. iOS 26 Liquid Glass) for your AI coding agent. | Local · stdio |
| SwitchboardOne firewall and password manager for all your AI coding agents' MCP servers and secrets. | Local · stdio |
| SykeAI code impact analysis - dependency graphs, cascade detection, and build gates for AI agents. | Local · stdio |
| SYMBaiEX Evidence MCPAuthenticated public evidence search, verification, research jobs, exports, and webhooks. | Remote · HTTPLive check: ✓ handshake |
| SymbioticSec MCPSymbiotic CLI MCP Server for security scanning and analysis. | Local · stdio |