NitroStack Calculator MCP Server
# NitroStack Starter Template
Minimal template for learning NitroStack fundamentals with a calculator-focused
MCP server and basic widgets.
## What This Template Includes
- `calculator` module with tools, resources, and prompts
- TypeScript + Zod validation setup
- Widget-ready project structure
- Production-friendly npm scripts
## Quick Start
```bash
npx @nitrostack/cli init my-server --template typescript-starter
cd my-server
npm run dev
```
## Common Commands
```bash
npm run dev
npm run build
npm start
```
## NitroStudio
NitroStudio is the recommended way to test and debug this template during
development.
- Download: <https://nitrostack.ai/studio>
- Studio: <https://nitrostack.ai/studio>
## Links
- Docs: <https://docs.nitrostack.ai>
- Templates docs: <https://docs.nitrostack.ai/templates/01-starter-template>
- Main repository: <https://github.com/nitrocloudofficial/nitrostack>
## Community
- Discord: <https://discord.gg/uVWey6UhuD>
- X: <https://x.com/nitrostackai>
- YouTube: <https://www.youtube.com/@nitrostackai>
- LinkedIn: <https://linkedin.com/company/nitrostack-ai/>
- GitHub: <https://github.com/nitrostackai>
TDQS
Scored across 10 tools
Each tool has a clear, distinct purpose: calculation, temperature conversion, fetching notifications from specific platforms (Slack, Jira, Calendar, GitHub, Gmail), building user context, prioritizing notifications, and listing Gmail accounts. There is no ambiguity between tools, as the platform or action is explicitly stated in the name/description.
Tool names follow mixed conventions: most use camelCase with a verb prefix (e.g., fetchSlackNotifications, buildUserContext), but one uses snake_case (convert_temperature) and another is a bare verb (calculate). Verbs also vary (calculate, fetch, build, prioritize, convert, list), so no consistent verb_noun pattern exists.
At 10 tools, the count is within the typical 3-15 range and not excessive. However, the server's stated 'Calculator' purpose is served by only two tools (calculate, convert_temperature), while the majority focus on notification aggregation, so the count feels somewhat misaligned with the server name but is still reasonable for the actual feature set.
The notification aggregation workflow is fairly complete: fetching from five platforms, building user context, and prioritizing. However, the calculator functionality is minimal (basic arithmetic and temperature only), missing many expected operations like unit conversions or scientific functions. Additionally, there is no 'mark as read' or 'send' action for notifications, so the domain has notable gaps.