MCP Authentication Samples

🚀 MCP Joke Server with Authentication

This is an example of a Model Context Protocol (MCP) server implemented using FastAPI, providing programming joke services with token-based authentication.

🚀 Quick Start

📦 Installation

1. Open this folder in VS Code.
2. When prompted, click "Reopen in Container" to use the devcontainer configuration.
3. The container will automatically install all dependencies from requirements.txt.

💻 Usage Examples

Basic Usage

To start the server, run the following command:

python server.py

The server will start at http://localhost:8000.

✨ Features

This MCP server offers a simple joke-telling capability. Each time it is called, it cycles through a collection of programming-related jokes. The server's features include:

1. Implements a single MCP tool tell_joke.
2. Returns a different programming joke each time it is called.
3. Requires authentication to access the SSE endpoint.

🔧 Technical Details

Authentication

The server implements a simple token-based authentication for the SSE endpoint (/sse). To make a request, you need to include a valid Bearer token in the HTTP header.

For this demonstration, use the following token: valid_token

Here is an example curl request:

curl http://localhost:8000/sse \
  -H "Authorization: Bearer valid_token"

Any SSE endpoint request that does not provide a valid token will receive a 401 Unauthorized response.

VS Code Copilot Integration

This server can serve as a custom joke proxy for GitHub Copilot in VS Code. To use it:

1. Start the MCP server using python server.py.
2. The VS Code settings have already been configured in .vscode/settings.json to use this server.
3. The server will respond to joke requests via the MCP protocol.

Supported Features

• Telling jokes through the MCP tool.
• Token-based authentication for the SSE endpoint.
• An HTTP server based on FastAPI.

📄 License

This is a demonstration implementation. In a production environment, you should:

1. Use appropriate authentication.
2. Store secrets securely.
3. Implement effective token issuance and management.
4. Use HTTPS.
5. Add rate limiting and other security measures.

⚠️ Important Note

This is a demonstration implementation. In a production environment, you should follow proper security practices such as using appropriate authentication, securely storing secrets, implementing effective token issuance and management, using HTTPS, and adding rate limiting and other security measures.

💡 Usage Tip

When using the server, make sure to include the valid Bearer token in the HTTP header for SSE endpoint requests to avoid getting a 401 Unauthorized response.