Documentation
Build on DeckStera through HTTP and MCP
DeckStera exposes one application model through visual, HTTP, and MCP interfaces. Integrations can create decks, list organization content, apply idempotent semantic operations, inspect revisions, run diagnostics, compile supported outputs, and submit governed proposals. The versioned schemas make those behaviors discoverable without granting a model direct database or document access.
- Opening
- Evidence
- Offer
- Next step
Designed as a system
Make the story durable, not just the file
Versioned contracts
DeckSpec and operation schemas define stable semantic boundaries.
Transport parity
HTTP and MCP adapters invoke the same organization-scoped application services.
Idempotent writes
Mutation keys and revision preconditions make retries deterministic and conflicts visible.
From intent to delivery
A governed path through every revision
- 01
Structure the narrative
Start with a brief, a reusable pattern, or an existing DeckSpec.
- 02
Edit through semantic operations
Use the visual builder, HTTP, or MCP without splitting the document model.
- 03
Review and deliver
Resolve diagnostics and proposals before compiling the approved revision.
Direct answers
Frequently asked questions
Does DeckStera provide an API?
Yes. DeckStera exposes organization-scoped HTTP endpoints for decks, revisions, operations, publishing, providers, custom domains, and governed migration. Versioned OpenAPI contracts describe the supported customer surface.
What can agents do through DeckStera MCP?
MCP tools expose the same application use cases as HTTP, including semantic authoring, diagnostics, compilation, publication, provider compatibility, and migration controls. Remote access requires scoped credentials; local stdio remains available for trusted workflows.
Ready when the story matters