Skip to main content
Glama

Summary MCP

by philipbloch

Summary MCP

AI-powered daily and weekly productivity summaries from Slack, Calendar, and Gmail

An MCP (Model Context Protocol) server that provides comprehensive productivity summaries by analyzing your Slack messages, Calendar events, and Gmail activity.

🌟 Features

  • šŸ“… Daily Summaries: Concise end-of-day wrap-ups with tomorrow's preview

  • šŸ“Š Weekly Summaries: Comprehensive 7-day productivity analysis

  • ⚔ Quick Stats: Fast metrics without full summary generation

  • šŸ“ˆ Period Comparison: Compare productivity across different weeks

  • šŸ“ File Management: List and retrieve past summaries

  • šŸ¤– Automated Generation: Scheduled daily (Mon-Fri 8:30 AM) and weekly (Mon 9:00 AM) summaries

  • 🚫 Smart Filtering: Automatically excludes personal conversations (sports, politics, entertainment)

šŸš€ Quick Start

Installation

  1. Clone and setup:

cd ~/shopify-projects git clone <repo-url> summary-mcp cd summary-mcp npm install
  1. Configure Cursor MCP: Add to ~/.cursor/mcp.json:

{ "mcpServers": { "summary-mcp": { "type": "stdio", "command": "node", "args": ["/Users/philipbloch/shopify-projects/summary-mcp/src/index.js"], "env": {} } } }
  1. Install Automation (optional):

./scripts/install-automation.sh

This sets up:

  • Daily summaries: Monday-Friday at 8:30 AM PT

  • Weekly summaries: Mondays at 9:00 AM PT

šŸ“– Available Tools

1. generate_daily_summary

Generate a concise daily productivity summary.

Parameters:

  • date (optional): Date in YYYY-MM-DD format (default: today)

  • output_format: html, markdown, both, or json

  • save_to_file: Whether to save to summaries folder (default: true)

  • include_sections: Array of sections to include

Example:

Generate my daily summary and save to summaries folder

2. generate_weekly_summary

Generate a comprehensive weekly productivity summary.

Parameters:

  • days_back (optional): Number of days to analyze (default: 7)

  • start_date / end_date (optional): Custom date range

  • output_format: html, markdown, both, or json

  • save_to_file: Whether to save to summaries folder (default: true)

Example:

Generate my weekly summary for the last 7 days

3. get_quick_stats

Get quick productivity metrics without generating a full summary.

Parameters:

  • days_back (optional): Number of days to analyze (default: 7)

  • start_date / end_date (optional): Custom date range

Example:

Show me quick stats for the past week

4. list_summaries

List previously generated summaries.

Parameters:

  • limit: Max results (default: 10)

  • sort: newest or oldest

  • format: Filter by html, markdown, or all

5. get_summary

Retrieve a specific summary by filename or date range.

Parameters:

  • filename: Specific summary file

  • start_date / end_date: Find by date range

  • format: Return html, markdown, or both

6. compare_periods

Compare productivity between two time periods.

Parameters:

  • period1: { start_date, end_date }

  • period2: { start_date, end_date }

  • metrics: Array of metrics to compare

šŸ“ Project Structure

summary-mcp/ ā”œā”€ā”€ src/ │ ā”œā”€ā”€ index.js # MCP server entry point │ ā”œā”€ā”€ config.js # Configuration │ ā”œā”€ā”€ tools/ │ │ ā”œā”€ā”€ index.js # Tool definitions │ │ ā”œā”€ā”€ handler.js # Tool routing │ │ ā”œā”€ā”€ generate-daily-summary.js │ │ ā”œā”€ā”€ generate-summary.js │ │ ā”œā”€ā”€ list-summaries.js │ │ ā”œā”€ā”€ get-summary.js │ │ ā”œā”€ā”€ quick-stats.js │ │ └── compare-periods.js │ ā”œā”€ā”€ analyzers/ │ │ ā”œā”€ā”€ slack-analyzer.js │ │ ā”œā”€ā”€ calendar-analyzer.js │ │ └── gmail-analyzer.js │ └── utils/ │ ā”œā”€ā”€ date-utils.js │ └── file-utils.js ā”œā”€ā”€ scripts/ │ ā”œā”€ā”€ generate-daily-summary.sh │ ā”œā”€ā”€ generate-weekly-summary.sh │ ā”œā”€ā”€ install-automation.sh │ └── uninstall-automation.sh ā”œā”€ā”€ summaries/ # Generated summaries ā”œā”€ā”€ logs/ # Automation logs ā”œā”€ā”€ com.philipbloch.dailysummary.plist ā”œā”€ā”€ com.philipbloch.weeklysummary.plist └── package.json

šŸ¤– Automation

Schedules

  • Daily Summary: Monday-Friday at 8:30 AM PT

  • Weekly Summary: Mondays at 9:00 AM PT

Managing Automation

Install:

./scripts/install-automation.sh

Uninstall:

./scripts/uninstall-automation.sh

Check Status:

launchctl list | grep philipbloch

View Logs:

# Daily summary logs tail -f logs/daily-summary-*.log # Weekly summary logs tail -f logs/weekly-summary-*.log # LaunchD logs tail -f logs/launchd-daily.out.log tail -f logs/launchd-weekly.out.log

Manual Trigger

Daily Summary:

./scripts/generate-daily-summary.sh

Weekly Summary:

./scripts/generate-weekly-summary.sh

šŸ› ļø Development

Running the Server

# Start the server npm start # Development mode with auto-reload npm run dev

Testing

npm test

Debug Mode

Set DEBUG=true in your environment to enable detailed logging:

{ "mcpServers": { "summary-mcp": { "type": "stdio", "command": "node", "args": ["/Users/philipbloch/shopify-projects/summary-mcp/src/index.js"], "env": { "DEBUG": "true" } } } }

šŸ“Š Data Sources

The MCP server integrates with:

  1. Slack MCP: Messages, threads, reactions

  2. Google Calendar: Events, attendees, meeting duration

  3. Gmail: Emails, threads, important contacts

🚫 Content Filtering

By default, Summary MCP filters out personal conversations about sports, politics, and entertainment to keep your summaries focused on work.

  • Enabled by default - Only work-related content in summaries

  • Easily toggle - Set CONTENT_FILTERING_ENABLED=false in .env to disable

  • Customizable - Add your own keywords and topics to filter

See FILTERING.md for complete documentation.

šŸŽØ Output Formats

Format Generation Rules

Daily & Weekly Summaries: Generate both .html and .md by default

  • Can optionally generate JSON for programmatic access

  • Default: output_format: 'both'

Period Comparisons: Generate both .html and .md only (no JSON)

  • Optimized for human-readable trend analysis

  • Default: output_format: 'both'

HTML

Professional, Shopify-branded styling with:

  • Syntax highlighting

  • Interactive sections

  • Visual metrics

  • Print-friendly layout

  • Perfect for sharing and presentations

Markdown

Clean, portable text format:

  • Easy to edit

  • Version control friendly

  • Great for notes and documentation

  • Plain text searchable

JSON (Daily/Weekly only)

Structured data for:

  • Programmatic access

  • Custom processing

  • Integration with other tools

  • Not available for comparisons

šŸ”’ Privacy

All data processing happens locally. The MCP server:

  • āœ… Reads data from your connected services

  • āœ… Processes summaries locally

  • āœ… Saves to your local filesystem

  • āŒ Never sends data to external services

  • āŒ No cloud processing or storage

šŸ› Troubleshooting

Automation not running?

  1. Check if jobs are loaded:

launchctl list | grep philipbloch
  1. Check logs:

tail -f logs/launchd-daily.err.log tail -f logs/launchd-weekly.err.log
  1. Verify Cursor is running (required for automation)

Summaries not saving?

Ensure the summaries directory exists:

mkdir -p ~/shopify-projects/summary-mcp/summaries

MCP server not responding?

  1. Restart Cursor

  2. Check MCP config in ~/.cursor/mcp.json

  3. Verify Node.js is installed: node --version

šŸ“ License

MIT

šŸ‘¤ Author

Philip Bloch philip.bloch@shopify.com


Need Help? Check the AUTOMATION.md for detailed automation setup and troubleshooting.

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/philipbloch/summary-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server