home / mcp / mcp server playground
A playground MCP server enabling HTTP transport, OAuth proxy authentication, and tool execution for MCP clients.
Configuration
View docs{
"mcpServers": {
"chrisleekr-mcp-server-boilerplate": {
"url": "http://localhost:3000/mcp"
}
}
}You deploy and run an MCP server that enables authenticated, OAuth-enabled access to model context protocols over an HTTP transport. It supports session management, dynamic application registration via an OAuth proxy, and a set of ready-made tools to interact with cloud resources, time, streams, and project metadata. This server is designed to be deployed in development or small-scale environments where you want to experiment with MCP flows and third-party authorization providers while keeping control over how clients register and obtain tokens.
You connect an MCP client to the server over HTTP. The server implements the MCP protocol through a streamable HTTP transport, handles sessions, and can execute a predefined set of tools. For third-party authorization, you route OAuth interactions through a proxy so the server delegates authorization to providers like Auth0, Github, or Google.
To start a client session, you typically target the MCP endpoint to establish a session and then perform tool actions or data requests. The server exposes an MCP endpoint at /mcp for protocol requests and keeps sessions manageable across requests. When you need to terminate a session, you can use the designated session-termination flow at the same endpoint.
Prerequisites: you need Node.js and npm installed on your machine. You may also run desktop or containerized environments for development.
Step 1 — Install dependencies and set up the project locally.
Step 2 — Set up environment variables for local development. Copy the example env file to your working environment and adjust values as needed.
Step 3 — Start the local MCP server in development mode. Use the provided development setup command to prepare the local environment and then run the server.
Key endpoints include health and MCP operation points, OAuth metadata, and client registration helpers.
MCP endpoints you can interact with include the following (HTTP): ping, mcp, and session termination.
OAuth-related endpoints support dynamic registration via a proxy, including authorization, token handling, and callback processing.
Stateful sessions across multiple MCP server instances require storing the initial request and replaying it on subsequent touches to a different instance. A session store like Valkey can be used to persist the initial request’s session identifier and replay behavior, ensuring the transport connects to the same server flow.
If you deploy in a cluster, understand that the transport is not shared by default across instances. The session replay mechanism is introduced to preserve state and continuity across instances.
Security considerations: dynamic application registration via an OAuth proxy provides a scalable approach to client onboarding, but public endpoints must be protected against abuse. Ensure the proxy and the underlying providers are configured securely.
Investigate the ECS service, its tasks, and cloudwatch logs using AWS ECS, Cloudwatch Logs, and Bedrock.
Fetch and list S3 buckets and objects accessible to your credentials.
Return the current system time in multiple formats and timezones.
Echo input with optional transformations and repetition.
Simulate real-time streaming data with live updates to demonstrate MCP streaming.
Search for keywords within the current project directory to aid exploration.