nitro-mcp-server
by peterbud·★ 5·Score 39
A lightweight MCP server built with Nitro, featuring HTTP transport, authentication, and example tools/resources.
Overview
The Nitro MCP Server is a TypeScript implementation that demonstrates how to build MCP servers using streamable HTTP transport powered by Nitro. It includes example tools like echo and getPostsByUser, and resources like posts and users, all with Zod schema validation. The server supports authentication through pluggable providers including Auth0 and Microsoft Entra ID, making it suitable for production environments requiring secure access control.
Try asking AI
After installing, here are 5 things you can ask your AI assistant:
When to choose this
Choose this when you need a lightweight MCP server with authentication support and prefer a TypeScript implementation using Nitro.
When NOT to choose this
Avoid if you need a server with extensive built-in tools or if you prefer a different transport protocol than HTTP.
Tools this server exposes
2 tools extracted from the READMEechoEchoes back the input, demonstrating basic tool functionality
getPostsByUserFetches posts by a user using an API, demonstrating output schema validation
Comparable tools
Installation
Installation
- Clone the repository:
git clone https://github.com/peterbud/nitro-mcp-server.git
cd nitro-mcp-server- Install dependencies:
pnpm install- Start the server:
pnpm dev- Run the MCP inspector:
pnpm inspectThen open your browser to the inspector URL like http://localhost:6274/?MCP_PROXY_AUTH_TOKEN=<token> and connect to your server at http://localhost:3000/mcp.
Claude Desktop Configuration
Add this to your Claude Desktop config.json:
{
"mcpServers": {
"nitro": {
"command": "npx",
"args": ["nitro-mcp-server"]
}
}
}FAQ
- What authentication providers are supported?
- The server supports Auth0 and Microsoft Entra ID through pluggable providers that can be configured in the server settings or .env file.
- How do I add custom tools or resources?
- You can add custom tools or resources by implementing them in the appropriate directories (likely in 'tools' or 'resources') following the schema validation patterns established in the codebase.
Compare nitro-mcp-server with
Last updated · Auto-generated from public README + GitHub signals.