Google Drive
Hermoso is a marketing MCP server. Connect Google Drive once and it becomes callable from Claude, ChatGPT, Claude Code, Cursor, Codex, Cline or the CLI — the same connection the web app uses, so nothing is duplicated and nothing is re-authorised per client.
What Hermoso does with Google Drive
One connection for Drive, Sheets and Docs — pull files into the composer, save renders back, build reports and briefs. Hermoso only ever sees the files you pick in the Google picker.
Files: Drive · Sheets · Docs
Driving it from an agent
The Google Drive tools an agent can call, by name (19 today):
append_to_doc append_to_sheet clear_sheet_range create_doc create_drive_folder create_sheet delete_drive_file export_swipefile_deck format_sheet get_drive_file list_drive_files list_sheet_tabs manage_sheet_tabs read_doc read_sheet save_to_drive update_doc update_drive_file update_sheet
Connecting
Open the app, go to Workspace ▸ Connectors and connect Google Drive. One authorisation covers the web app, the MCP server and the CLI. See MCP & CLI for the endpoint and the client setup, or every channel we connect to.
Frequently asked questions
Can an AI agent post to Google Drive through Hermoso?
Yes. The Google Drive surface is exposed over one OAuth'd MCP endpoint, so Claude, ChatGPT, Cursor, Codex, Cline and the CLI can all drive it once the account is connected.
Do I need a separate Google Drive connection for the app and for MCP?
No. One authorisation covers the web app, the MCP server and the CLI — it is the same stored connection.