# deco developer documentation

> Storefront documents the Blocks framework, the Site Editor app, website templates, and commerce integrations.
> Studio documents the extensible platform: context, tasks, sandboxes, connectors, and MCP Apps.
> Blocks 7.x is the released default. Blocks Next is an unreleased proposal; Fresh and the former admin are retired.
> Site Editor publishing follows Git changes, a pull request, review or merge, and the configured deployment. Runtime content reload APIs are separate delivery capabilities.
> Respect availability labels. Do not describe preview, planned, or in-build APIs as available.

Any documentation page is available as Markdown by appending `.md` to its URL.

## Scoped indexes

- [Storefront — current](https://docs.decocms.com/storefront/llms.txt)
- [Studio](https://docs.decocms.com/studio/llms.txt)
- [Site Editor](https://docs.decocms.com/storefront/editor/llms.txt)
- [Templates and storefront implementation](https://docs.decocms.com/storefront/templates/llms.txt)
- [Blocks 7.x — current](https://docs.decocms.com/storefront/blocks/v7/llms.txt)
- [Blocks Next — UNRELEASED PREVIEW](https://docs.decocms.com/storefront/blocks/next/llms.txt)
- [Fresh — retired runtime archive](https://docs.decocms.com/storefront/blocks/fresh/llms.txt)
- [Former admin — retired archive](https://docs.decocms.com/storefront/legacy/llms.txt)

## Storefront — Getting started

- [Blocks 7.x](https://docs.decocms.com/storefront/blocks/v7/overview.md): Configuration management for humans and agents with the released Blocks 7.x framework.
- [How v7 works](https://docs.decocms.com/storefront/blocks/v7/architecture.md): The request path, the authoring path and the package graph of a Deco Blocks v7 site.
- [Quickstart: TanStack Start on Cloudflare Workers](https://docs.decocms.com/storefront/blocks/v7/quickstart.md): Build a TanStack Start site on Cloudflare Workers with one CMS-driven page that Deco Studio can edit.
- [Quickstart: Next.js App Router](https://docs.decocms.com/storefront/blocks/v7/quickstart-nextjs.md): Add Deco Blocks to a Next.js App Router site, render one CMS page and connect Deco Studio.
- [Project structure](https://docs.decocms.com/storefront/blocks/v7/project-structure.md): The files of a Deco Blocks v7 site, the files the code generator writes, and which of them to commit.

## Storefront — Core concepts

- [Blocks and sections](https://docs.decocms.com/storefront/blocks/v7/model.md): What a block is, how to write a section that editors can configure, and how sections are registered and nested.
- [Content and the decofile](https://docs.decocms.com/storefront/blocks/v7/content.md): How a v7 site stores content as a flat map of JSON blocks, how blocks refer to each other, and how content reaches the running site.
- [Pages and routing](https://docs.decocms.com/storefront/blocks/v7/routing.md): How a URL finds a page block in v7, the path pattern syntax, redirects, sitemaps, and the route helpers in each binding.
- [Loaders and actions](https://docs.decocms.com/storefront/blocks/v7/loaders.md): The three kinds of server functions in a v7 site (loaders called from content, section loaders, and site loaders and actions) and how to call them over /deco/invoke.
- [Matchers and variants](https://docs.decocms.com/storefront/blocks/v7/variants.md): Show different content to different visitors with multivariate flags and matchers, including A/B splits, device and location rules, and custom matchers.
- [Schema generation](https://docs.decocms.com/storefront/blocks/v7/schema.md): How Studio's forms are generated from your TypeScript Props types and JSDoc tags, and how the schema is served to Studio.
- [Site Editor and the v7 admin protocol](https://docs.decocms.com/storefront/blocks/v7/studio.md): The v7 runtime's metadata, preview, invoke and content reload endpoints, and how they relate to Studio's repository-backed Site Editor.
- [Previews and draft preview](https://docs.decocms.com/storefront/blocks/v7/preview.md): How Studio previews sections and pages, how to make previews render correctly, and how draft preview shows unpublished content on the real site.
- [Request context](https://docs.decocms.com/storefront/blocks/v7/request-context.md): Read the current request, its abort signal, device and request id from anywhere in server code with RequestContext, and set response headers from loaders and actions.

## Storefront — Rendering

- [Section conventions](https://docs.decocms.com/storefront/blocks/v7/sections.md): The exports a section file can declare (eager, layout, cache, sync, LoadingFallback and the rest), what each one changes, and how they reach the runtime.
- [Deferred sections](https://docs.decocms.com/storefront/blocks/v7/rendering.md): How sections that editors mark async in Studio render as a skeleton first and load afterwards, which sections get deferred, and how to configure it.
- [Images, scripts and UI helpers](https://docs.decocms.com/storefront/blocks/v7/components.md): The React components and helpers sections use most, such as Image and Picture, LazySection, inline scripts, device detection, cookies, analytics events, load-more pagination and JSON-LD.
- [SEO](https://docs.decocms.com/storefront/blocks/v7/seo.md): Where a page's title, description, canonical URL and structured data come from, how each binding writes them into the head, and how crawlers are treated.

## Storefront — Framework guides

- [TanStack Start on Cloudflare Workers](https://docs.decocms.com/storefront/blocks/v7/tanstack.md): Every file, option and component the TanStack Start binding gives a site that runs on Cloudflare Workers.
- [Next.js App Router](https://docs.decocms.com/storefront/blocks/v7/nextjs.md): The four surfaces of the Next.js binding in depth, how to render CMS pages as Server Components, and what the binding deliberately leaves out.
- [Storefront as an API](https://docs.decocms.com/storefront/blocks/v7/storefront-api.md): Serve loader results and whole CMS pages as JSON for native apps and other non-HTML clients.
- [Eitri apps](https://docs.decocms.com/storefront/blocks/v7/eitri.md): Use @decocms/eitri to generate the schema and content snapshot Studio needs to author content for an Eitri mobile app.

## Storefront — CLI

- [Code generation](https://docs.decocms.com/storefront/blocks/v7/generate.md): What the generate command produces from your content and source, when each generator runs, how its cache works, and every flag.
- [CLI reference](https://docs.decocms.com/storefront/blocks/v7/cli.md): Synopsis, flags, defaults and exit codes for every command in @decocms/blocks-cli and @decocms/eitri.

## Storefront — Apps

- [Apps](https://docs.decocms.com/storefront/blocks/v7/apps.md): What a Deco app is, how a site installs and configures one, and which apps exist today.
- [Commerce types and utilities](https://docs.decocms.com/storefront/blocks/v7/apps-commerce.md): The shared commerce vocabulary every platform app returns, the Cart v2 contract, and small helpers for prices, links, offers and analytics.
- [Website app](https://docs.decocms.com/storefront/blocks/v7/apps-website.md): The generic, non-commerce half of a site: SEO sections, analytics tags, theme and fonts, video, and the secret and environment loaders.
- [VTEX](https://docs.decocms.com/storefront/blocks/v7/vtex.md): Configure the VTEX app, register its cached commerce loaders, wire checkout, segments and sitemaps into the Worker, and build the cart with Cart v2.
- [Shopify](https://docs.decocms.com/storefront/blocks/v7/shopify.md): Connect a site to the Shopify Storefront API for product pages, listings, shelves, carts and customer sign-in.
- [Wake](https://docs.decocms.com/storefront/blocks/v7/wake.md): Connect a site to Wake Commerce for catalog pages, search, carts, wishlists and checkout routing.
- [Magento](https://docs.decocms.com/storefront/blocks/v7/magento.md): The partial Magento app: configuration, cart, user and wishlist loaders, a few actions, a shared response cache and an instrumented fetch.
- [Salesforce Personalization](https://docs.decocms.com/storefront/blocks/v7/salesforce.md): Product recommendations from Salesforce Marketing Cloud Personalization, as three stateless loaders.
- [Algolia](https://docs.decocms.com/storefront/blocks/v7/algolia.md): A shared, configured Algolia v5 client for writing your own search loaders.
- [Blog](https://docs.decocms.com/storefront/blocks/v7/blog.md): Write blog posts, categories and authors in Studio, and list, page, search and render them with SEO and structured data.
- [Resend](https://docs.decocms.com/storefront/blocks/v7/resend.md): Send transactional email, such as contact-form messages, through Resend.

## Storefront — Production

- [Deploying and Fast Deploy](https://docs.decocms.com/storefront/blocks/v7/releases.md): Deploy v7 code and repository content; configure optional Fast Deploy runtime/KV delivery separately from Studio's GitHub publish workflow.
- [Caching](https://docs.decocms.com/storefront/blocks/v7/caching.md): The cache layers of a v7 site, the cache profiles that configure them, and how to segment, debug and purge the edge cache.
- [Observability](https://docs.decocms.com/storefront/blocks/v7/observability.md): The traces, metrics and logs a v7 site emits, how to send them to your OpenTelemetry collector, and how to instrument your own code.
- [Speculation rules](https://docs.decocms.com/storefront/blocks/v7/speculation-rules.md): Let the browser prefetch or prerender the next page before a click, on TanStack Start sites, without double-counting analytics.
- [Troubleshooting](https://docs.decocms.com/storefront/blocks/v7/troubleshooting.md): Symptoms you may hit on a v7 site, what causes each one, and how to fix it.

## Storefront — Upgrading

- [Upgrading from @decocms/start 6.x](https://docs.decocms.com/storefront/blocks/v7/upgrade-from-start.md): Move a TanStack Start site from the single @decocms/start 6.x and @decocms/apps 5.x packages to the split v7 packages.
- [Migrating from Fresh and Deno](https://docs.decocms.com/storefront/blocks/v7/migrate-from-fresh.md): Move a Deco storefront from Fresh, Preact and Deno to TanStack Start, React 19 and Cloudflare Workers with the deco-migrate tooling.
- [Going live after a migration](https://docs.decocms.com/storefront/blocks/v7/migration-cutover.md): Check a migrated storefront against the live Fresh site and move traffic to it gradually.
- [Moving a Next.js site off @decocms/start 5.x](https://docs.decocms.com/storefront/blocks/v7/nextjs-from-start.md): Replace the @decocms/start 5.x /core, /next and /node imports of a Next.js site with @decocms/blocks, @decocms/blocks-admin and @decocms/nextjs.

## Storefront — Reference

- [Packages and exports](https://docs.decocms.com/storefront/blocks/v7/packages.md): Every v7 package, every import path it exposes, and which ones are safe in browser code.
- [Configuration reference](https://docs.decocms.com/storefront/blocks/v7/configuration.md): Every environment variable, binding and setup option a v7 site reads, in one place.
- [Glossary](https://docs.decocms.com/storefront/blocks/v7/glossary.md): The terms used throughout the v7 docs, each with a short definition and a pointer to where it's explained.

## Storefront — Site Editor

- [Site Editor](https://docs.decocms.com/storefront/editor/overview.md): Edit storefront content in Studio with a preview and a Git-backed publishing workflow.
- [Connect a site](https://docs.decocms.com/storefront/editor/connect-site.md): Configure the repository, content editing, and preview server for a Studio site project.
- [Storefront and Studio](https://docs.decocms.com/storefront/editor/digital-experience.md): Understand the relationship between the storefront offering and the extensible Studio platform.
- [Content editing with agents](https://docs.decocms.com/storefront/editor/agentic-cms.md): Combine visual content editing and agent-assisted development in the storefront project.
- [Create and edit pages](https://docs.decocms.com/storefront/editor/content/pages.md): Compose a page from registered sections and preview real URLs before publishing.
- [Edit and reuse sections](https://docs.decocms.com/storefront/editor/content/sections.md): Configure components, share saved sections, and detach local copies when needed.
- [Publish changes](https://docs.decocms.com/storefront/editor/content/releases.md): Review a draft, publish under the project policy, or submit it for approval.
- [Upload and select assets](https://docs.decocms.com/storefront/editor/content/assets.md): Use the site asset browser and image fields with configured storage.
- [Edit and schedule blog posts](https://docs.decocms.com/storefront/editor/content/blog.md): Manage posts with the blog app installed by your storefront.
- [Configure and run loaders](https://docs.decocms.com/storefront/editor/advanced/loaders.md): Inspect available data functions and save reusable input configurations.
- [Configure and run actions](https://docs.decocms.com/storefront/editor/advanced/actions.md): Configure registered actions and understand the effect of invoking them.
- [Configure storefront apps](https://docs.decocms.com/storefront/editor/advanced/apps.md): Edit configuration blocks for installed integrations through the Site Editor.
- [Configure page and section variants](https://docs.decocms.com/storefront/editor/advanced/segments.md): Use matcher-driven content variants and preview the selected experience.
- [Create URL redirects](https://docs.decocms.com/storefront/editor/advanced/redirects.md): Redirect old paths through the site redirect loader and check query parameter behavior.
- [Configure SEO](https://docs.decocms.com/storefront/editor/advanced/seo.md): Set site defaults and page overrides using the storefront SEO schema.

## Storefront — Templates

- [Website templates](https://docs.decocms.com/storefront/templates/overview.md): Start with a working website implementation, then adapt its sections, content, and commerce integration.
- [Storefront TanStack](https://docs.decocms.com/storefront/templates/storefront-tanstack.md): Use the public TanStack Start storefront implementation as the starting point for your website.

## Storefront — Commerce

- [Commerce overview](https://docs.decocms.com/storefront/commerce/overview.md): Configure commerce integrations for the released Blocks 7.x framework.
- [VTEX overview](https://docs.decocms.com/storefront/commerce/vtex/overview.md): Connect a released Blocks 7.x storefront to VTEX with registered provider modules.
- [VTEX loaders and actions](https://docs.decocms.com/storefront/commerce/vtex/loaders-and-actions.md): Server-side data fetch and mutation API for VTEX.
- [VTEX client and middleware](https://docs.decocms.com/storefront/commerce/vtex/client-and-middleware.md): vtexFetch family, intelligentSearch, fetchCache, extractVtexContext, propagateISCookies.
- [VTEX hooks](https://docs.decocms.com/storefront/commerce/vtex/hooks.md): Cart v2 (createCart, useAddToCart, useCartSummary), plus useCart, useUser, useWishlist, useAutocomplete for the browser.
- [VTEX inline loaders](https://docs.decocms.com/storefront/commerce/vtex/inline-loaders.md): createVtexCommerceLoaders, CMS-shaped page loaders for PDP, PLP, shelf, search.
- [VTEX gotchas](https://docs.decocms.com/storefront/commerce/vtex/gotchas.md): Cookies, sales channel, expectedOrderFormSections, regionId, IS sort sanitization, README drift.
- [Shopify](https://docs.decocms.com/storefront/commerce/shopify.md): Configure Shopify for a Blocks 7.x storefront and wire server-side products, carts, and customers.
- [Resend](https://docs.decocms.com/storefront/commerce/resend.md): Configure transactional email for a Blocks 7.x site.
- [Shared commerce](https://docs.decocms.com/storefront/commerce/shared.md): schema.org types, useOffer, formatPrice, analytics, useVariantPossibilities, Image / Picture / JsonLd.

## Storefront — Migration

- [Migration overview](https://docs.decocms.com/storefront/migration/overview.md): Move a retired Fresh/Deno storefront to the released Blocks 7.x runtime.
- [Migration checklist](https://docs.decocms.com/storefront/migration/checklist.md): Walk through this list before merging a migration PR.
- [Migration playbook](https://docs.decocms.com/storefront/migration/playbook.md): Phase-by-phase walkthrough of moving a Fresh storefront to TanStack Start.
- [Migrate script](https://docs.decocms.com/storefront/migration/migrate-script.md): What npx -p @decocms/blocks-cli deco-migrate actually does.
- [Migrate from Fresh](https://docs.decocms.com/storefront/migration/migrate-from-v1.md): Move a Fresh/Deno deco.cx storefront to TanStack Start.
- [Agent skills](https://docs.decocms.com/storefront/migration/agent-skills.md): Use Claude Code, Cursor, Codex, or any AI coding tool to drive the migration.
- [Validate & capture with parity](https://docs.decocms.com/storefront/migration/parity.md): Use parity to extract a live storefront and validate the migrated site — see the Parity section.

## Storefront — Migration validation

- [Parity overview](https://docs.decocms.com/storefront/migration/parity/overview.md): A CLI that captures a live storefront into an agent-ready bundle and validates a migrated site against the original.
- [parity journey](https://docs.decocms.com/storefront/migration/parity/journey.md): Run only the purchase journey, step-by-step, prod vs cand — the tightest CI loop.
- [Commands reference](https://docs.decocms.com/storefront/migration/parity/commands.md): Every parity command — inspect probes, run management, and the full flag surface.
- [Configuration](https://docs.decocms.com/storefront/migration/parity/config.md): .parityrc.json selectors + run defaults, .parityignore noise filters, and environment variables.
- [Checks reference](https://docs.decocms.com/storefront/migration/parity/checks.md): Every check parity runs, what it catches, and its module (the --only/--skip scoping key).
- [parity run](https://docs.decocms.com/storefront/migration/parity/run.md): Compare two URLs (prod × cand) and produce a parity report — with module selection for focused runs (SEO, visual, cache, vitals, DOM/CSS).
- [parity extract](https://docs.decocms.com/storefront/migration/parity/extract.md): Single-site, AI-ready component extraction — HTML, computed styles, screenshots, assets per component.
- [parity migrate](https://docs.decocms.com/storefront/migration/parity/migrate.md): Phased, target-agnostic capture of a live storefront into an agent-ready migration bundle.
- [CI/CD & workflows](https://docs.decocms.com/storefront/migration/parity/ci.md): Gate PRs with parity in GitHub Actions, and drive an AI fix loop from the report.
- [Performance (vitals & cache)](https://docs.decocms.com/storefront/migration/parity/performance.md): Compare Web Vitals and cache coverage across many pages, prod vs cand.
- [Pixel-perfect (fix & section)](https://docs.decocms.com/storefront/migration/parity/pixel-perfect.md): Diff one section between prod and cand — screenshots, pixelmatch heatmap, computed styles — into an LLM-ready bundle.
- [Single-site (e2e & audit)](https://docs.decocms.com/storefront/migration/parity/single-site.md): Validate ONE live URL end-to-end — no prod baseline. For pre-launch and partner audits.

## Storefront — Hosting

- [Hosting and deployment](https://docs.decocms.com/storefront/hosting/overview.md) [IN BUILD]: Deploy your storefront, manage previews, and distinguish site hosting from Studio hosting

## Storefront — Additional reference

- [SDK utilities](https://docs.decocms.com/storefront/blocks/v7/framework/sdk-utilities.md): Verified SDK examples for encoding, redirect maps, server timing and connection-closed retries.
- [Framework package export maps (7.43.0)](https://docs.decocms.com/storefront/blocks/v7/reference/package-exports.md): Verified export maps for the packages published at version 7.43.0.
- [Commerce package export maps (7.43.0)](https://docs.decocms.com/storefront/blocks/v7/reference/commerce-exports.md): Verified export maps for the packages published at version 7.43.0.

## Storefront — Engineering reference

- [How v7 is built](https://docs.decocms.com/storefront/blocks/v7/internals.md): Why v7 ships as separate packages of plain TypeScript source, how runtime state stays single, and which entry points are safe for the browser.
- [How resolution works](https://docs.decocms.com/storefront/blocks/v7/walkthrough.md): What the runtime does to turn a page block's JSON into sections ready to render, in order, with a worked example.
- [The Worker request pipeline](https://docs.decocms.com/storefront/blocks/v7/request-pipeline.md): Everything createDecoWorkerEntry does with a request on TanStack Start, in order, from opening the request scope to the edge cache and the response headers.

## Studio — Getting started

- [What is Studio](https://docs.decocms.com/studio/get-started/what-is-deco.md): An extensible platform for connecting context, organizing work, and running agents
- [Quickstart](https://docs.decocms.com/studio/get-started/quickstart.md): From zero to a working agent in 5 minutes
- [Key concepts](https://docs.decocms.com/studio/get-started/core-concepts.md): How deco Studio is organized and how the pieces fit together
- [Architecture](https://docs.decocms.com/studio/get-started/architecture.md): How Studio is wired end to end — edge, cloud cluster, and desktop — and how requests, runs, and sandboxes flow between the tiers.

## Studio — Workflows and delivery

- [Workflows and delivery](https://docs.decocms.com/studio/agency/overview.md): Connect signals and context to tasks, execution, and review
- [Tasks & the board](https://docs.decocms.com/studio/agency/tasks.md): Where demand becomes work — the columns, the repository, the pull request, the preview
- [Writing a task](https://docs.decocms.com/studio/agency/writing-a-task.md): Removing ambiguity before an agent starts — the highest-leverage thing you do here
- [Reviews & QA](https://docs.decocms.com/studio/agency/reviews-and-qa.md): How a change gets checked before and after it ships
- [Signals & monitoring](https://docs.decocms.com/studio/agency/signals.md) [IN BUILD]: How problems get found before you report them
- [Objectives](https://docs.decocms.com/studio/agency/objectives.md) [NOT BUILT YET]: A goal with a metric and a budget, per project — what tasks get measured against

## Studio — Connections and agents

- [Agents](https://docs.decocms.com/studio/agents/overview.md): The working surface of Studio — one agent, one job, its own thread history and tools
- [Connections](https://docs.decocms.com/studio/agents/connections.md): Connect tools and services to Studio — once, securely, for your whole team
- [Automations](https://docs.decocms.com/studio/agents/automations.md): Run an agent on a schedule or in response to an event — without a human in the loop
- [AI Providers](https://docs.decocms.com/studio/agents/ai-providers.md): Connect the AI models that power Decopilot and your agents
- [Monitoring](https://docs.decocms.com/studio/agents/monitoring.md): See every tool call your agents make — who, what, when, and how it performed
- [Overview](https://docs.decocms.com/studio/agents/decopilot/overview.md): The AI assistant built into deco Studio
- [Context and tasks](https://docs.decocms.com/studio/agents/decopilot/context-and-tasks.md): How Decopilot manages memory and how to use subtasks for heavy work
- [Tools](https://docs.decocms.com/studio/agents/decopilot/tools.md): What Decopilot can do, and the two kinds of tools it has access to
- [Voice mode](https://docs.decocms.com/studio/agents/decopilot/voice-mode.md): Talk to the current Studio agent while keeping the same chat and preview

## Studio — MCP Apps and extensions

- [Creating Agents](https://docs.decocms.com/studio/build/no-code/creating-agents.md): Configure a focused role, instructions, and selected connection tools in Studio
- [Creating Tools](https://docs.decocms.com/studio/build/no-code/creating-tools.md): Add focused virtual tools that combine connected capabilities without scaffolding an MCP server
- [Project Structure](https://docs.decocms.com/studio/build/full-code/project-structure.md): Understand the full-stack TypeScript architecture of MCP Apps on deco
- [Building Tools](https://docs.decocms.com/studio/build/full-code/building-tools.md): Build MCP tools in TypeScript with full type safety
- [Building MCP Apps](https://docs.decocms.com/studio/build/full-code/building-views.md): Build interactive UIs for MCP tools using the MCP Apps SDK
- [Resources](https://docs.decocms.com/studio/build/full-code/resources.md): Serve MCP App UIs and data as MCP resources
- [Deployment](https://docs.decocms.com/studio/build/full-code/deployment.md): Build and deploy your MCP App

## Studio — Data & content

- [Buckets](https://docs.decocms.com/studio/data/buckets.md): Connect your own S3-compatible bucket for CMS assets — and the IAM permissions it needs
- [Library](https://docs.decocms.com/studio/data/library.md): A Drive-like browser for your organization's shared filesystem
- [MCP catalog](https://docs.decocms.com/studio/data/store.md): Find MCPs in the Deco registry

## Studio — Deploy and self-host Studio

- [Quickstart](https://docs.decocms.com/studio/self-hosting/quickstart.md): Run Studio locally or deploy to your infrastructure
- [Authentication](https://docs.decocms.com/studio/self-hosting/authentication.md): Supported auth methods and how to configure them for self-hosting
- [Monitoring](https://docs.decocms.com/studio/self-hosting/monitoring.md): How to persist and query monitoring data in self-hosted deployments
- [Linux Desktop Support](https://docs.decocms.com/studio/self-hosting/linux-desktop-support.md): Supported architecture, prerequisites, and known limitations for the Linux desktop app
- [Docker Compose](https://docs.decocms.com/studio/self-hosting/deploy/docker-compose.md): Deploy deco Studio locally using Docker Compose for testing and development
- [Kubernetes](https://docs.decocms.com/studio/self-hosting/deploy/kubernetes.md): Deploy deco Studio and agent sandboxes on Kubernetes using Helm

## Studio — Reference

- [Glossary](https://docs.decocms.com/studio/reference/glossary.md): The platform concepts used to connect context, organize work, and extend Studio.
- [API Keys](https://docs.decocms.com/studio/reference/api-keys.md): Create scoped API keys to access management tools, proxies, and agents
- [Secrets](https://docs.decocms.com/studio/reference/secrets.md): Store API keys, tokens, and sensitive values — encrypted, scoped, and never returned over the API
- [User Management](https://docs.decocms.com/studio/reference/user-management.md): Control who can access your organization and what they're allowed to do
- [Connection Proxy Endpoint](https://docs.decocms.com/studio/reference/api/connection-proxy.md): Connect MCP clients directly to upstream MCP servers through deco Studio
- [Call an Agent from Your App](https://docs.decocms.com/studio/reference/api/external-agent-integration.md): Drive a Studio agent from an external system with a scoped API key — create a thread, run the agent, stream the response, and read the thread back