io.github.matiasbattocchia/google-mcp

Official registry Productivity

Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.

What can you do with io.github.matiasbattocchia/google-mcp?

  • List and search your calendar events
  • Create, update, or delete events
  • Read and write to Google Sheets
  • Create new spreadsheets

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http google-mcp 'https://g.mcp.openbsp.dev/mcp' --header 'Authorization: <Bearer token with your API key from https://g.mcp.openbsp.dev>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "google-mcp": {
            "type": "http",
            "url": "https://g.mcp.openbsp.dev/mcp",
            "headers": {
                "Authorization": "<Bearer token with your API key from https://g.mcp.openbsp.dev>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. OpenBSP MCP for Google Workspace
  2. Why this exists
  3. What you can do
  4. How it works
  5. Privacy & Security
  6. Setup for MCP Clients
  7. Available Tools
  8. Self-Hosting
  9. FAQ

OpenBSP MCP for Google Workspace

A public Model Context Protocol (MCP) server that lets AI assistants access your Google Calendar and Sheets.

**Live at: https://g.mcp.openbsp.dev**

Why this exists

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:

  1. Click "Login with Google"
  2. Get an API key
  3. Add it to your MCP client

No Google Cloud setup. No local servers. No environment variables. Just connect and go.

What you can do

Once connected, ask your AI assistant to:

  • List and search your calendar events
  • Create, update, or delete events
  • Read and write to Google Sheets
  • Create new spreadsheets

How it works

┌──────────────┐     ┌──────────────────┐     ┌──────────────┐
│  AI Client   │────▶│  OpenBSP MCP     │────▶│  Google APIs │
│  (Claude)    │◀────│  Server          │◀────│              │
└──────────────┘     └──────────────────┘     └──────────────┘
  1. You select which Google products to connect (Calendar, Sheets)
  2. You authenticate with Google and grant permissions
  3. You receive an API key to configure your MCP client
  4. Your AI assistant can now access your Google data

Privacy & Security

What we store
DataPurposeProtection
API KeyAuthenticate your MCP clientStored as-is (random 256-bit value)
OAuth TokensAccess Google APIs on your behalfAES-256-GCM encrypted
ScopesRemember which products you authorizedNot 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.

What we DON'T store
  • Your Google password
  • Your email content
  • Your calendar events or spreadsheet data
  • Any personal information
Data retention
  • API keys: Stored until you revoke them (or until expiration if set)
  • OAuth tokens: Stored alongside your API key
  • Temporary auth states: Deleted after 10 minutes
How to revoke access

Option 1: Delete your API key

curl -X DELETE https://g.mcp.openbsp.dev/key/YOUR_API_KEY

Option 2: Revoke from Google

  1. Go to Google Account Security
  2. Find "OpenBSP MCP" in the list
  3. Click "Remove Access"

Both options will immediately invalidate your API key.

Setup for MCP Clients

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"
      }
    }
  }
}
Programmatic integration

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
ParameterDescription
api_keyThe generated API key
urlThe MCP endpoint URL
emailThe Google account email that authorized access
filesComma-separated file names (only when Sheets authorized and files selected)

Available Tools

Calendar

Scopes requested:

  • calendar.events - read and write events
  • calendar.calendarlist.readonly - list your calendars (read-only)
ToolDescription
list_calendarsList all your calendars
list_eventsGet events with optional date filters
check_availabilityCheck busy/free times (no event details exposed)
create_eventCreate a new calendar event
update_eventUpdate an existing event
delete_eventDelete an event
Sheets

Scope requested:

  • drive.file - access only files you select or files created by the app
ToolDescription
list_authorized_filesList files the user has authorized for access
get_spreadsheetGet spreadsheet metadata, sheets, and tables
get_sheet_schemaGet column names and inferred types
describe_sheetGet statistical summary of all columns
search_rowsSearch for rows matching filter criteria
semantic_searchAI-powered semantic search over rows (finds by meaning, not exact match)
read_sheetRead data from a range (e.g., "A1:D10")
write_sheetWrite data to a range
append_rowsAppend rows (supports Tables with tableId for footer-aware append)
create_spreadsheetCreate a new spreadsheet

The drive.file scope only grants access to files the user explicitly selects during authentication (via Google Drive Picker) or files created by the app. Use list_authorized_files to discover which spreadsheets are available.

Tables support: The get_spreadsheet tool returns table metadata including tableId. Pass this to append_rows for proper table-aware appending that respects footers and auto-expands the table.

Semantic search: The semantic_search tool uses AI embeddings to find rows by meaning. Powered by TAG.

Self-Hosting

Want to run your own instance? See DEPLOY.md for instructions.

FAQ

Is this official? No, this is an independent open-source project. It is not affiliated with Google or Anthropic.

Is it safe? We only request the minimum permissions needed. Your data flows directly between Google and your AI client through our server - we don't store or log it.

Can I see the code? Yes! This project is open source. Review the code, run your own instance, or contribute improvements.

What if I lose my API key? Generate a new one by authenticating again. Old keys remain valid unless you revoke them.

Does it cost anything? This public instance is free. If you self-host, you'll pay for Cloudflare Workers (generous free tier available).

Frequently asked questions

What is io.github.matiasbattocchia/google-mcp?

Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.

How do I install io.github.matiasbattocchia/google-mcp?

It runs as a remote server. In Claude Code: claude mcp add --transport http google-mcp 'https://g.mcp.openbsp.dev/mcp' --header 'Authorization: <Bearer token with your API key from https://g.mcp.openbsp.dev>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.matiasbattocchia/google-mcp need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is io.github.matiasbattocchia/google-mcp open source?

Yes. Its code is on GitHub under the Unlicense license.

Who maintains io.github.matiasbattocchia/google-mcp?

It is published by matiasbattocchia. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.