Admin API / MCP for AI agents (draft & edit; Auth still gates publish) #16

Open
opened 2026-10-11 00:31:22 +00:00 by rhelwig · 0 comments
Owner

Idea

Expose DecentSite Admin capabilities as an API and/or MCP server so AI agents can drive site building and editing (pages, posts, assets, themes, asides, preferred sources, prepare-review) without scraping the UI.

Auth / money boundary (for now)

  • Agents may create and change local drafts and prepare review payloads.
  • Publication, contract registration, and any spend stay gated by DecentSite Auth (device approval), same as today.
  • Later (noted, not required for v1): agents with their own wallets/funds and more autonomy could be an optional path; do not weaken current Auth gates in the first cut.

Why

  • Matches DecentSite’s existing AI-authoring direction and Markdown-first reading for agents.
  • Lets assistants (and other tools) build sites programmatically while humans keep the approval key.
  • Complements issue #15 (import from Platform) for multi-editor / multi-machine workflows.

Sketch (non-binding)

  • Local Admin HTTP API (loopback or token) and/or MCP tools mirroring Admin actions.
  • Clear scopes: read site, write draft, upload asset, prepare review — never auto-broadcast Platform writes.
  • Document in SPECS / AI harness policy.

Related: existing Admin AI chat / harness docs; #15 import-from-Dash.

## Idea Expose DecentSite Admin capabilities as an **API and/or MCP server** so AI agents can drive site building and editing (pages, posts, assets, themes, asides, preferred sources, prepare-review) without scraping the UI. ## Auth / money boundary (for now) - Agents may create and change **local drafts** and prepare review payloads. - **Publication, contract registration, and any spend** stay gated by DecentSite Auth (device approval), same as today. - Later (noted, not required for v1): agents with their own wallets/funds and more autonomy could be an optional path; do not weaken current Auth gates in the first cut. ## Why - Matches DecentSite’s existing AI-authoring direction and Markdown-first reading for agents. - Lets assistants (and other tools) build sites programmatically while humans keep the approval key. - Complements issue #15 (import from Platform) for multi-editor / multi-machine workflows. ## Sketch (non-binding) - Local Admin HTTP API (loopback or token) and/or MCP tools mirroring Admin actions. - Clear scopes: read site, write draft, upload asset, prepare review — never auto-broadcast Platform writes. - Document in SPECS / AI harness policy. Related: existing Admin AI chat / harness docs; #15 import-from-Dash.
Sign in to join this conversation.
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rhelwig/DecentSite#16
No description provided.