GitHub Push Event Scraper avatar
GitHub Push Event Scraper

Pricing

$0.45 / 1,000 events

Go to Store
GitHub Push Event Scraper

GitHub Push Event Scraper

Developed by

Andrew K

Andrew K

Maintained by Community

Extracts GitHub push events with your specified date range. Scrapes commit metadata, including author info (name, email), commit messages, and URLs for users, commits, and repos. Ideal for monitoring repository activity or tracking user contributions.

0.0 (0)

Pricing

$0.45 / 1,000 events

0

Total users

2

Monthly users

2

Last modified

a day ago

You can access the GitHub Push Event Scraper programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=krab/github-push-event-scraper",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with GitHub Push Event Scraper

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=krab/github-push-event-scraper along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=krab/github-push-event-scraper",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.