Developer Tools
Give your coding agent searchable, authoritative Google Workspace developer documentation while you build add-ons, apps, and API integrations.
Overview
goog.workspace-developer/developer-tools is an MCP server for the Build phase that lets agents search Google Workspace developer documentation via a hosted streamable-http endpoint.
What is this MCP server?
- Official Google Workspace developer MCP remote at workspace-developer.goog/mcp
- Tools for searching Workspace documentation and related developer resources
- Streamable-http transport for MCP-capable clients
- No API key called out in the published server manifest
- Version 1.0.0 against MCP server schema 2025-09-29
- Remote MCP URL https://workspace-developer.goog/mcp
- Server version 1.0.0
What problem does it solve?
Your agent keeps guessing Workspace API details, scopes, and doc links while you are building integrations.
Who is it for?
Indie developers building Workspace add-ons, Apps Script alternatives, or API automations who want doc-grounded agent answers.
Skip if: Teams not targeting Google Workspace APIs, or builders who need direct production API execution without separate OAuth implementation.
What do I get? / Deliverables
After adding the remote MCP, your agent can query official Workspace developer documentation tools instead of relying on stale training data.
- Doc-search MCP tools wired into your agent session
- Faster, source-linked answers for Workspace implementation questions
- Remote endpoint entry at workspace-developer.goog/mcp in project config
Recommended MCP Servers
Journey fit
Workspace API work happens during build when you implement features against Gmail, Drive, Calendar, and related surfaces. Documentation search and reference tooling maps to the docs subphase—agents need correct API guidance before you ship integrations.
How it compares
Official Google Workspace documentation MCP, not a generic browser automation skill or cloud deploy pack.
Common Questions / FAQ
Who is goog.workspace-developer/developer-tools for?
Solo builders and small teams implementing Google Workspace apps, add-ons, or API integrations who want MCP-backed doc search in their coding agent.
When should I use goog.workspace-developer/developer-tools?
Use it during build and docs-heavy integration spikes whenever you need current Workspace API guidance inside Claude Code, Cursor, or Codex.
How do I add goog.workspace-developer/developer-tools to my agent?
Configure the streamable-http remote MCP URL https://workspace-developer.goog/mcp in your client’s MCP settings following your host’s remote-server instructions.