Cloche

dev.clochePublished by cloche.devOfficial publisherv1.0.0Updated Oct 26, 2026

Publish a client-side app with Cloche and share it with a link.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Cloche lets an assistant publish a client-side app and share it with a link, connecting to a hosted MCP server with browser sign-in.

What you can do
  • Publish a client-side app from the agent's work and get a shareable link
  • Send the app's files, name, address, icon and data schema, plus a short note on what it does or what changed
  • Invite people to a shared app by email address or name
  • Wire an app to data from another connected service through read-only calls, either fetched with each viewer's own access or stored as an owner-made copy
  • Upload images and other binary files to an upload address the server returns
When to use it
Useful when you want an assistant to turn a small client-side app into something you can hand to others through a link, rather than keeping it only in the chat. Suited to quick demos, internal tools and shared prototypes that need sign-in and invitations.
Requirements
A remote MCP endpoint at mcp.cloche.dev; no local package or runtime is needed. OAuth sign-in through the browser is required. Some clients install it as a plugin from a marketplace repository; others can add the server address directly, which connects the tools without the bundled skill.
Before you install
Publishing sends the app's files, name, address, icon, data schema and a work note to Cloche, and binary files may go to an upload address the server returns. Inviting people sends their email address or name. Connected-service data may be fetched with the viewer's or the owner's access and, if the owner keeps a copy, stored and shown to everyone who can open the app. The tools are meant to leave out chat transcripts, credentials and saved app data, but review what is sent before publishing.

Installation

In SourceWeft

  1. Open Cloche in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.cloche%2Fcloche/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cloche": {
      "type": "http",
      "url": "https://mcp.cloche.dev/mcp"
    }
  }
}

README

Cloche plugin

Cloche lets your agent publish a client-side app and share it with a link.

Install

Ask your agent to follow the Cloche setup instructions. It will connect the MCP server and verify the connection.

In Claude Code, add this repository as a marketplace with /plugin marketplace add cloche-it/plugin, then install with /plugin install cloche@cloche.

In Codex, add the repository with codex plugin marketplace add cloche-it/plugin, then install Cloche from /plugins.

In other clients that support Agent Plugins, install this repository as a plugin. Complete the browser sign-in. If the tools do not appear, start a new chat.

You can also add https://mcp.cloche.dev/mcp as an MCP server. This connects the tools without installing the bundled skill.

Data and privacy

The plugin is a skill and an MCP server setting. It runs no scripts or hooks. Your agent talks to Cloche's MCP server, https://mcp.cloche.dev/mcp. Images and other binary files may go to a Cloche upload address that server returns. The agent sends:

  • The app: its files, name, address, icon and data schema, and a line on what it is for or what changed.
  • A short note on the work, so another chat can pick it up. The tools tell the agent to leave out the chat transcript, credentials and the data people saved in the app.
  • When you share an app, the email address or name of each person you invite.
  • When an app shows data from another connected service, the read-only calls that fetch it: the service's address and label, the tool names and their arguments, and a line on what you chose to share. Each time the app loads that data, Cloche makes those calls with the viewer's own access. If the owner keeps a copy instead, Cloche makes the calls with the owner's access, stores the result and shows that copy to everyone who can open the app.

See the privacy policy.

Support

[email protected]

Source: README.md at commit fb5868e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 27, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts