Skip to main content
Spitzli Cloud uses stateless Streamable HTTP with JSON responses at https://studio.webdock.dev/api/mcp.
1

Prepare the client

Use an operator-registered OAuth client with the exact callback used by your MCP client. Complete the account security setup before authorizing.
2

Choose permissions

Select registry or hosting access. Request read access first and add write access only when required.
3

Connect and authorize

Configure the endpoint below, complete OAuth consent, and request the exact registered MCP resource audience.
4

Discover tools

Use your client’s tool discovery after login. Tools depend on granted scopes and current permissions; a tool’s presence does not bypass resource authorization.

​
Scope families

Keep registry and hosting scope families separate. Hosting access does not grant operator catalog authority.

​
Operations and results

Registry tools include list_records and get_record. Hosting tools include list_hosting_apps, get_hosting_app, get_hosting_logs and get_hosting_operation. Write-capable hosting tools enqueue operations: inspect their result and final resource state. Deletion and retained-storage purge require current platform administrator permissions and their explicit confirmation inputs. Read the tool schema rather than guessing arguments.
This is the Spitzli Cloud MCP server. The Mintlify management MCP server manages documentation and uses a different account and authorization flow.

​
BYOK tools

Use discovery for currently wired tools; older provider command lists are not a promise of native availability. See BYOK boundaries for provider credentials and revisions, and plugin API and MCP for installed extension tools. Source: native tool discovery (crates/control-plane/src/first_party_mcp.rs), Hosting tools (crates/control-plane/src/resource_hosting.rs) and OAuth authority (crates/oauth/src/mcp_authority.rs).