MCP Feature Reference Server

A production-ready example of a Model Context Protocol (MCP) server with OAuth 2.0 authentication, demonstrating best practices for secure, scalable MCP deployments.

What is this?

This repository provides a complete implementation of an MCP server that:

• Shows how to add authentication to MCP servers using OAuth 2.0
• Demonstrates all MCP protocol features (tools, resources, prompts)
• Uses a scalable architecture suitable for production deployments
• Serves as a learning resource and starting template for your own MCP servers

The Model Context Protocol is an open standard that enables seamless integration between AI applications and external data sources, tools, and services.

Why OAuth for MCP?

MCP servers often handle sensitive operations and data. This implementation shows how to:

• Authenticate users before granting access to MCP resources
• Integrate with existing identity providers (Auth0, Okta, Google)
• Implement user session isolation in multi-tenant environments
• Scale horizontally while maintaining security

Quick Start

Get the server running in 5 minutes:

# 1. Prerequisites
brew install orbstack       # macOS: Install OrbStack (skip if already installed)
orbctl start                # macOS: Start OrbStack daemon
# OR install Docker Desktop and start it (Windows/Linux/macOS alternative)

# 2. Setup
git clone https://github.com/modelcontextprotocol/example-remote-server.git
cd example-remote-server
npm install                 # Install dependencies for all workspaces

# 3. Start services
docker compose up -d        # Start Redis
npm run dev                 # Start both auth-server and mcp-server

# 4. Test with Inspector
npx -y @modelcontextprotocol/inspector

# Connect to http://localhost:3232/mcp
# (Make sure to include the http:// prefix!)

For detailed instructions, see Installation.

Repository Structure

This repository demonstrates a production-ready MCP deployment pattern with separate authorization and resource servers:

auth-server/             # OAuth 2.0 authorization server (demo only - replace in production)
  └── src/               # Authorization endpoints and token management

mcp-server/              # MCP resource server (customize tools/resources/prompts)
  └── src/               # MCP protocol implementation with external auth

scripts/                 # Testing and deployment scripts
docs/                    # Architecture and API documentation
examples/                # Example code and usage patterns

The architecture separates authentication concerns from MCP functionality, allowing you to integrate with commercial OAuth providers (Auth0, Okta, etc.).

Customizing for Your Use Case

This is a reference implementation with demo tools, resources, and prompts. To adapt it for production:

• Replace MCP features: See Customization Guide for replacing demo functionality with your own
• Integrate OAuth provider: See OAuth Architecture Patterns for production authentication setup

Usage Examples

Making Your First MCP Request

Once the servers are running, here's how to interact with them:

1. Register an OAuth Client

# Register your application with the auth server
curl -X POST http://localhost:3001/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "my-mcp-client",
    "redirect_uris": ["http://localhost:3000/callback"]
  }'

# Response:
# {
#   "client_id": "abc123...",
#   "client_secret": "xyz789...",
#   "client_name": "my-mcp-client"
# }

2. Get an Access Token

For testing, use the MCP Inspector which handles the OAuth flow automatically. For programmatic access, implement the OAuth 2.0 authorization code flow (see docs/oauth-flow.md).

3. Initialize MCP Session

# Initialize a new MCP session
curl -X POST http://localhost:3232/mcp \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "1",
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {},
      "clientInfo": {
        "name": "my-client",
        "version": "1.0"
      }
    }
  }'

# Response includes session ID for subsequent requests

4. Use MCP Features

# List available tools
curl -X POST http://localhost:3232/mcp \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Mcp-Session-Id: YOUR_SESSION_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "2",
    "method": "tools/list"
  }'

# Call a tool (echo example)
curl -X POST http://localhost:3232/mcp \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Mcp-Session-Id: YOUR_SESSION_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "3",
    "method": "tools/call",
    "params": {
      "name": "echo",
      "arguments": {
        "message": "Hello, MCP!"
      }
    }
  }'

For more examples, see the examples/ directory.

Understanding the Flow

sequenceDiagram
    participant User
    participant Client as Your App
    participant Auth as Auth Server (:3001)
    participant MCP as MCP Server (:3232)

    User->>Client: Wants to use MCP
    Client->>Auth: 1. Register & OAuth flow
    Auth->>User: 2. Login page
    User->>Auth: 3. Authenticate
    Auth->>Client: 4. Access token
    Client->>MCP: 5. MCP request + token
    MCP->>Auth: 6. Validate token
    Auth->>MCP: 7. Token valid ✓
    MCP->>Client: 8. MCP response
    Client->>User: 9. Results

The auth server is separate so you can easily replace it with Auth0, Okta, or any OAuth provider. See docs/oauth-architecture-patterns.md for integration guidance.

Table of Contents

• Quick Start
• Features
• Installation
• Configuration
• Architecture
• Development
  • Testing with MCP Inspector
  • Automated End-to-End Testing
• Common Issues & Solutions
• Technical Details
• API Reference
• Security
• Monitoring & Debugging
• Contributing

Features

MCP Protocol Features

• Tools: 7 demonstration tools including echo, add, long-running operations, LLM sampling, image handling, annotations, and resource references
• Resources: 100 example resources with pagination, templates, and subscription support
• Prompts: Simple and complex prompts with argument support and resource embedding
• Sampling: Integration with MCP sampling for LLM interactions
• Completions: Auto-completion support for prompt arguments
• Logging: Multi-level logging with configurable verbosity
• Notifications: Progress updates, resource updates, and stderr messages

Transport & Infrastructure

• Streamable HTTP: Full implementation with GET/POST/DELETE support
• SSE Transport: Backwards-compatible Server-Sent Events
• Redis Integration: Pub/sub message routing and session state management
• Session Management: 5-minute TTL with automatic cleanup
• Horizontal Scaling: Any instance can handle any request

Authentication & Security

• OAuth 2.0: Complete authorization flow with PKCE support
• Separate Auth Server: Demonstrates integration with external OAuth providers
• Token Introspection: Validates tokens via RFC 7662
• Session Ownership: User isolation and access control
• Security Headers: CSP, HSTS, X-Frame-Options, and more
• Bearer Token Auth: Middleware for protected endpoints

Installation

Prerequisites

• Node.js >= 16
• npm or yarn
• Docker runtime (for Redis)

Step 1: Install Docker Runtime

Choose one option:

macOS (Recommended: OrbStack)

brew install orbstack
# Start OrbStack daemon (required before using Docker commands)
orbctl start
# Or download from https://orbstack.dev/download

Windows/Linux: Docker Desktop

• Download from https://www.docker.com/products/docker-desktop
• Start Docker Desktop after installation

Alternative: Local Redis Installation

# macOS
brew install redis && brew services start redis

# Ubuntu/Debian
sudo apt-get install redis-server && sudo systemctl start redis

Step 2: Clone and Install Dependencies

git clone https://github.com/modelcontextprotocol/example-remote-server.git
cd example-remote-server
npm install  # Installs dependencies for all workspaces

Step 3: Start Redis

# Ensure Docker/OrbStack is running first!
docker compose up -d

# Verify Redis is running
docker compose ps

Step 4: Start the Servers

# Start both servers concurrently
npm run dev

# Or start them individually:
npm run dev:auth-server  # Auth server on http://localhost:3001
npm run dev:mcp-server   # MCP server on http://localhost:3232

Configuration

Each server has its own .env file:

Auth Server (auth-server/.env):

AUTH_SERVER_URL=http://localhost:3001  # Auth server URL
AUTH_SERVER_PORT=3001                  # Auth server port
BASE_URI=http://localhost:3232         # MCP server URL (for redirects)
REDIS_URL=redis://localhost:6379       # Redis connection

MCP Server (mcp-server/.env):

BASE_URI=http://localhost:3232         # MCP server URL
PORT=3232                              # MCP server port
AUTH_SERVER_URL=http://localhost:3001  # External auth server URL
REDIS_URL=redis://localhost:6379       # Redis connection

Architecture

Per the MCP Authorization specification, this implementation demonstrates a production-ready pattern with separate authorization and resource servers.

System Architecture

graph TD
    Client["MCP Client<br/>(Inspector)"]
    MCP["MCP Server<br/>(port 3232)<br/>Resource Server"]
    Auth["Auth Server<br/>(port 3001)<br/>OAuth Server"]

    Client <-->|"1. Discover metadata"| MCP
    Client <-->|"2. OAuth flow<br/>(register, authorize, token)"| Auth
    Client <-->|"3. Use tokens for MCP resources"| MCP
    MCP <-->|"Token validation<br/>(introspect)"| Auth

This architecture pattern:

• Separates concerns: Auth server handles OAuth, MCP server handles protocol
• Enables integration: Can replace auth server with Auth0, Okta, etc.
• Scales independently: Auth and MCP servers can scale based on their load
• Follows standards: Uses OAuth 2.0 and token introspection (RFC 7662)

For alternative patterns like embedded OAuth, see docs/oauth-architecture-patterns.md.

OAuth Flow

The implementation uses OAuth 2.1 with PKCE. For detailed flow analysis including data storage, TTLs, and implementation details, see docs/oauth-flow.md.

Understanding the Mock Identity Provider

The /mock-upstream-idp endpoints simulate what a real identity provider (Google, GitHub, corporate SSO) would do. In production, users would be redirected to their actual identity provider for login. This mock implementation helps you test the complete flow locally without external dependencies.

Project Structure

├── auth-server/                 # OAuth authorization server
│   ├── src/
│   │   ├── index.ts             # Auth server entry point
│   │   ├── auth/
│   │   │   ├── provider.ts      # FeatureReferenceAuthProvider
│   │   │   └── auth-core.ts     # Token generation, PKCE
│   │   ├── services/            # Auth services, redis-auth
│   │   ├── handlers/            # Mock upstream auth
│   │   └── utils/logger.ts      # Structured logging
│   ├── package.json
│   ├── tsconfig.json
│   └── .env
│
├── mcp-server/                  # MCP resource server
│   ├── src/
│   │   ├── index.ts             # MCP server entry point
│   │   ├── auth/
│   │   │   ├── external-verifier.ts  # Token introspection
│   │   │   └── auth-core.ts
│   │   ├── services/            # MCP server, redisTransport
│   │   ├── handlers/            # SHTTP, SSE handlers
│   │   └── utils/logger.ts
│   ├── package.json
│   ├── tsconfig.json
│   └── .env
│
├── scripts/                     # Testing and deployment
│   └── test-e2e.sh              # End-to-end OAuth + MCP verification
├── docs/
│   ├── customization-guide.md   # How to adapt this for your use case
│   ├── endpoints.md             # API endpoint reference
│   ├── oauth-flow.md            # OAuth flow documentation
│   ├── oauth-architecture-patterns.md  # OAuth integration guidance
│   └── session-ownership.md     # Session management details
├── examples/                    # Example code and usage patterns
│   ├── client.js                # Node.js client example
│   └── curl-examples.sh         # Shell script with curl examples
├── package.json                 # Root workspace configuration
└── docker-compose.yml           # Redis service

Development

# Start servers
npm run dev                 # Both servers concurrently
npm run dev:auth-server     # Auth server only
npm run dev:mcp-server      # MCP server only

Build & Production

npm run build               # Build all workspaces
npm run start               # Run both servers
npm run start:auth-server   # Run auth server only
npm run start:mcp-server    # Run MCP server only

Testing & Quality

npm test                    # All unit tests
npm run lint                # Lint all code
npm run typecheck           # Typecheck all code
npm run test:e2e            # End-to-end test

Testing with MCP Inspector

The MCP Inspector is a web-based tool for testing MCP servers.

Prerequisites

1. Ensure Docker/OrbStack is running
2. Ensure Redis is running: docker compose ps

Test the Server

# 1. Start both servers (Redis must already be running)
npm run dev

# 2. Launch MCP Inspector in a new terminal
npx -y @modelcontextprotocol/inspector

# 3. Connect to: http://localhost:3232/mcp
# 4. Auth flow will redirect to :3001 for authentication
# 5. Complete OAuth flow in the Auth tab
# 6. Test MCP features (tools, resources, prompts, etc.)

Automated End-to-End Testing

The E2E script in scripts/test-e2e.sh verifies the complete OAuth flow and all MCP features:

npm run test:e2e

The script:

• Automatically manages server lifecycle
• Tests OAuth 2.0 + PKCE flow
• Verifies all MCP features (tools, resources, prompts)
• Validates token introspection between servers
• Tests session management and ownership

Common Issues & Solutions

"Token validation failed"

• Cause: Token expired or servers not communicating
• Solution:
  • Ensure both servers are running (npm run dev)
  • Check that Redis is running (docker compose ps)
  • Verify the token hasn't expired (tokens last 7 days)

"Cannot connect to MCP server" or "Connection Error - Check if your MCP server is running"

• Cause: Incorrect URL format or servers not running
• Solution:
  • Use the full URL with http:// prefix: http://localhost:3232/mcp
  • Ensure both auth and MCP servers are running (npm run dev)

"Cannot connect to Docker daemon"

• Cause: Docker/OrbStack not running
• Solution:
  • macOS with OrbStack: orbctl start (verify with orbctl status)
  • Windows/Linux/macOS with Docker Desktop: Start Docker Desktop application

"Redis connection refused"

• Cause: Redis container not running
• Solution:
  • Check Redis is running: docker compose ps
  • If not running: docker compose up -d
  • Ensure Docker/OrbStack is started first

"Port already in use"

• Cause: Another process using port 3001 or 3232
• Solution:
  • Check for existing processes: lsof -i :3232 or lsof -i :3001
  • Kill existing processes or change PORT in .env files

Understanding the Mock IDP

• The mock IDP simulates user login for testing
• In production, this would be replaced by:
  • Your company's SSO system (LDAP, Active Directory)
  • Auth0/Okta login page
  • Google/GitHub OAuth
• The mock IDP creates random user IDs for testing multi-user scenarios

"Authentication service unavailable" (HTTP 503)

• Cause: Auth server is not running or not reachable
• What happens: MCP server runs in degraded mode
  • Splash page accessible with warning banner
  • Health endpoint shows degraded status: curl http://localhost:3232/health
  • Protected MCP endpoints return 503 with helpful error message
• Solution:
  • Start the auth server: npm run dev (starts both servers)
  • Or start manually: cd auth-server && npm run dev
  • Restart the MCP server to retry connection

"Authentication flow fails"

• Cause: Misconfiguration or servers not communicating
• Solution:
  • Check server logs for error messages
  • Ensure Redis is running: docker compose ps
  • Verify .env configuration in both server directories
  • Check that both servers are running

Technical Details

Scalability Architecture

The server is designed for horizontal scaling using Redis as the backbone:

Session State Management

• Redis Storage: All session state stored in Redis
• 5-minute TTL: Automatic session cleanup
• Session Ownership: User isolation via Redis keys
• Stateless Servers: Any instance can handle any request

Message Routing

• Pub/Sub Channels: Redis channels for message distribution
• Message Buffering: Reliable delivery for disconnected clients
• Connection State: Tracked via pub/sub subscription counts
• Automatic Cleanup: No explicit cleanup required

Redis Key Structure

MCP Session Keys

session:{sessionId}:owner                    # Session ownership
mcp:shttp:toserver:{sessionId}              # Client→Server messages
mcp:shttp:toclient:{sessionId}:{requestId}  # Server→Client responses
mcp:control:{sessionId}                     # Control messages

OAuth/Auth Keys

auth:client:{clientId}                      # OAuth client registrations
auth:pending:{authCode}                     # Pending authorizations
auth:installation:{accessToken}             # Active MCP installations
auth:exch:{authCode}                        # Token exchanges
auth:refresh:{refreshToken}                 # Refresh tokens

Note: The auth: prefix ensures complete namespace isolation between auth and MCP functions.

Transport Methods

Streamable HTTP (Recommended)

Modern transport supporting bidirectional communication over HTTP:

• Single endpoint for all operations
• Session management via headers
• Efficient message buffering
• Automatic reconnection support

Server-Sent Events (Legacy)

Backwards-compatible transport using SSE:

• Separate endpoints for SSE streams and messages
• Session management via URL parameters
• Redis-backed message routing
• Real-time event delivery

API Reference

For a complete listing of all endpoints provided by each server, including OAuth authorization endpoints, MCP resource endpoints, and demo identity provider endpoints, see docs/endpoints.md.

Security

Implemented Security Measures

• Authentication: OAuth 2.0 with bearer tokens
• Token Validation: Introspection via RFC 7662
• Authorization: User-based session ownership
• Session Isolation: Users can only access their own sessions
• Security Headers:
  • Content Security Policy (CSP)
  • Strict Transport Security (HSTS)
  • X-Frame-Options
  • X-Content-Type-Options
• Input Validation: Zod schemas for all inputs
• Error Handling: Sanitized error responses

Security Best Practices

1. Always use HTTPS in production
2. Configure proper CORS origins
3. Use strong client secrets
4. Enable all security headers
5. Monitor session lifetimes
6. Implement rate limiting
7. Use structured logging

Monitoring & Debugging

Logging

Structured JSON logging with sanitized outputs:

• HTTP request/response logging
• Authentication events
• Session lifecycle events
• Redis operations
• Error tracking

Redis Monitoring

# Monitor session ownership
redis-cli KEYS "session:*:owner"

# Watch real-time operations
redis-cli MONITOR | grep "session:"

# Check active sessions
redis-cli PUBSUB CHANNELS "mcp:shttp:toserver:*"

# Debug specific session
redis-cli GET "session:{sessionId}:owner"

Debug Tools

• MCP Inspector for interactive debugging
• Comprehensive test suite
• Hot-reload development mode
• Source maps for debugging
• Redis monitoring commands

Contributing

We welcome contributions! Please see our Contributing Guidelines for details.

Development Workflow

1. Fork the repository
2. Create a feature branch
3. Implement your changes
4. Add tests for new functionality
5. Ensure all tests pass
6. Run linting and fix issues
7. Submit a pull request

Code Style

• TypeScript with strict mode
• ESLint configuration included
• Prettier formatting recommended
• Comprehensive type definitions

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

Built by the Model Context Protocol team as a reference implementation for the MCP ecosystem.

References

MCP Documentation

• Model Context Protocol Documentation
• MCP Authorization Specification
• MCP Specification
• MCP Concepts
  • Tools
  • Resources
  • Prompts
  • Sampling
  • Transports
• TypeScript SDK

OAuth 2.0 / 2.1 Resources

• RFC 6749: OAuth 2.0 Framework
• RFC 7662: Token Introspection
• OAuth 2.1 Draft - Modern security best practices
• OAuth.net: End User Authentication
• The Resource Server - OAuth 2.0 Simplified

Architecture Patterns

This implementation demonstrates patterns discussed in:

• Stack Overflow: Separating Resource and Authorization Servers
• OAuth 2.0 Overview - Curity
• Microsoft identity platform documentation on OAuth 2.0 flows