MCP
The MCP server
The Google Workspace tools ship as a self-hosted Model Context Protocol (MCP) server package. Today it is a building block inside Executive, not an endpoint you connect your own assistant to.
What it is
The package @executive/mcp-google-workspace exports an MCP server named google-workspace. It lists exactly two tools, each with a JSON schema, and validates every call’s arguments against that schema before it reads any credential.
How Executive uses it
During a turn, Executive calls the same two tools as typed functions inside its own process, which keeps Google’s error details intact. The server is the standard MCP wrapper around those functions.
What it is not, yet
The server is not attached to a network transport, so there is no public MCP URL and no way to connect an outside MCP client to it today. Adding a stdio or HTTP transport is a planned adapter, not a shipped feature.