Preview. The Allternit Apps SDK packages and the allternit CLI are not published to npm yet, so the install commands on this page do not work outside the Allternit repository today. To build an MCP App now, follow the Quickstart, which uses the open MCP SDK directly. Your app will not need changes to adopt the SDK later.
The Allternit Apps SDK is a set of small packages for building MCP Apps. A MCP App has three layers: The allternit CLI scaffolds, runs, tests, packages and submits an app.

Built on the open standard

Everything the SDK produces is plain MCP Apps (SEP-1865): a streamable-HTTP MCP server whose tools point at ui:// resources. The SDK adds no private protocol. An app built with it runs in any host that supports MCP Apps; Allternit-only features (window.allternit) are optional and feature-detected.

The packages

apps-server

defineApp, appTool, view, a streamable-HTTP starter and the allternit.app.json manifest.

apps-bridge

A typed, dependency-free client for the standard ui/* calls, plus window.allternit and a compatibility shim.

apps-ui

Web components for Views: Card, Table, List, Form, Detail.

look-packs

DTCG token types, a validator, CSS variable output and a contrast check.

The manifest

defineApp emits one manifest, allternit.app.json, listing the tools, Views, look pack and permissions. It carries the same plugin.json and mcp.json fields the plugin package uses, so the package is built from it with no second source of truth.
allternit.app.json
permissions is derived, not typed by hand: writes is true when any tool is not read-only, destructive when any tool is destructive, and network is every host the Views declare in their CSP. The install prompt and directory review read it.

Get started

Follow the Quickstart.