sage (賢者)

AI Task Management Assistant - MCP Server for Claude Desktop, Claude Code, and Remote clients.

Overview

sage is an intelligent task management assistant that helps you:

• Analyze tasks - Automatically assign priorities (P0-P3), estimate time, and extract stakeholders
• Split complex tasks - Break down large tasks into actionable subtasks
• Smart routing - Route tasks to Apple Reminders (≤7 days) or Notion (8+ days)
• Calendar awareness - Find available time slots based on your schedule

sage is an MCP (Model Context Protocol) server that supports HTTP Transport for both local and remote connections.

Quick Start

For Claude Desktop / Claude Code (Local MCP)

# Claude Code - one command setup
claude mcp add sage -- npx -y @shin1ohno/sage

For Claude Desktop, see Local MCP Setup Guide.

For iOS / iPadOS / Web (Remote MCP)

See Remote MCP Setup Guide.

Documentation

Features

Task Analysis

Analyze text input (emails, meeting notes, etc.) and get structured task information:

User: analyze_tasks with input: "田中さんからの依頼: 明日までに報告書を提出。来週の会議資料も準備してください。"

sage:
  Task 1: 報告書を提出
  - Priority: P0 (due tomorrow)
  - Estimated: 50 minutes
  - Stakeholder: 田中さん

  Task 2: 会議資料を準備
  - Priority: P2 (due next week)
  - Estimated: 90 minutes

OAuth Token Persistence

sage now includes persistent OAuth token storage for Remote MCP server:

• Automatic token persistence: OAuth refresh tokens, client registrations, and user sessions are automatically saved and restored across server restarts
• Encrypted storage: All tokens are encrypted using AES-256-GCM before being stored on disk
• Secure key management: Encryption keys can be provided via SAGE_ENCRYPTION_KEY environment variable or auto-generated at ~/.sage/oauth_encryption_key
• No re-authentication needed: Users no longer need to re-authenticate after server restarts

Storage Location: All OAuth data is stored in ~/.sage/ directory:

• oauth_refresh_tokens.enc - Encrypted refresh tokens
• oauth_clients.enc - Encrypted client registrations
• oauth_sessions.enc - Encrypted user sessions
• oauth_encryption_key - Encryption key (auto-generated if not provided)

Setup: To use a custom encryption key (recommended for production), set the environment variable:

export SAGE_ENCRYPTION_KEY="your-secure-random-key-at-least-32-characters"
npx @shin1ohno/sage --remote

If no key is provided, sage will automatically generate one and store it securely with 600 file permissions.

Google Calendar Integration

sage now supports multiple calendar sources:

• macOS: Use EventKit, Google Calendar, or both simultaneously
• Linux/Windows: Use Google Calendar as your primary calendar source
• Automatic fallback: If one source fails, sage automatically uses the other
• Event deduplication: Intelligent merging prevents duplicate events

Supported Event Types: sage supports all Google Calendar event types:

• default - Standard meetings and events
• outOfOffice - Vacation and out-of-office blocks with auto-decline
• focusTime - Focus time blocks with Google Chat status integration
• workingLocation - Remote work, office, or custom location (all-day)
• birthday - Birthday and anniversary events (all-day, yearly recurring)
• fromGmail - Auto-generated events from Gmail (read-only, cannot be created)

Setup: See Configuration Guide for Google OAuth setup instructions.

Remote Server Google OAuth Setup

When running sage as a remote MCP server (e.g., on a VPS or cloud instance), you can use Google Calendar by setting up a Web Application OAuth client:

1. Create OAuth Client in Google Cloud Console

1. Go to Google Cloud Console
2. Navigate to "APIs & Services" → "Credentials" → "Create Credentials" → "OAuth client ID"
3. Application type: Web application
4. Authorized redirect URIs:
   • Local development: http://localhost:3000/oauth/callback
   • Production server: https://mcp.example.com/oauth/google/callback

2. Configure Environment Variables

export GOOGLE_CLIENT_ID="your-client-id.apps.googleusercontent.com"
export GOOGLE_CLIENT_SECRET="your-client-secret"
export GOOGLE_REDIRECT_URI="https://mcp.example.com/oauth/google/callback"

3. Authenticate

From Claude, run the authenticate_google tool:

1. The tool returns an authorization URL
2. Open the URL in your browser
3. Complete Google authentication
4. The server receives the callback automatically
5. A success page is displayed - close the window and return to Claude

Troubleshooting

Smart Reminder Routing

Tasks are automatically routed to the appropriate system:

Platform Support

Apple Reminders requires macOS (AppleScript). Calendar support is available on all platforms via Google Calendar, with optional EventKit integration on macOS.

Tools

Setup & Configuration

Task Management

Requirements

• Node.js >= 18.0.0
• Notion MCP server (任意、Notion 統合用)

Platform-Specific Requirements

• macOS: Full feature support (Apple Reminders, EventKit, Google Calendar)
• Linux/Windows: Calendar features via Google Calendar API (Apple Reminders not available)

注意: Apple Reminders 機能を使用する場合は macOS が必要です。Google Calendar のみを使用する場合は、Linux/Windows でも動作します。

Development

# Clone repository
git clone https://github.com/shin1ohno/sage.git
cd sage

# Install dependencies
npm install

# Run in development mode
npm run dev

# Run tests
npm test

# Build
npm run build

License

MIT - see LICENSE for details.