MCP.Market

Google Events MCP server

online · 100% uptime
by johnisanerd·io.github.johnisanerd/google-events·v1.0.0·2 stars

Google Events listings with dates, venues, and ticket links via a hosted MCP server.

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed Google Events yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Google Events tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 936ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Google Events compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
119 ms
faster than 80% of 30,031 servers
GitHub stars
2
more than 75% of 28,688 servers

Install Google Events in Claude Code, Cursor or VS Code

claude mcp add --transport http google-events https://mcp.apify.com/?tools=johnvc/google-events-api---access-google-events-data
Add to Cursor

What the publisher says

From the Google Events repository's README, as published. We do not edit it. Read it on GitHub

🎭 Google Events API: Event Search in Clean JSON

The most efficient, reliable, and developer-friendly way to use the Google Events API.

Actor page: apify.com/johnvc/google-events-api---access-google-events-data Input schema: apify.com/johnvc/google-events-api---access-google-events-data/input-schema

The Google Events API runs an event search for any query and returns clean, structured JSON. Each page of results comes back with event titles and descriptions, dates and full date/time ranges, venue names with ratings and reviews, multi-line addresses, ticket-provider links (Ticketmaster, Eventbrite, Spotify, and more), map preview images and links, and the filter chips Google offers. It supports location biasing, country and language localization, date and event-type filters, and pagination.

Video Walkthrough

Quick Start

Prerequisites

  • Python 3.11 or higher
  • An Apify account and API key (get a free key here)
  1. Clone the repository
git clone https://github.com/johnisanerd/Apify-Google-Events-API.git
   cd Apify-Google-Events-API
  1. Install dependencies with UV
# Install UV if you do not have it:
   curl -LsSf https://astral.sh/uv/install.sh | sh

   # Install project dependencies:
   uv sync
  1. Configure your API key
cp .env.example .env
   # Edit .env and add your Apify API key
   # Get your free API key at: https://apify.com?fpr=9n7kx3
  1. Run the example
uv run python google-events-api.py

Alternative: set the API key directly

export APIFY_API_TOKEN="your_api_key_here"
uv run python google-events-api.py

Why Use This Google Events API?

Full event detail. Each result includes the title, description, dates, venue (with rating and reviews), address, ticket links from multiple providers, and map links, so you get everything Google Events shows in one structured record.

Aggregated ticket links. Ticket sources like Ticketmaster, Eventbrite, Spotify, AXS, and SeatGeek are collected per event, ready to surface purchase options.

Localized and filterable. Bias by location, localize by country and language (240+ countries, 200+ languages), and filter with Google's own chips: date (today, this week, weekend, month) and event type (virtual).

Predictable, pay-per-use pricing. Billing is per run plus per page processed, with no subscription. You control cost with the page limit.

Easy to automate. Call it from Python in a few lines, or load it as an MCP tool so assistants like Claude and Cursor can find events for you on demand.

Features

Core Capabilities

  • Natural-language event search across concerts, conferences, festivals, sports, theater, and virtual events
  • Location biasing plus country (gl) and language (hl) localization
  • Date and event-type filters via Google's hit chips
  • Multi-page pagination with a configurable page cap

Data Quality

  • Structured events with title, description, dates, address, and primary link
  • Ticket links aggregated from multiple providers
  • Venue details with name, rating, and review count
  • Map previews (image and Google Maps link) per event
  • Per-page metadata and consistent JSON across queries

Usage Examples

Basic search

{
  "q": "concerts in New York",
  "max_pages": 1
}

Localized search

{
  "q": "music festivals",
  "location": "Austin, Texas, United States",
  "gl": "us",
  "hl": "en",
  "max_pages": 2
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Google Events: common questions

Is Google Events MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Google Events safety report
How do I install Google Events?
It runs remotely at mcp.apify.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Google Events need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Google Events maintained?
The last commit was 41 days ago (2026-09-24). The latest release is v1.0.0.
Is Google Events up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Google Events compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 119 ms (faster than 80% of 30,031 servers). Full comparison.