Activity Collector

Collects activity data from GitLab, GitHub, Google Calendar, and Outlook Calendar via MCP
  • javascript

0

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "srdmathur-activity-collector-mcp": {
      "command": "npx",
      "args": [
        "activity-collector-mcp"
      ]
    }
  }
}

You can collect and centralize developer activity data from GitLab, GitHub, Google Calendar, and Outlook Calendar using the Activity Collector MCP Server. It integrates multiple sources, caches data for fast access, and stores OAuth tokens securely in your home directory so you can query activity across projects and calendars from a single place.

How to use

Use an MCP client to connect to the Activity Collector MCP Server and fetch activity data from your connected services. You can configure the server to use GitLab, GitHub, Google Calendar, and Outlook Calendar individually or in combinations, then request activity for specific date ranges or periods.

How to install

Prerequisites you should have installed before running the MCP server:

  • Node.js and npm (Node Package Manager) installed on your machine.

Install or run the MCP server using one of the following methods.

# Run with npx (recommended for quick start)
npx activity-collector-mcp
# Install globally with npm
npm install -g activity-collector-mcp
# Build from source
git clone https://github.com/srdmathur/activity-collector-mcp.git
cd activity-collector-mcp
npm install
npm run build

Configuration

You can configure the MCP server to integrate with different services. The following examples show how to wire the server into Claude Desktop and Claude Code for easy access.

{
  "mcpServers": {
    "activity-collector": {
      "command": "npx",
      "args": ["activity-collector-mcp"]
    }
  }
}

For Claude Code (VS Code), add the following configuration to your mcp.json.

{
  "servers": {
    "activity-collector": {
      "type": "stdio",
      "command": "npx",
      "args": ["activity-collector-mcp"]
    }
  }
}

API Configuration is stored in your home directory as a separate config file to enable connections to the various services.

{
  "gitlab": {
    "url": "https://gitlab.com"
  },
  "google": {
    "clientId": "YOUR_GOOGLE_CLIENT_ID",
    "clientSecret": "YOUR_GOOGLE_CLIENT_SECRET",
    "redirectUri": "http://localhost:3000/oauth/callback"
  },
  "outlook": {
    "clientId": "YOUR_OUTLOOK_CLIENT_ID",
    "clientSecret": "YOUR_OUTLOOK_CLIENT_SECRET",
    "tenantId": "YOUR_TENANT_ID",
    "redirectUri": "http://localhost:3000/oauth/callback"
  }
}

Security

Tokens are stored securely in your home directory with restricted permissions. OAuth tokens are refreshed automatically when they expire. Do not commit the configuration file to version control.

Getting API Credentials

Use the following paths to obtain tokens and credentials for the connected services.

# GitLab Personal Access Token
# Create token with read_api and read_repository scopes in GitLab
# GitHub Personal Access Token
# Generate token with repo and read:user scopes in GitHub
# Google Calendar Credentials
# Create OAuth 2.0 Client ID credentials in Google Cloud Console
# Outlook Calendar Credentials
# Register application in Azure AD and grant Calendars.Read

Notes and tips

This MCP is designed to work smoothly with Timesheet Assistant MCP for timesheet generation and PSI submission, providing a cohesive workflow across calendars and code activity.

Troubleshooting

If you encounter issues with authentication or data fetching, verify that your API credentials are correctly configured, tokens are not expired, and the OAuth redirect URIs are reachable from your local environment.

Available tools

configure_gitlab

Set up GitLab integration by providing a personal access token with read_api and read_repository scopes.

configure_github

Set up GitHub integration by providing a personal access token with repo and read:user scopes.

configure_google_calendar

Start Google Calendar OAuth flow to authorize access to calendar data.

google_calendar_callback

Complete Google Calendar OAuth flow after the user authorizes access.

configure_outlook_calendar

Start Outlook Calendar OAuth flow to authorize access to calendar data.

outlook_calendar_callback

Complete Outlook Calendar OAuth flow after authorization.

fetch_gitlab_activity

Fetch GitLab activity for a specific date or date range.

fetch_github_activity

Fetch GitHub activity for a specific date or date range.

fetch_google_calendar_events

Fetch Google Calendar events for a specific date or range.

fetch_outlook_calendar_events

Fetch Outlook Calendar events for a specific date or range.

check_authentication_status

Check authentication status for all configured services.

clear_cache

Clear cached activity data to force fresh fetches.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational