Google Mcp
Let your agent read and write Google Calendar and Google Sheets through a hosted streamable HTTP MCP endpoint after OAuth login.
Overview
google-mcp is a MCP server for the Build phase that provides streamable HTTP access to Google Calendar and Google Sheets with OAuth login.
What is this MCP server?
- Streamable HTTP MCP remote at https://g.mcp.openbsp.dev/mcp
- Tools target Google Calendar and Google Sheets with OAuth-based Google login
- Requires Authorization Bearer API key from https://g.mcp.openbsp.dev
- Version 0.1.2; repository github.com/matiasbattocchia/google-mcp
- Keeps scheduling and spreadsheet updates inside the agent thread for solo PM and ops work
- Remote URL https://g.mcp.openbsp.dev/mcp with streamable-http transport
- Server version 0.1.2
- Scopes described as Google Calendar and Google Sheets with OAuth
What problem does it solve?
Solo builders duplicate work between their agent and Google Calendar or Sheets because there is no OAuth-backed MCP bridge for scheduling and spreadsheet updates.
Who is it for?
Indie operators who run launch and ops in Google Calendar and Sheets and want Claude Code or Cursor to manage events and sheet data via MCP.
Skip if: Builders avoiding Google Cloud data, teams needing Drive or Gmail MCP tools, or workflows that require fully offline/local-only integrations.
What do I get? / Deliverables
After you add the remote MCP URL with a Bearer API key and complete OAuth, your agent can interact with Calendar and Sheets from the coding environment.
- Agent-driven Google Calendar operations after OAuth
- Agent-driven Google Sheets read and write workflows
- Hosted MCP endpoint without self-running a Google API proxy locally
Recommended MCP Servers
Journey fit
Google Workspace hooks land during build when solo founders connect scheduling, ops spreadsheets, and launch planning to their agent. Remote streamable-http MCP with API key auth is a hosted integration pattern for Calendar and Sheets, not local agent-tooling binaries.
How it compares
Hosted Google Calendar and Sheets MCP with OAuth, not a generic Google Cloud admin skill or local gcloud CLI wrapper.
Common Questions / FAQ
Who is google-mcp for?
Solo builders and small teams that centralize planning in Google Calendar and Sheets and want their coding agent to read and update those apps via MCP.
When should I use google-mcp?
Use it when wiring workspace integrations during build or daily ops—scheduling ship dates, tracking leads, or updating launch checklists in Sheets from the agent.
How do I add google-mcp to my agent?
Get an API key from https://g.mcp.openbsp.dev, configure the streamable-http remote https://g.mcp.openbsp.dev/mcp with Authorization Bearer header, and complete OAuth login for Google access.