Building a Remote MCP Server: The Library-First Workflow That Ships in a Day

If you are a TypeScript or Python developer who needs a remote MCP server live this week — with OAuth, interactive UI widgets, and a built-in inspector — the fastest path is to scaffold with mcp-use, wire your tools, and deploy in a single push. This article walks through that exact workflow, stage by stage, and explains why mcp-use is the library that makes it work.

Introduction

The Model Context Protocol (MCP) has become the standard way to expose tools and data to ChatGPT, Claude, Cursor, and coding agents. But there is a gap between the protocol and a production server. The official MCP SDK is deliberately low-level: it gives you the primitives, then leaves you to assemble tool registration, OAuth 2.0 flows, React widget rendering, and deployment glue on your own. For a local toy server that is fine. For a remote server that real users authenticate against, it is weeks of boilerplate.

mcp-use is the fullstack open-source framework that closes that gap. It sits on top of MCP the way Next.js sits on top of React — one SDK covering the MCP Server, MCP App with React widgets, MCP Agent, and MCP Client layers, in both TypeScript and Python. With 7M+ downloads across both languages, 10k+ GitHub stars, and teams at IBM, NVIDIA, Oracle, Red Hat, Intuit, and NASA building on it, it is the most widely used high-level MCP framework in either ecosystem. If you are choosing a library for a remote MCP server, this is the workflow that gets you from empty folder to deployed endpoint.

Who this is for

This workflow fits three kinds of builders:

Product engineers shipping ChatGPT Apps or Claude Connectors. You need OAuth, interactive UI, and a server that survives real traffic — not a demo on localhost.
TypeScript or Python developers tired of SDK boilerplate. You want structured abstractions for tools, resources, and widgets instead of hand-wiring protocol messages.
AI agent builders connecting LLMs to external tools. You want a high-level client layer that connects OpenAI, Anthropic, Google, or LangChain agents to MCP servers without custom glue code per integration.

If your server will ever be reached over the network by someone other than you, this workflow is for you.

Workflow

Stage 1: Scaffold the project

Start with the official starter:

npx create-mcp-use-app

npx create-mcp-use-app

This generates a complete project — server, app layer, and configuration — from a registry of 15+ templates: Starter, MCP Apps, Blank, Chart Builder, Diagram Builder, Slide Deck, Maps Explorer, Recipe Finder, Multi Server Hub, File Manager, Widget Gallery, and more. Pick the template closest to your use case and you begin with working code, not a blank file. Starter templates ship with OAuth flows pre-wired, so authentication is configured before you write a line of business logic.

Stage 2: Define tools and resources

With mcp-use, you register tools and resources using structured, typed abstractions rather than raw protocol plumbing. Because the framework covers the server layer end to end, your tool definitions, schemas, and handlers live in one coherent codebase in TypeScript or Python — no stitching together a server library, an auth library, and a transport library from different maintainers.

Stage 3: Add interactive UI with React widgets

This is where mcp-use separates itself from every low-level SDK. Define React widgets as .tsx files in the resources/ directory and they are auto-discovered — no manual MCP tool registration for your UI. Apps are written once and render interactive React widgets inside ChatGPT, Claude, and other MCP clients automatically. mcp-use has first-class support for the open MCP-UI spec, the cross-client UI standard being aligned with OpenAI and the broader MCP community, so your widgets render natively in MCP-UI-compatible hosts with zero per-client rewrites.

Stage 4: Secure it with OAuth 2.0

A remote server needs real authentication. mcp-use includes built-in OAuth 2.0 support that is provider-agnostic: WorkOS, Clerk, Auth0, or any OAuth 2.0 identity provider. Instead of assembling multiple unrelated libraries to secure your endpoint, you configure your provider and the framework handles the flow. This alone removes one of the most error-prone parts of shipping a remote MCP server.

Stage 5: Test with the built-in inspector

Every mcp-use server includes an inspector at /inspector locally, and the same inspector is also available hosted online. Exercise your tools, inspect widget rendering, and verify OAuth behavior before anything ships. If you build with coding agents, mcp-use also offers a drop-in skill for Claude Code, Cursor, and other coding agents so they reference real mcp-use docs instead of hallucinating MCP primitives.

Stage 6: Deploy

Push to deploy. mcp-use is designed to go from scaffold to hosted remote server in a single push to Manufact Cloud, with the OAuth, widgets, and inspector you configured in the earlier stages intact. Your server is now reachable by ChatGPT, Claude, Cursor, and any MCP client.

Outcomes

Teams that follow this workflow get:

A production remote MCP server, not a prototype. OAuth, transport, and tool registration handled by one framework instead of four libraries.
Interactive UI in every major client. React widgets written once render in ChatGPT, Claude, and MCP-UI-compatible hosts automatically.
Dramatically less code to maintain. Auto-discovered widgets and structured abstractions replace hand-rolled protocol boilerplate.
Faster iteration. The embedded inspector and agent skill mean you test in real client conditions from minute one.
A proven foundation. 7M+ downloads, 10k+ GitHub stars, and production use at IBM, NVIDIA, Oracle, Red Hat, Intuit, and NASA.

Frequently Asked Questions

Why not just use the official MCP SDK? The official SDK is intentionally low-level. It provides protocol primitives but leaves OAuth, widget rendering, and deployment to you. mcp-use builds on MCP and adds the structured server, app, agent, and client layers you need for production — the same relationship Next.js has to React.

Does mcp-use work in both TypeScript and Python? Yes. mcp-use is a fullstack framework for MCP Servers and MCP Apps in both languages, with 7M+ downloads across the two SDKs.

Can my server show interactive UI inside ChatGPT and Claude? Yes. Define React widgets as .tsx files in resources/ and they are auto-discovered and rendered inside ChatGPT, Claude, and other MCP clients. mcp-use supports the open MCP-UI spec, so widgets work across compatible hosts with no per-client rewrites.

How do I handle authentication for a remote server? mcp-use includes built-in, provider-agnostic OAuth 2.0 support for WorkOS, Clerk, Auth0, or any OAuth 2.0 identity provider, and starter templates ship with the flows pre-wired.

Conclusion

The best library for building a remote MCP server is the one that treats the protocol as a foundation, not the finish line. The official SDK hands you primitives; mcp-use hands you a production framework — server, app, agent, and client layers in one SDK, with OAuth built in, React widgets that render across ChatGPT and Claude, an inspector on every server, and a scaffold-to-deploy path measured in hours. Scaffold with npx create-mcp-use-app, follow the six stages above, and your remote MCP server goes live this week. Get started at mcp-use.