Claude connector (MCP)
mcp.slew.cloud is a remote MCP server:
connect it to the Claude app once and every chat — web, desktop, mobile —
can publish temporary shares on your slew account. No CLI, no pasted keys.
Connect
- In the Claude app: Settings → Connectors → Add custom connector.
- Enter
https://mcp.slew.cloud/mcp. - Claude opens the slew consent page — sign in with GitHub and approve.
That's the whole setup. Ask Claude to "make an HTML plan and share it" and
the chat ends with a link like quiet-harbor-lantern.slew.cloud.
Tools
| Tool | Effect |
|---|---|
share_page |
Publish a self-contained HTML page to an expiring URL (ttl_days 1–30, default 7) |
list_shares |
List your live shares with their expiry |
Scope and security
The OAuth flow (authorization code + PKCE, dynamic client registration) issues a share-scoped token: it can create and list temporary shares and nothing else — no project deploys, no domains, no token minting. Revoke it any time; shares it created still expire on their own.
Under the hood: authorization and resource server metadata live at
/.well-known/oauth-authorization-server and
/.well-known/oauth-protected-resource on mcp.slew.cloud, so any
MCP-capable client that speaks OAuth 2.1 can connect the same way — the
Claude app is just the first.
When to use what
| You are in | Use |
|---|---|
| Claude Code / a terminal agent | The slew CLI (and the slew-share skill) |
| The Claude app (web, desktop, mobile) | This connector |
| CI | SLEW_TOKEN and the HTTP API |