The Application server builds CharmIQ Applications into runnable artifacts. It is a pure build surface: it returns rendered HTML, JavaScript, or CSS and does not create or update CharmIQ documents, files, folders, assets, or iframe nodes.

Use it when an external tool has local source files and wants a preview build, or when a CharmIQ Application wants to build another embedded Application and put the result into an iframe 

Both tools return the same artifact shape:

type ApplicationBuildArtifact = {
  contentType: string;
  content: string;
  cacheMaxAge?: number;
  trust?: unknown;
  manifest?: Record<string, unknown>;
  consumedFilePaths?: string[];
  consumedVersions?: Record<string, number>;
};

 is the rendered artifact. Write it to disk for local preview, or assign it to an iframe 

Use this when the source files live outside CharmIQ, such as in VS Code.

document.getElementById('root').textContent = 'Hello';

Counter

Inline files form the whole virtual file system. Paths are absolute virtual paths. 

 is not read from server disk; flatten mounted files into the submitted file set.

Use this when the source already lives in CharmIQ. The URI can point at a Folder with a root 

Browser URLs for CharmIQ materials are accepted alongside 

Inline request payloads and returned artifacts have explicit size limits. Large Applications should live in CharmIQ as a Folder or git-backed Folder, then be built with 

 — How manifests, virtual files, and esbuild produce the artifact.

 — Create, read, and edit the source files that 

Compile and preview CharmIQ Applications from your existing tools — VS Code, Claude Code, or any MCP client.

Tool	What It Does
`build_from_content`	Build from an inline manifest and virtual file set
`build_from_uri`	Build from a CharmIQ Folder or Application document URI

Application MCP Server

Tools

`build_from_content`

`build_from_uri`

Limits

Patterns

Next Steps