Remote MCP Server using Descope's MCP Auth SDK (Express) and Fly.io

Introduction

This example shows how to add auth to a Remote MCP Server using Descope's MCP Auth SDK (Express) and deploy it to Fly.io. It handles fetching weather-related data.

Preview

This MCP Server is deployed to Fly.io here: https://mcp-server-weather-ez9f9a.fly.dev

You can connect to the server using the Cloudflare Playground, MCP Inspector or any other MCP client. Be sure to include the /sse path in the connection URL.

Features

• Real-time weather data streaming
• Secure authentication using Descope
• MCP Authorization Compliant

Requirements

Before proceeding, make sure you have the following:

• Node.js (version 18 or later)
• A valid Descope Project ID and Management Key
• The Descope Inbound Apps feature enabled
• Git installed

Running the Server

First, add the environment variables in a .env file at the root:

DESCOPE_PROJECT_ID=      # Your Descope project ID
DESCOPE_MANAGEMENT_KEY=  # Your Descope management key
SERVER_URL=             # The URL where your server is hosted

Then, install dependencies:

npm i

Finally, run the server:

npm run dev

The server will start on port 3000 (or the port specified in your environment variables).

API Endpoints

• GET /sse: Establishes an SSE connection for real-time weather data
• POST /message: Handles incoming messages for the MCP protocol

Authentication

The server uses Descope for authentication. All MCP endpoints except the authentication router require a valid bearer token.