# text.parts > Shared, themeable app components and validated JSON interfaces for the txt ecosystem. Build interfaces with json-render; operate supported components through UI SDK and WebMCP; keep storage, sync and permissions in the host. ## Start here - [Full agent guide](https://text.parts/llms-full.txt): architecture, working recipe, runtime instructions, capabilities and limits. - [Create an interface](https://text.parts/parts): compose a notebook, edit its JSON or generate a recipe from a prompt. - [Agent runtime sandbox](https://text.parts/parts/agents): actual UI SDK/WebMCP with synthetic, tab-local content. - [Component contracts](https://text.parts/parts/manifest.json): app ownership, source paths, actions, dependencies and runtime capabilities. - [Source inventory](https://text.parts/parts/source.json): generated import graph and hashes. Reachability is not proof of runtime support. - [Browse source](https://text.parts/parts/source): discover the reusable source library. This is not a published text.parts npm package. - [App components](https://text.parts/parts/apps): specialist parts from the apps. - [List parts](https://text.parts/parts/lists): full/embedded list presentations, fields, filtering, maps and themes. - [Live site studio](https://text.parts/parts/sites): schema-generated record forms, instant page previews and authenticated CM.Systems releases. - [Theme studio](https://theme.parts/): portable validated theme recipes, previewed on sites, notes and lists. Also at https://text.parts/parts/themes. - [Site recipe catalog](https://text.parts/parts/sites/catalog.json): site design format and layouts. - [Theme catalog](https://text.parts/parts/themes/catalog.json): shared theme format, bases and controls. - [CMS parts](https://text.parts/parts/cms): schema-driven forms, tables, cards, detail views and release previews. - [CMS UI catalog](https://text.parts/parts/cms/catalog.json): the separate CMS json-render catalog and bindings. - [Sync contracts](https://text.parts/parts/sync): revisions and component-change coordination. - [Filesystem guide](https://api.txt.mn/llms.txt): the shared txt HTTP/CLI/MCP foundation. - [Full filesystem API guide](https://api.txt.mn/llms-full.txt): live API and MCP reference. ## Architecture Files + host controllers + sync + Dots access are the foundation. n0t.es is the shared reading/editing surface. my-li.st, cm.systems, prompt.cat, 0utlin.es, pubs.li and f-il.es contribute specialist app components. text.parts is their component directory, source contract and interface playground. The same file may appear through several interfaces. A layout recipe does not create a second data store or grant access. Use existing host commands for edits and persistence. Dots identity, group membership and resource roles are evaluated by the host/server; component JSON is not an authorization channel. ## Agent entry points Browser tools are registered through document.modelContext when the browser supports WebMCP. On the studio and runtime sandbox: text_parts_catalog, text_parts_layout, text_parts_validate, text_parts_preview. Generated writing components expose snapshot, query and act using @ui-sdk/svelte. These are browser tools, not HTTP API paths. Requested dedicated remote MCP endpoint: https://mcp.text.parts/ Status: planned; not deployed or connected by the text.parts runtime release. The endpoint is the root URL; do not append an MCP path. Existing authenticated remote txt file tools remain at https://txt.mn/mcp. An in-chat ChatGPT/Codex UI additionally needs the MCP Apps UI-resource/host adapter, which is not yet deployed. Browser WebMCP alone does not embed an app into a conversation. ## Supported today - Constrained json-render recipes, preview, themes and explicit save/export. - UI SDK direct value actions for generated NoteTitle and NoteEditor. - Host permission checks and read-only/mode enforcement for accepted edits. - Shared list readers with compact note embeds and standalone presentations. - CMS schema proposals from prompts, selected text files/folders and public pages through the authenticated CM.Systems flow. - Source/contract discovery for the app component library. ## Scope boundaries Direct agent-action adapters for lists, CMS and other specialist components are not complete. A component in the source inventory is not automatically available in a generated notes recipe. Notes and CMS use separate validated catalogs. Native/messaging source starters do not establish runtime parity. This release did not test a live Dots group collaboration session or deploy the dedicated MCP Apps server. Use the full guide for validated formats and exact tool behavior.