Google Mcp

io.github.matiasbattocchiaPublished by GitHub account matiasbattocchiav0.1.2Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Hosted MCP server that lets an AI assistant read and manage your Google Calendar events and Google Sheets through a proxy OAuth login and an API key.

What you can do
List calendars, list events with date filters, and check busy/free availability without event details exposed to the assistant; create, update and delete calendar events; list authorized spreadsheets and read spreadsheet metadata, sheet schemas and column statistics; search rows by filter or by meaning, read and write ranges, append rows and create new spreadsheets.
When to use it
Useful when you want an assistant to work with your Google Calendar and selected Google Sheets without creating a Google Cloud project or running a local server, for example scheduling events or querying and updating spreadsheet data.
Requirements
A remote endpoint at g.mcp.openbsp.dev, reachable over the network. A Google account to log in and grant Calendar and Sheets permissions, then an API key from the provider, sent as a Bearer token in the Authorization header. No local runtime or environment variables.
Before you install
The server holds OAuth tokens that let it act on your Google account, and the provider stores your API key as-is and your OAuth tokens encrypted. It can create, update and delete calendar events and write to spreadsheets. Your Google data passes through a third-party hosted server. Revoke by deleting the API key or removing access in your Google account; old keys stay valid until revoked.

Installation

In SourceWeft

  1. Open Google Mcp in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.matiasbattocchia%2Fgoogle-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "google": {
      "type": "http",
      "url": "https://g.mcp.openbsp.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

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

bash
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:

json
{  "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 protected]&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).

Source: README.md at commit 66972ac

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts