Clayre

io.github.albemarlestudiov1.0.0Updated Oct 2, 2026

Brand strategy and content-calendar context for agents, with human-confirmed approval gates.

VerifiedStreamable HTTPWeb executableBusiness & CommerceProductivity & Workflow

Overview

AI-generated overview

Gives an assistant brand strategy and content-calendar context for an operator's content operation, with human-confirmed approval gates.

What it does
Clayre is described as the strategy and brand layer around an operator's content operation, providing brand strategy and content-calendar context to agents. It is explicitly not a posting tool: it decides what is worth posting, while scheduling and publishing stay with the human's own channel. Access is offered through an MCP endpoint and a REST API with the same key.
When to use it
Worth adding when an assistant needs brand and content-strategy context, or a content calendar, to help plan what is worth publishing. Not intended for scheduling or publishing posts, which remain with the operator's own channel.
Requirements
A remote endpoint at with MCP at Sign-in is by OAuth, or by a scoped bearer key minted in the cockpit under Settings, Connections, Assistants. A REST API with an OpenAPI document is also offered using the same key.
Before you install
The connector asks for OAuth sign-in or a scoped bearer key; treat that key as a secret and keep it out of shared logs. The description mentions human-confirmed approval gates, so confirm what an assistant may change before relying on it. It states it does not post or publish, so scheduling and publishing remain manual.

Installation

In SourceWeft

  1. Open Clayre in the dashboard and add it to a workspace.
  2. 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "clayre": {
      "type": "http",
      "url": "https://www.clayre.app/mcp"
    }
  }
}

README

Clayre connector skill

The public mirror of skills/clayre-connector/SKILL.md — the file an agent reads to learn when and how to call Clayre, the strategy and brand layer around an operator's content operation.

Connect:

  • MCP — https://www.clayre.app/mcp (OAuth sign-in, or a scoped clyr_… bearer key minted in the cockpit at Settings → Connections → Assistants).
  • REST — OpenAPI at https://www.clayre.app/api/v1/openapi.json, same key.

Not a posting tool — Clayre decides what's worth posting; scheduling and publishing stay with the human's own channel.

Canonical source lives in the private product repo; this mirror is refreshed on each connector change.

Source: README.md at commit 30fece0

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 2, 2026