Google Docs MCP for Hermes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docs_readA | Read bounded content, tab metadata, and the current Docs revision. |
| docs_createC | Create a private native Google document and verify its initial content. |
| docs_replace_markdownB | Replace one document tab from Markdown under an exact revision guard. |
| docs_edit_textA | Preview or apply exact, revision-guarded replacements in one tab. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Read and create are clearly distinct, while replace_markdown and edit_text both modify a document and could be confused. However, their descriptions draw a clear line between whole-tab Markdown replacement and precise revision-guarded text edits, so misselection is unlikely.
All tools use lowercase snake_case with a docs_ prefix and action-oriented verbs. There is a minor inconsistency because read and create omit explicit objects while replace_markdown and edit_text include them, but the pattern remains predictable.
Four tools is a tight, purposeful set for reading, creating, and editing Google Docs content. Each tool covers a distinct core operation and none feel redundant or unnecessary for the server's focused scope.
The set covers the core create/read/update workflows and revision-guarded edits. It lacks document deletion, listing, or full-content export, but agents can work around these gaps for most document editing tasks.