Agent API / MCP for campaign editing (GM gates consequential actions) #2

Open
opened 2026-10-11 00:36:23 +00:00 by rhelwig · 1 comment
Owner

Idea

Expose the RPG Campaign Platform to AI agents via an HTTP API and/or MCP server so assistants can help draft and edit campaign content (lore, NPCs, characters, sessions, print packages) without driving the browser UI.

Auth / safety boundary (for now)

  • Agents may read and draft instance-local content the operator allows.
  • Consequential actions stay human-gated: invites, deletes, public publish links, consent changes, and anything that spends money or changes who can access the instance.
  • Pattern matches DecentSite #16: agents draft; humans approve.

Why

  • Latitude / campaign-history work is high-volume text; agents already help offline — a first-class MCP would make that durable.
  • When CampaignHistory_Latitude (or similar) migrates to DecentSite or this platform, agent tooling should already be designed in.
  • Self-hosted instances should keep all data on the operator’s machine; MCP should be loopback/token-scoped by default.

Sketch (non-binding)

  • MCP tools: list campaigns, get/put markdown or structured records, search, prepare print package — no auto-invite.
  • Document scopes in SPECS; align with passkeys / Sign-in with Dash sessions.
## Idea Expose the RPG Campaign Platform to AI agents via an **HTTP API and/or MCP server** so assistants can help draft and edit campaign content (lore, NPCs, characters, sessions, print packages) without driving the browser UI. ## Auth / safety boundary (for now) - Agents may read and draft **instance-local** content the operator allows. - **Consequential actions** stay human-gated: invites, deletes, public publish links, consent changes, and anything that spends money or changes who can access the instance. - Pattern matches DecentSite [#16](https://git.ronhelwig.com/rhelwig/DecentSite/issues/16): agents draft; humans approve. ## Why - Latitude / campaign-history work is high-volume text; agents already help offline — a first-class MCP would make that durable. - When CampaignHistory_Latitude (or similar) migrates to DecentSite or this platform, agent tooling should already be designed in. - Self-hosted instances should keep all data on the operator’s machine; MCP should be loopback/token-scoped by default. ## Sketch (non-binding) - MCP tools: list campaigns, get/put markdown or structured records, search, prepare print package — no auto-invite. - Document scopes in SPECS; align with passkeys / Sign-in with Dash sessions.
Author
Owner

Note from Ron (2026-10-10): CampaignHistory_Latitude is expected to migrate to DecentSite (or similar) in the not-too-distant future; agent MCP on this platform and/or DecentSite #16 should cover that content workflow once migrated.

Note from Ron (2026-10-10): CampaignHistory_Latitude is expected to migrate to DecentSite (or similar) in the not-too-distant future; agent MCP on this platform and/or DecentSite #16 should cover that content workflow once migrated.
Sign in to join this conversation.
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
ronhelwig.com/rpg-campaign-platform#2
No description provided.