Frontier Now
Search

Gateways

mcp-use: build, debug and ship MCP servers in TypeScript

A full-stack TypeScript MCP framework: Zod types flow from tools to results, React views bind to tools as MCP Apps, and a browser Inspector is built in.

Author
Frontier Now Editorial
Published

Project and installation docs

View project

https://github.com/mcp-use/mcp-use

Building an MCP server for your product on the official SDK means wiring up transports, types and debugging yourself, and showing an interactive UI inside ChatGPT or Claude is another round of plumbing. mcp-use is a TypeScript framework whose scaffold gives you the server, dev scripts, an Inspector and a React view pipeline. Tool inputs and outputs are Zod schemas, and the types carry through to the UI components.

What it does

  • End-to-end types: server.tool() declares inputSchema and outputSchema in Zod; structured results, view props and tool calls share those types, and MCP annotations like readOnlyHint sit right on the tool.
  • Native views: a React component in views/<name>/view.tsx that matches the tool’s view.name becomes an interactive UI in clients that support MCP Apps.
  • Built-in debugging: the dev server includes an Inspector at http://localhost:3000/mcp/inspector to list and call tools and preview views, with a headless CLI option.
  • Agent-friendly: you can hand a coding agent one prompt and have it scaffold, test and deploy the server.

Who it’s for

  • TypeScript developers building an MCP server, ChatGPT app or Claude connector for their SaaS.
  • Product teams that want tool results to render as charts, cards or other interactive UI.

Setup

Needs Node.js. Scaffold a project, start the dev server, then open the Inspector:

npx -y create-mcp-use-app@latest
npm run dev

Our take

About 10.7k stars as of 2026-10-06, and one of the most active MCP frameworks. It’s a different kind of entry from the rest of this directory: it’s a tool for building servers, which agents themselves never call. Compared with the official TypeScript SDK alone, it removes the typing and debugging boilerplate, and MCP Apps view support is the clearest difference. Note that v2 has breaking changes from v1, so older projects need the migration guide. The README’s deploy link points to the Manufact hosting platform, but you can deploy the generated server yourself. Licensed MIT.