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

| 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.

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

| 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) |

Available Tools

Calendar

Scopes requested:

• calendar.events - read and write events
• calendar.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

... View full README on GitHub