Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
{
"mcpServers": {
"io-github-matiasbattocchia-google-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 35 days ago. 1 stars.
Will it work with my client?
Transport: . Compatibility not confirmed.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Official Notion MCP Server
Search, evaluate, and compare 17,000+ MCP servers — each scored on security, maintenance, and efficiency.
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
MCP Security Weekly
Get CVE alerts and security updates for io.github.matiasbattocchia/google-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A public Model Context Protocol (MCP) server that lets AI assistants access your Google Calendar and Sheets.
Live at: https://g.mcp.openbsp.dev
Most Google MCP servers require you to create your own Google Cloud project, set up OAuth credentials, and run a local server. This is tedious and error-prone.
This project is different. It's a hosted public server with proxy OAuth. You just:
No Google Cloud setup. No local servers. No environment variables. Just connect and go.
Once connected, ask your AI assistant to:
┌──────────────┐ ┌──────────────────┐ ┌──────────────┐
│ AI Client │────▶│ OpenBSP MCP │────▶│ Google APIs │
│ (Claude) │◀────│ Server │◀────│ │
└──────────────┘ └──────────────────┘ └──────────────┘
| Data | Purpose | Protection | |------|---------|------------| | API Key | Authenticate your MCP client | Stored as-is (random 256-bit value) | | OAuth Tokens | Access Google APIs on your behalf | AES-256-GCM encrypted | | Scopes | Remember which products you authorized | Not encrypted |
OAuth tokens are encrypted at rest using AES-256-GCM. The encryption key is stored separately from the database, so a database breach alone cannot expose your Google tokens.
Option 1: Delete your API key
curl -X DELETE https://g.mcp.openbsp.dev/key/YOUR_API_KEY
Option 2: Revoke from Google
Both options will immediately invalidate your API key.
After authenticating, add this to your MCP client configuration:
{
"mcpServers": {
"google-mcp": {
"url": "https://g.mcp.openbsp.dev/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
MCP clients can automate the setup by redirecting users to:
https://g.mcp.openbsp.dev/auth/google?products=calendar,sheets&callback=YOUR_CALLBACK_URL
After authentication, the user is redirected to your callback with credentials in the URL fragment:
YOUR_CALLBACK_URL#api_key=gmc_xxx&url=https://g.mcp.openbsp.dev/mcp&email=user@gmail.com&files=Budget.xlsx,Sales.xlsx
| Parameter | Description |
|-----------|-------------|
| api_key | The generated API key |
| url | The MCP endpoint URL |
| email | The Google account email that authorized access |
| files | Comma-separated file names (only when Sheets authorized and files selected) |
Scopes requested:
calendar.events - read and write eventscalendar.calendarlist.readonly - list your calendars (read-only)| Tool | Description |
|------|-------------|
| list_calendars | List all your calendars |
| list_events | Get events with optional date filters |
| check_availability | Check busy/free times (no event details exposed) |
| create_event | Create a new calendar event |
| `update_eve