Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| productivity_analysis | Creates a comprehensive productivity analysis prompt |
| learning_analysis | Creates a deep learning pattern analysis prompt |
| research_topic_extraction | Extract and summarize research topics from browsing history |
| generate_insights_report | Generate a personalized insights report based on browsing patterns |
| export_visualization | Export your browsing data as interactive visualizations |
| compare_time_periods | Compare your browsing habits across different time periods |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_browser_status | Step 1: Check which browsers are available and which are locked. This is the first step in the workflow - run this to see if you need to close any browsers. Returns a dictionary with:
- status: "ready", "browser_locked", or "error"
- error_message: Clear error message if there's an issue
- user_action_required: True if user needs to close browsers
- recommended_action: Specific instructions for the user
- available_browsers: List of detected browsers
- active_browsers: List of browsers that are currently running
IMPORTANT: If status is "browser_locked", you MUST tell the user to close the specified browser(s).
|
| get_browser_history | Step 2: Get raw browser history data without analysis. This is the fastest way to retrieve browser history and should be used before any analysis. Args:
time_period_in_days: Number of days of history to retrieve (default: 7)
browser_type: Browser type ('firefox', 'chrome', 'safari', or None for auto-detect)
all_browsers: If True, get history from all available browsers (default: True)
Returns:
Either a list of history entries or a dictionary with partial results and browser status |
| analyze_browser_history | Step 3: Analyze browser history with different levels of detail. This is the main analysis tool that consolidates all analysis options.
Args:
time_period_in_days: Number of days of history to analyze (default: 7)
analysis_type: Type of analysis to perform:
- "quick_summary": Basic stats only (fastest)
- "basic": Domain analysis and categorization (not yet implemented)
- "comprehensive": Full analysis with sessions and insights (default)
fast_mode: If True, limits analysis for faster processing (default: True) |
| search_browser_history | Search browser history for specific queries. Use this after getting history data. Args:
query: Search term to look for in URLs and titles |
| suggest_categories | Get uncategorized URLs for custom categorization. Use this after running analysis. |
| diagnose_safari_support | Diagnose Safari support and accessibility. Useful for debugging Safari integration. |
| health_check | Simple health check that returns immediately to test if the MCP server is working. |