# Jetrepo

> Self-hosted, agent-native CMS. External agents model and author content; humans govern access, Approval, Operations, and publication. Jetrepo runs no model and stores no model-provider credentials.

This is the curated entry point for agents using Jetrepo. Resolve root-relative links against the documentation origin from which you fetched this file. The connected installation's live schemas, permissions, and state are authoritative.

## Start here

- [Agent execution workflow](/developers/mcp/agent-workflow.md): Discovery, bootstrap, exact proposals, execution, human Approval, result verification, and recovery.
- [Connect your client](/developers/mcp/clients.md): Codex, Claude Code, Cursor, VS Code with GitHub Copilot, and generic HTTP setup.
- [Authentication](/developers/mcp/authentication.md): Organization-bound OAuth, optional Agent Auth, workload-key limits, and revocation.
- [Core concepts](/guides/getting-started/core-concepts.md): Organization, Backend, Environment, Change Set, Candidate, Approval, Operation, and Published state.
- [First task with a human](/guides/getting-started/first-agent-task.md): Connect an app, create an unpublished draft, and inspect the result.

## Operating contract

Management MCP is POST /agent/mcp on the installation's Management API origin. Exactly four public tools exist: inspect, propose, execute, control_operation. Domain actions are versioned Operation Definitions behind those tools. Discover their current schemas instead of guessing a mutation API.

1. Inspect ORGANIZATIONS explicitly. Select the user's intended Organization, Backend, and Environment from returned IDs. Inspect existing state before creating resources.
2. Normal work carries the stable Backend and exact Environment. Empty-Organization bootstrap uses an Organization Change Set and backend.create without fake Backend, Environment, or manifest values.
3. Inspect OPERATION_DEFINITIONS and follow nextCursor. Use inputSchema for operation arguments and outputSchema for domain results. Read the current Draft base through SETTINGS. Use exact revisions and $localRef for client dependencies, never internal $localId.
4. Propose a Change Set. Validation persists an immutable Candidate without changing managed Content. The response contains row, document, and uri; repeating a proposal can create another Candidate.
5. Execute row.id as candidateId and document.digest as digest with an idempotency key. Reuse that key for the same execution after a transport failure. Observe the returned Operation id until terminal.
6. If AWAITING_APPROVAL, return review and Operation links and wait. Client tool confirmation and chat consent are not Jetrepo human Approval. Agents cannot approve on behalf of a human.
7. Read relevant item outcomes before reporting success. A successful Draft operation does not publish Content. Never publish or delete beyond the user's authorized task.
8. Handle drift by reading current state and proposing again. Use only eligible cancellation, retry, secret-claim, and rollback controls. Keep secrets out of source, logs, and summaries.

- [Management tool contract](/developers/mcp/tools-and-safety.md): Permission expressions, immutable review evidence, human decisions, quotas, Tasks, subscriptions, and recovery.
- [States and permissions](/developers/reference/statuses-perspectives-permissions.md): Exact Operation states and permission/scope reference.
- [Members and roles](/admin/access/members-roles-scopes.md): Additive grants, resource and field scopes, and Organization connections.
- [Publication policy](/admin/settings/general.md): Environment override, Backend default, distinct approvers, and policy changes.
- [Credentials and claims](/admin/access/api-keys.md): Delivery keys, restricted Agent keys, mandatory Approval, and one-time claims.

## Choose the right read surface

Applications read REST/OpenAPI. Agents retrieve content through Context MCP on the separate Delivery origin. Delivery uses a scoped Delivery key or Preview Bearer, not a Management OAuth token. Read the authorization-cache boundary when revocation timing matters.

- [Endpoints and authentication](/developers/getting-started/endpoints-and-auth.md): Backend/Environment selection, aliases, credential separation, and provenance.
- [REST/OpenAPI](/developers/delivery/rest.md): Read-only resources, queries, errors, and exact contract identity.
- [Generate a frontend client](/developers/delivery/generate-client.md): Generate in the consumer repository from saved OpenAPI bytes and verify their hash.
- [Context MCP](/developers/mcp/context.md): Read-only search, read, traverse, resources, and subscriptions.
- [Structured fields](/developers/delivery/relations-components-taxonomy.md): IDs remain IDs, Components stay inline, and related reads use bounded batches.
- [Filters](/developers/delivery/filter-and-search.md), [pagination](/developers/delivery/sort-and-pagination.md), and [localization](/developers/delivery/localization.md): Supported semantics and cursor constraints.
- [Media](/developers/delivery/media-and-images.md) and [text rendering](/developers/delivery/text-and-html.md): Asset metadata, signed URLs, and safe HTML.
- [Preview handoff](/developers/preview/frontend-bootstrap.md): Verified frontend protocol, exact Candidate, one-time claim, and server-side sessions.
- [Preview lifetime and scope](/developers/preview/perspectives-and-sessions.md): A read capability grants no Approval, mutation, or publication.
- [Webhooks](/developers/webhooks/events.md), [signature verification](/developers/webhooks/verify-signatures.md), and [retries](/developers/webhooks/delivery-and-retries.md).

## Human and operator tasks

- [Console tour](/guides/getting-started/product-tour.md): Overview, Changes, Operations, Access, Delivery, Audit, Settings, and Connections.
- [Administration](/admin.md) and [Audit](/admin/activity.md): Decisions, operational controls, and immutable evidence.
- [Accounts](/guides/accounts/sign-in-and-profile.md), [security](/guides/accounts/security.md), and [Organizations](/guides/accounts/organizations-and-invitations.md).
- [Self-hosting](/self-hosting.md): Production Compose deployment and operator runbook index.
- [Install](/self-hosting/getting-started/install.md), [configuration](/self-hosting/configuration/environment.md), and [origins/auth](/self-hosting/configuration/public-origins-and-auth.md).
- [Architecture](/self-hosting/architecture.md) and [storage](/self-hosting/configuration/storage-redis-images.md): PostgreSQL, Redis, objects, workers, and public services.
- [Backup/restore](/self-hosting/operations/backups-and-restore.md), [upgrades](/self-hosting/operations/upgrades.md), and [health](/self-hosting/operations/health-and-logs.md).
- [Troubleshooting](/guides/troubleshooting.md), [Delivery errors](/developers/delivery/errors-and-limits.md), and [deployment troubleshooting](/self-hosting/troubleshooting.md).

## Boundaries and full corpus

There is no Content Studio, visual editor, editorial collaboration workflow, saved View editor, Management GraphQL, Delivery GraphQL, hosted control plane, model runtime, or Jetrepo-hosted SDK generator. Historical repository specs may describe removed surfaces; use these public guides and live Operation Definitions for current behavior.

- [Complete public documentation](/llms-full.txt): Full Markdown corpus generated from the same published guides.
- [Documentation home](/index.md): Audience entry points and navigation.