example-remote-server/examples
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Basil Hosmer c03a9b4e77
Remove embedded OAuth implementation and flatten directory structure
Simplified the repository to have a single OAuth pattern with separate auth and MCP servers at the top level. Preserved embedded OAuth documentation as an alternative pattern.
2025-10-06 21:30:14 -04:00
..
client.js Remove embedded OAuth implementation and flatten directory structure 2025-10-06 21:30:14 -04:00
curl-examples.sh Remove embedded OAuth implementation and flatten directory structure 2025-10-06 21:30:14 -04:00
README.md Remove embedded OAuth implementation and flatten directory structure 2025-10-06 21:30:14 -04:00

MCP Server Examples

This directory contains example code demonstrating how to interact with the MCP server.

Prerequisites

Before running any examples, ensure:

  1. Redis is running: docker compose up -d
  2. Both servers are running: npm run dev
  3. Servers are accessible at:

Available Examples

curl-examples.sh

Shell script demonstrating API interactions using curl.

Features:

  • OAuth client registration
  • MCP session initialization
  • Tool calls (echo, add)
  • Resource listing and reading
  • Prompt operations

Usage:

# Make executable
chmod +x curl-examples.sh

# Register client (step 1)
./curl-examples.sh

# After getting token (via MCP Inspector)
./curl-examples.sh YOUR_ACCESS_TOKEN

# With session ID
./curl-examples.sh YOUR_ACCESS_TOKEN YOUR_SESSION_ID

client.js

Node.js client showing programmatic interaction with the MCP server.

Features:

  • Complete OAuth flow demonstration
  • Automatic client registration
  • MCP session management
  • Tool and resource operations

Usage:

# Run the example
node client.js

# Or make it executable
chmod +x client.js
./client.js

Getting an Access Token

Option 1: MCP Inspector (Easiest)

# Launch inspector
npx -y @modelcontextprotocol/inspector

# Connect to http://localhost:3232/mcp
# Complete OAuth flow in the Auth tab
# Copy the access token from the debug console

Option 2: Manual OAuth Flow

  1. Register a client (see examples)
  2. Navigate to authorization URL
  3. Complete authentication
  4. Exchange authorization code for token
  5. Use token in API calls

Common Patterns

Making MCP Requests

All MCP requests follow this pattern:

{
  "jsonrpc": "2.0",
  "id": "unique-id",
  "method": "category/action",
  "params": { /* method-specific parameters */ }
}

Required Headers

Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json
Mcp-Session-Id: YOUR_SESSION_ID  // After initialization

Session Lifecycle

  1. Initialize: Create a new session
  2. Use: Make requests with session ID
  3. Terminate: Optional cleanup (auto-expires after 5 min)

Troubleshooting

"401 Unauthorized"

  • Token may be expired (7-day TTL)
  • Token may be invalid
  • Get a new token via OAuth flow

"Session not found"

  • Session expired (5-minute TTL)
  • Re-initialize with the same token

"Cannot connect"

  • Ensure servers are running: npm run dev
  • Check Redis is running: docker compose ps
  • Verify URLs are correct

Additional Resources