mcp-typescript-template vs openai-apps-sdk-examples

Two of the top mcp servers and chat-host apps, side by side: score, setup, license, activity and what each review found.

11st of 5 in MCP servers and chat-host apps

mcp-typescript-template

Express and Effect template for a stateless remote MCP server

60 out of 100
#44th of 5 in MCP servers and chat-host apps

openai-apps-sdk-examples

Example MCP servers and widgets for ChatGPT apps on the Apps SDK

32 out of 100
mcp-typescript-template vs openai-apps-sdk-examples: score parts and facts
What we comparemcp-typescript-templateopenai-apps-sdk-examples
Score parts, out of 100
Adoption0, niche72, popular
Freshness100, active68, recent
Maintenance99, healthy1, weak
Easy to run50, easy0, hard
Agent-ready85, ready0, none
Facts from GitHub and the README
Stars582.4k
LicenseMIT (permissive)MIT (permissive)
Last commitOct 2026Apr 2026
Last releaseSep 2026None published
LanguageTypeScriptTypeScript
DockerYesNo
GPUNot neededNot needed
arm64 or Apple SiliconNot statedNot stated

mcp-typescript-template

TypeScript 7 project serving a stateless MCP endpoint at /mcp on port 3000 via Express and createMcpHandler from the MCP TypeScript SDK, with Effect for config, logging and errors. Ships echo and elicit_echo tools with outputSchema, structuredContent and annotations, HTTP-boundary and in-memory tests, a Dockerfile and compose with a /health check. For TypeScript teams starting a remote MCP server; no auth.

Who it is for: TypeScript developers building a remote MCP server

Strengths

  • Stateless per the 2026-07-28 spec with SDK fallback for older clients
  • Tests at the HTTP boundary and against an in-memory client
  • Typed tool I/O via Effect Schema adapted to MCP Standard Schema
  • Dockerfile and docker-compose with health check

Weaknesses

  • No auth or OAuth; remote hosts will need it
  • Effect is a hard dependency with a learning curve
  • TypeScript 7 compiler plus a TS6 alias for ESLint is unusual tooling
  • TypeScript, MCP TypeScript SDK (@modelcontextprotocol/server)
  • GitHub template
  • Docker

openai-apps-sdk-examples

pnpm workspace with React widget sources, a Vite build that emits hashed HTML/JS/CSS bundles served on port 4444, and paired MCP servers in Node and Python (Pizzaz, kitchen-sink-lite, solar system, shopping cart, an OAuth-gated example). Widgets use the window.openai host API and _meta.ui.resourceUri to render inside ChatGPT. For developers building ChatGPT apps; test via developer mode and an ngrok tunnel.

Who it is for: Developers building ChatGPT apps with MCP and widgets

Strengths

  • Node and Python MCP servers for the same widgets
  • kitchen-sink-lite covers the full window.openai host API surface
  • Shopping-cart example shows widgetSessionId state across tool calls
  • Authenticated server demonstrates OAuth-gated tools

Weaknesses

  • Examples only; no persistence or deploy config beyond BASE_URL
  • Requires ChatGPT developer mode and a public tunnel to test
  • Chrome 142+ needs a flag change to render widgets locally
  • Maintainers may not review all PRs
  • TypeScript, OpenAI Apps SDK, MCP TypeScript SDK, MCP Python SDK
  • Needs ChatGPT developer mode, ngrok or a public host for testing

More in MCP servers and chat-host apps