mcp -remote-setup-with-jwt-auth

This MCP server exposes several AI tools over a secure Server-Sent Events (SSE) channel, protected by JWT Bearer authentication. Clients first obtain a JWT by calling the token endpoint, then connect to the SSE stream at /sse using the Authorization header with Bearer <token>. Once connected, you can dynamically interact with registered tools such as test, echo, get-time, and random-number through the MCP Inspector or any compatible client. The server supports session management for /message interactions, allowing you to send messages to the active session and receive structured tool results in real time over SSE. In short, you get a JWT-protected gateway that exposes a small suite of utility tools suitable for remote tool orchestration and testing, with lifecycle events logged for observability.

Prerequisites:

• Node.js (LTS version) and npm installed on your system
• Git installed

1. Clone the repository

git clone https://github.com/anisirji/mcp-server-remote-setup-with-jwt-auth.git
cd mcp-server-remote-setup-with-jwt-auth

2. Install dependencies

npm install

3. Create a .env file with a JWT secret

echo "JWT_SECRET=your-secret-key" > .env

4. Start the server (development mode)

npm run dev

5. Server will run on port 3001 by default, with the SSE endpoint at http://localhost:3001/sse and the auth token endpoint at http://localhost:3001/auth/token?username=<user>&scope=mcp:access

Tips and caveats:

• Ensure JWT_SECRET in .env is kept secure and not checked into version control.
• The server exposes tools like test, echo, get-time, and random-number. The Inspector can list and invoke these tools once connected.
• If you change the port or host, update the client configuration accordingly (SSE URL and token endpoint).
• Token retrieval uses the /auth/token endpoint; include username and scope=mcp:access in the query parameters.
• The environment variable JWT_SECRET is required for token creation and validation.
• For production deployment, consider TLS termination and configuring a reverse proxy in front of the Node server.