modelcontextprotocol/example-remote-server
Watch
1
0
Fork
You've already forked example-remote-server
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Improve client.js and curl-examples.sh usability

Browse source 
Fix PKCE implementation, SSE parsing, error handling, and usage clarity.
Add --help flag and improve output messaging for both examples.
This commit is contained in:
Basil Hosmer 2025-10-07 14:36:41 -04:00
commit 7b7aa513f5
No known key found for this signature in database
1 changed files with 328 additions and 272 deletions
Download patch file Download diff file Expand all files Collapse all files

29
examples/README.md
View file

@ -24,21 +24,28 @@ Shell script demonstrating API interactions using curl.
- Resource listing and reading
- Prompt operations
**Usage:**
**Three-step workflow:**
```bash
# Make executable
chmod +x curl-examples.sh
# Register client (step 1)
# Step 1: Setup - Register OAuth client and get instructions
./curl-examples.sh
# After getting token (via MCP Inspector)
# Step 2: Create session - Get an access token (via Inspector or client.js), then:
./curl-examples.sh YOUR_ACCESS_TOKEN
# → Initializes MCP session and displays session ID
# With session ID
# Step 3: Run examples - Use both access token and session ID:
./curl-examples.sh YOUR_ACCESS_TOKEN YOUR_SESSION_ID
# → Demonstrates all MCP features (tools, resources, prompts)
```
**Quick reference:**
- Run `./curl-examples.sh --help` for detailed usage
- Get access token from MCP Inspector or `node client.js`
- Each step explains what to do next
### client.js
Node.js client showing programmatic interaction with the MCP server.
@ -59,6 +66,20 @@ chmod +x client.js
./client.js
```
**Note:** When you complete the OAuth flow in your browser, you'll be redirected to `http://localhost:8080/callback` which will show "site can't be reached". This is expected! Simply copy the authorization code from the URL in your browser's address bar (the long string after `code=`). The script will exchange this for an access token and display it for use with other tools.
## Understanding OAuth Tokens
**Authorization Code** vs **Access Token**:
- **Authorization Code**: The temporary code you get from the browser redirect (e.g., `302a80e8...`)
- One-time use only
- Must be exchanged for an access token
- Expires quickly (usually within minutes)
- **Access Token**: The actual bearer token for API authentication (e.g., `mcp_at_...`)
- Used in the `Authorization: Bearer` header
- Valid for 7 days
- What you need for `curl-examples.sh`
## Getting an Access Token
### Option 1: MCP Inspector (Easiest)