psyrotrack
# PsyroTrack MCP 🚀
**Tagline:** "PsyroTrack MCP - Notion ka Baap, Free for Lifetime"
PsyroTrack MCP is an advanced, privacy-first routine and habit tracking Model Context Protocol (MCP) Server created by **Psyro8-t**.
## How It Works (Privacy & Data Isolation)
Your data belongs exclusively to **YOU**. No cloud, no databases, no shared repositories.
All tracker data is stored entirely on your own local machine inside your OS home directory:
`~/.psyrotrack/data.json`
## Features
- **Default Protocols**: By default, you get Psyro8-t's legendary 10 protocols (Wake up 6am, 3hr code, etc.)
- **Customizable**: Want your own routine? Just tell the AI to set up your custom protocols!
- **Stats & Trackers**: Generate dynamic monthly reports and streak statistics natively inside Claude/Cursor.
## âš¡ Super Easy Installation (No Download Required!)
You don't need to download any code. Just use the `npx` command to run it directly from GitHub!
### For Claude Desktop App (Mac/Windows)
1. Open your Claude desktop config file:
- **Mac**: `~/Library/Application Support/Claude/claude_desktop_config.json`
- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
2. Add the following to your config:
```json
{
"mcpServers": {
"psyrotrack": {
"command": "npx",
"args": ["-y", "github:Psyro8-t/PsyroTrack-MCP"]
}
}
}
TDQS
Scored across 8 tools
Tools are mostly distinct: show_tracker and show_stats both display information but one is progress per month and the other is streaks/completion, which could be slightly confused. The protocol management tools (add/remove/set) and tick/reset are clearly separated.
Most tools follow a verb_noun pattern (show_tracker, show_stats, reset_tracker, add_protocol, remove_protocol, tick_protocol). init_user and set_protocols are also verb_noun, so the pattern is consistent, though init_user is more of a setup action than a resource operation.
8 tools is well-scoped for a personal tracking server: initialization, protocol management, ticking, and stats/reporting. Each tool serves a distinct function without redundancy.
The surface covers the core lifecycle: init, add/remove/replace protocols, tick, reset, and view progress/stats. A minor gap is the lack of an explicit way to view or edit a single protocol's details, but the set is otherwise complete for the domain.