Skip to main content
Glama
Skydeo Landing MCP

Skydeo Landing MCP

by irwing-reza

Skydeo Landing MCP

Hosted control plane for creating, previewing, revising, and eventually publishing Skydeo landing pages through Model Context Protocol clients.

Documentation

Related MCP server: lobby

Current milestone

This repository currently provides a production-authenticated draft and preview workflow:

  • Streamable HTTP MCP transport through Cloudflare Agents SDK

  • a Cloudflare Access OAuth integration for Skydeo team identity

  • manage_landing for deterministic initial page discovery and persisted legacy-draft status reads

  • confirm_publish as a separate landings:publish boundary that currently fails closed without reading draft state or taking repository action

  • create_draft, get_draft, update_draft, and revoke_preview MCP tools

  • a typed landing-draft state machine

  • one SQLite-backed Durable Object per draft

  • one isolated Sandbox preview runtime per draft

  • immutable SHA-256 revisions with revision-bound preview URLs

  • a fail-closed preview proxy that verifies Cloudflare Access assertions before forwarding production preview traffic to a Sandbox

  • a configurable preview TTL (24 hours by default), revocation, Durable Object alarms, and idempotent Sandbox cleanup

  • no production publishing capability or credentials

manage_landing is the intended public workflow boundary. Its safe discovery and status paths are active now. Repository-backed create/edit requests and all publish requests fail closed without allocating a Sandbox or changing state until the canonical repository and credentials are configured. The direct-HTML draft tools remain available as legacy foundation capabilities during that migration.

The deployed /mcp route uses Cloudflare Access-backed OAuth. npm run dev explicitly enables a local-only mode, while npm run dev:access exercises the complete Access OAuth flow after local secrets are configured.

Local checks

npm run cf-typegen
npm run check

Docker is required when starting the Sandbox-backed Worker locally:

npm run dev

The first container build can take several minutes. The MCP endpoint is available at http://localhost:8787/mcp, and health is available at http://localhost:8787/healthz.

The repository includes a project-scoped Codex MCP configuration at .codex/config.toml. Trust the repository, keep npm run dev running, and restart Codex (or open a new task) to make the skydeo_landing tools available directly in the app, CLI, or IDE extension. The configuration allow-lists only status and the draft/create/update workflow; it contains no publish tool.

create_draft accepts a hostname, base revision, and complete HTML document. update_draft replaces the HTML and requires the current revision as expected_revision, preventing one editor from silently overwriting another. Every successful create or update returns a preview URL for that immutable HTML revision. Local preview URLs remain development-only capability URLs. Production preview hostnames are routed through the Worker and require a valid assertion from the wildcard Cloudflare Access preview application before Sandbox proxying. The Worker also asks the draft coordinator for an active lifecycle decision before proxying. get_draft reports active, expired, revoked, or cleaned_up, and revoke_preview fails closed immediately while cleanup proceeds durably.

Planned capability sequence

  1. Create isolated repository workspaces from a pinned skydeo-landings revision instead of accepting complete HTML.

  2. Add validation and structured landing-page edit operations.

  3. Add a durable, explicitly approved publish workflow with production safeguards.

The MCP session is not the source of truth for a draft. Each draft is addressed by a stable Skydeo-scoped ID and stored in its own Durable Object so work survives client reconnections and can be resumed from different MCP hosts.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to manage markdown-based landing pages across many domains over MCP, with tools to list, read, write, and delete sites. Writes publish immediately and are atomic and versioned.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to connect to a selected website via OAuth, send ready-to-use static HTML packages, read and edit text, CSS, and JavaScript with preview, and manage pending updates without automatic publishing.
      3
      1
      MIT