> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spitzli.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP integration

> Connect an OAuth-capable client to Spitzli Cloud registry or hosting tools.

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.

```json theme={null}
{
  "mcpServers": {
    "Spitzli Cloud": {
      "url": "https://studio.webdock.dev/api/mcp"
    }
  }
}
```

## Scope families

| Scope | Access |
| - | - |
| `webdock:read` | Operator Registry reads and admitted installed-plugin reads |
| `webdock:write` | Registry and admitted plugin writes in addition to read access |
| `hosting:read` | Hosting reads within current customer permissions |
| `hosting:write` | Authorized hosting changes in addition to read access |
| `offline_access` | Renewal only for clients explicitly granted it |

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.

> [!NOTE]
>
> 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](https://docs.spitzli.cloud/developers/byok.md) for provider credentials and revisions, and [plugin API and MCP](https://docs.spitzli.cloud/developers/plugin-api-mcp.md) 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`).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.