Universal Goal Engine, Local Web Portal & Model Context Protocol (MCP) Server
Journey is a local-first goal tracking and mastery engine with a Next.js web portal and a built-in MCP server. It manages skill trees, mastery roadmaps, and daily task priorities through a single JSON file (~/.journey/data/roadmap.json) accessible by both humans and AI agents in real time.
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Journey Web Portal β
β (http://localhost:6161) β
β β’ Home Overview β’ Execution Dashboard β
β β’ Goal Tree Graph β’ 24 Preset Themes β
ββββββββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββ
β reads & writes
ββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββ
β ~/.journey/data/roadmap.json β
β (User's Local Goal & Mastery Data) β
ββββββββββββββββββββββββββββββ²βββββββββββββββββββββββββββββ
β MCP / Stdin-Stdout
ββββββββββββββββββββββββββββββ΄βββββββββββββββββββββββββββββ
β AI Assistants & MCP Clients β
β (Claude Code, OpenCode, Hermes, Cursor, Windsurf, etc.) β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
- Local-First & Private: Personal data remains stored locally at
~/.journey/data/roadmap.json. Requires no external databases, account creation, or cloud services. - Model Context Protocol (MCP): Native
journey-mcpexecutable exposing JSON-RPC 2.0 tools (get_roadmap,add_goal,update_item_status) for seamless AI integration. - 24 Theme Color Combos: Includes 24 harmonized color theme presets (Dracula, Nord, Gruvbox, Tokyo Night, Monokai, RosΓ© Pine, Synthwave, Catppuccin, Cyberpunk, and Clean Light/Dark) with automatic YIQ text contrast adjustment.
- Algorithmic Execution Engine: Evaluates task priority, career ROI, and dependencies to synthesize daily focus items and surface blocked goals on the Dashboard.
- Interactive Goal Graph: Visual node tree interface allowing direct inline node creation, deletion, status updates, and track filtering.
- Density Scaling: Toggle between Comfortable and Compact layout densities for different display sizes.
Install Journey globally via npm:
npm install -g @ziuus/journeyUpgrading: To update an existing global installation:
npm install -g @ziuus/journey@latest
Start the background web service:
journeyNavigate to http://localhost:6161. Journey automatically creates a starter roadmap file at ~/.journey/data/roadmap.json on initial launch if one does not exist.
| View | Path | Primary Purpose |
|---|---|---|
| Overview | / |
Track-by-track accordion hierarchy, global progress statistics, search filtering. |
| Dashboard | /dashboard |
Algorithmic focus recommendation engine, high-ROI target lists, dependency warning panels. |
| Goal Tree | /tree |
Full-screen interactive DAG node graph view with live node editing tools. |
| Settings | /settings |
Theme selector (24 presets), custom accent override, density mode, default landing view preferences. |
Journey supports any agent using the Model Context Protocol (MCP). Since different AI CLI tools and IDEs use different configuration formats, find your agent below for step-by-step setup instructions:
Run the built-in MCP CLI command:
claude mcp add journey journey-mcpOr with NPX (zero-install):
claude mcp add journey npx -y @ziuus/journey journey-mcpRun in your terminal:
opencode mcp add journey journey-mcpOr add to ~/.config/opencode/mcp.json:
{
"mcpServers": {
"journey": {
"command": "journey-mcp"
}
}
}Run in terminal:
hermes mcp add journey journey-mcpOr add to ~/.hermes/mcp.json:
{
"mcpServers": {
"journey": {
"command": "journey-mcp"
}
}
}Add to your claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"journey": {
"command": "journey-mcp"
}
}
}Open Cursor Settings β Features β MCP or edit .cursor/mcp.json in your project root:
{
"mcpServers": {
"journey": {
"command": "journey-mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"journey": {
"command": "journey-mcp"
}
}
}Open Roo Code Settings β MCP Servers β Add New MCP Server or edit cline_mcp_settings.json:
{
"mcpServers": {
"journey": {
"command": "journey-mcp"
}
}
}Add to ~/.config/zed/settings.json:
{
"context_servers": {
"journey": {
"command": "journey-mcp"
}
}
}Add to ~/.config/goose/config.yaml:
mcpServers:
journey:
command: journey-mcpAdd to ~/.continue/config.json:
{
"mcpServers": [
{
"name": "journey",
"command": "journey-mcp"
}
]
}If you prefer not to install globally, you can use npx in any MCP config:
{
"mcpServers": {
"journey": {
"command": "npx",
"args": ["-y", "@ziuus/journey", "journey-mcp"]
}
}
}When connected, AI agents automatically discover and execute these 3 tools:
| Tool | Input Parameters | Description |
|---|---|---|
get_roadmap |
None | Reads the user's complete roadmap and goal tree from ~/.journey/data/roadmap.json. |
add_goal |
layerId, title, goal |
Inserts a new goal into a specified roadmap layer. |
update_item_status |
type, itemId, status |
Updates target item status (pending or done). |
For agents without native MCP support (e.g. Gemini CLI, ChatGPT Web, custom scripts), simply inform your agent:
"My goal roadmap is stored at
~/.journey/data/roadmap.json. Read this file to track my active goals and progress."
| Environment | Strategy |
|---|---|
| Gemini CLI | Reference GEMINI.md in your workspace context. |
| Claude Code | Include AGENTS.md at your project root. |
| Custom Agents | Read/write directly to ~/.journey/data/roadmap.json. |
| Command | Action |
|---|---|
journey |
Launches background portal process on port 6161 |
journey dev |
Runs development portal in foreground on port 3000 |
journey status |
Queries current background service state |
journey stop |
Terminates background portal service |
journey logs |
Displays real-time portal process logs |
journey-mcp |
Runs stdio Model Context Protocol server |
journey/
βββ src/ # Next.js 16 Web Portal Application
β βββ app/ # Application routes (/ , /dashboard, /tree, /settings)
β βββ components/ # Navigation bar, Footer, and SVG Logo components
β βββ config/ # Theme metadata & default system configurations
β βββ context/ # Global preference & theme context provider
β βββ lib/ # Roadmap normalizers & scoring algorithm
βββ data/
β βββ roadmap.json # Repository starter template (Do NOT write user data here)
βββ scripts/
β βββ journey-cli.js # CLI service manager executable
β βββ mcp-server.js # Model Context Protocol stdio server executable
βββ ~/.journey/data/ # User storage location (roadmap.json)
Data Separation Policy:
- User Roadmap: Saved strictly to
~/.journey/data/roadmap.jsonoutside the source directory.- Starter Template: The repository file
data/roadmap.jsonprovides initial default schema structure for new installations.
MIT Β© ziuus


