Adding an official MCP App validator

Open
#673 1 comment 6 reactions 1 assignee View on GitHub

@liady is already working on this.

Since May 27, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement

We should provide an official validator for MCP Apps that lives in the same repo as the spec and SDK. Today there's no canonical way to check whether an app conforms - authors hit problems at runtime, and hosts end up enforcing slightly different subsets of the rules.
A first-party validator gives authors a single source of truth for conformance (manifest structure, capability negotiation, declared view mimetypes, and so on) and lets hosts rely on a shared definition of "valid" instead of each reimplementing their own checks.

refarding co-location: the validator stays in lockstep with spec changes rather than drifting in a separate repo or userland. It also doubles as executable documentation of the rules - when the spec adds or changes a constraint, the validator and its test fixtures get updated in the same PR.

Open questions:

  • Scope (static/schema validation only, or runtime/behavioral checks too?)
  • How it's exposed (CLI, library API, or both)
  • Whether it shares types directly with the SDK
  • What counts as an error vs. a warning
Dominant language
TypeScript
Stars
2.9k
Forks
387
Avg merge
3h 21m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/ext-apps

All issues in modelcontextprotocol/ext-apps

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.