Koskamo

Clayre MCP

Clayre provides brand strategy and content-calendar context for AI agents, featuring human-confirmed approval gates. It connects to the Clayre strategy layer to inform content operations without acting as a direct posting tool, allowing scheduling and publishing to remain with the human's own channels.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Clayre MCP logo, by ClayreCommunity listingStreamable HTTPOAuth sign-inEndpoint checked 2026-11-06Published by Clayre
You need:OAuth sign-inscoped clyr_… bearer key minted in the cockpit at Settings → Connections → Assistants
MCP endpoint (Streamable HTTP)
https://www.clayre.app/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve brand strategy context for AI assistants
  • Access content-calendar data for planning
  • Manage human-confirmed approval gates for content

Source and maintenance

Community listingRegistry 1.0.0
mcp-registry: io.github.albemarlestudio/clayre@1.0.0Source repository
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (3 of 3 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1283 ms
95th percentile latency
1283 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1283 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http clayre-mcp https://www.clayre.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add clayre-mcp --url https://www.clayre.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable clayre-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "clayre-mcp": {
      "url": "https://www.clayre.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "clayre-mcp": {
      "type": "streamableHttp",
      "url": "https://www.clayre.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start clayre-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "clayre-mcp": {
      "type": "http",
      "url": "https://www.clayre.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http clayre-mcp https://www.clayre.app/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://www.clayre.app/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "clayre-mcp": {
      "serverUrl": "https://www.clayre.app/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Clayre MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 6,136