nitro

Nitro MCP Server is a streaming HTTP MCP server built on the Nitro framework. It exposes a set of tools under the /tools path and demonstrates authentication via pluggable providers (Auth0 and Microsoft Entra ID). The server validates input and output schemas with Zod, and includes example tools like echo (which returns the input) and getPostsByUser (which fetches posts for a given user). It also showcases resource handling with posts and users resources, enabling clients to list and fetch resources as part of MCP interactions. To get started, run the server locally and use the MCP inspector to connect, explore available tools, and invoke them. The inspector URL is typically http://localhost:6274/?MCP_PROXY_AUTH_TOKEN=<token>, and you can point it at your server (for example http://localhost:3000/mcp) to test tool invocations and resource access.

Prerequisites:

• Node.js v20 or higher
• pnpm package manager

Installation steps:

1. Clone the repository: git clone https://github.com/yourusername/nitro-mcp-server.git cd nitro-mcp-server

2. Install dependencies: pnpm install

3. Create and configure environment variables:

   • Copy example env file to .env: cp env.example .env
   • Open .env and adjust as needed (host, port, and auth provider settings).

4. Run the server locally: pnpm dev

5. (Optional) Run the MCP inspector in another terminal: pnpm inspect

6. Build for production (produces a build in the .output directory): pnpm build

Tips and notes:

• The server uses a pluggable OAuth provider setup (Auth0 and Entra/Microsoft Entra ID). Configure providers in the environment file or in the server config under mcpServer.auth.providers.
• See lib/auth/ for implementation details and advanced options.
• Ensure you set appropriate rate limiting if exposing the registration endpoint due to DCR limitations of external IdPs.
• The tools are located at /tools and include echo and getPostsByUser; resources include posts and users to demonstrate resource handling.
• The inspector URL can be used to test and connect to your MCP server; ensure the MCP_PROXY_AUTH_TOKEN is provided if required by your environment.