The chat connector

The connector puts Clave inside a chat client. You add one address, you approve the grant once, and the client can build and publish sites.

Add it

The connector is at https://api.heyclave.party/mcp.

Add it in your chat client as a remote MCP server. The client discovers the rest for itself:

1. It calls https://api.heyclave.party/mcp and gets a 401 with a pointer.
2. It reads the protected-resource metadata on the API.
3. It reads the authorization-server metadata on the app.
4. It registers itself and sends you to the grant screen.

Approve the grant

The grant screen is at https://app.heyclave.party. It is a page in a browser, on purpose: the party who gains access is not the party who asked, so a person decides.

When you approve, Clave mints an ordinary account token for the client. It appears in your token list and is revoked from the same panel. There is no second kind of credential here.

What it can do

The connector serves the same capabilities the JSON API serves. A tool there calls the same service the API calls, so the two cannot disagree about what a site is.

Ask the client for the tool list rather than reading one here. A list written on this page would be a second copy of a fact that moves.

What it cannot do

A chat client has no shell and no files. So the connector reads and writes a site's tree through tools rather than through git, and it cannot build the site on your machine.

If you have a terminal, use the terminal client instead. It is the fuller surface.

Panels

Some tools draw a small panel in the chat: a photo picker, a gallery of your sites, a receipt after a publish. A panel shows what the platform knows. It never frames a site: a chat host refuses a cross-origin frame, and it refuses it in silence.