runelay+Google DocsIntegration · OAuth login
Google Docs on Runelay, an open source MCP gateway
Your agents write straight into Google Docs: start a document, read one you point them at and keep adding to it.
Built into Runelay
Runelay calls the Google Docs API itself with your Google token, with no third-party MCP server in between. account_whoami shows which Google account is connected.
Tools
- Create.
create_documentmakes an empty Google Doc with a title and returns its id and URL. - Read.
read_documentreturns a document's title and its plain text. - Write.
append_textadds text to the end of the document body.
Try asking
- “Create a Google Doc called Release notes and write the changes from this branch in it.”
- “Read the spec doc I just linked and list the open questions.”
- “Append today's decisions to the end of our meeting notes doc.”
How it signs in
- Google OAuth through the Runelay broker. No Google Cloud project of your own; Runelay renews the token.
- Scopes:
documents,drive.file, plusopenid,userinfo.emailanduserinfo.profile.
What this connection does
Agents find these tools with search_tools and run them with call_tool, so they only enter the context when a task needs them.
Connect Google Docs
Open the connectors in the panel
Pick Google Docs from the catalog.
Log in once
A browser tab opens on Google Docs. Approve the access and close it.
Done
The token is stored encrypted on your server and refreshed by Runelay. Every agent with a Runelay key can use the connection.
Use Google Docs in your agents
Agents do not need a Google Docs entry of their own. Point each one at Runelay and Google Docs is there.
Questions
Can it edit the middle of a document?
No. append_text writes at the end of the body. Rewriting a section is not supported yet.
Does reading keep the formatting?
read_document returns the title and the plain text, without styles.
Can it open documents it did not create?
Yes, if your account can open them. The documents scope covers your Google Docs, so pass the document id or link.