Connect Docklet to Claude

The Docklet connector lets Claude publish the HTML artifacts it creates — interactive guides, microsites, demos, reports, dashboards, landing pages — straight to a live, shareable URL. You ask Claude to build something; Claude publishes it to your Docklet account and hands you the link. Follow-up edits update the same link instead of creating a new one.

This page is the setup and usage guide for the connector. For data handling see our Privacy Policy; for the rules that govern published content see our Terms of Service (acceptable use and enforcement are in section 7 and section 13).

1. Before you start

• A free Docklet account.
• Claude with connector support (Claude.ai on a plan that allows adding connectors, or Claude Desktop). The connector speaks the Model Context Protocol (MCP) over HTTPS.
• The Docklet MCP endpoint: https://app.docklet.io/mcp

2. Option A — connect with OAuth (recommended)

OAuth is the simplest and safest way to connect: you sign in to Docklet in a browser window and approve access — no tokens to copy or store.

1. In Claude, open Settings → Connectors and choose Add custom connector (wording varies by client).
2. Enter the Docklet MCP URL: https://app.docklet.io/mcp
3. Claude opens a Docklet sign-in and consent page. Sign in and click Approve.
4. You're connected. Claude will list Docklet's tools and is ready to publish.

Behind the scenes Docklet uses the standard OAuth 2.0 authorization-code flow with PKCE and explicit user consent. You can revoke access at any time from the Docklet console (API tokens) or by removing the connector in Claude.

3. Option B — connect with a personal access token

If your client only lets you set a URL and headers, use a personal access token instead.

1. In the Docklet console, open API tokens → Create token, name it (e.g. Claude), and copy the secret. It is shown once and stored only as a hash.
2. Add the connector with the token in the Authorization header:

{
  "mcpServers": {
    "docklet": {
      "url": "https://app.docklet.io/mcp",
      "headers": { "Authorization": "Bearer docklet_pat_xxxxxxxx" }
    }
  }
}

Clients that cannot send custom headers may pass the token as a query parameter instead: https://app.docklet.io/mcp?token=docklet_pat_xxxxxxxx. Treat the token like a password; revoke it any time from the console.

4. What Claude can do

Once connected, Claude has these Docklet tools:

Each tool is annotated so Claude knows which ones only read versus which change or remove content — Claude will confirm before destructive actions like deleting.

5. Example prompts

Try these once the connector is active:

6. Visibility & who can see your Docklets

New Docklets are created with restricted visibility by default — they are not public until you choose to make them so. From the Docklet console (or the owner-only Share menu on a published page) you can set each Docklet to:

• Public — anyone with the link.
• Any signed-in user — must have a Docklet account.
• Selected users — only the email addresses you allow.

Visibility is enforced at the edge before any file is served. Changing visibility is done in the console — it is intentionally not exposed as a Claude tool, so the AI can't widen who sees your content.

7. Troubleshooting

8. Support & security

Questions or problems: hello@docklet.io. Security or abuse reports: security@docklet.io. You control your data and can delete any Docklet — or your whole account — at any time; see the Privacy Policy for how we handle and retain data.

← Back to the homepage