How do I install Google Docs?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Google Docs need an API key?

The publisher lists these environment variables: PIPEWORX_API_KEY.

What transport does Google Docs use?

Google Docs is reached over HTTP.

Google Docs MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://gateway.pipeworx.io/google_docs/mcp

Credentials from the publisher

PIPEWORX_API_KEY — Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.pipeworx-io-google_docs https://gateway.pipeworx.io/google_docs/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.pipeworx-io-google_docs": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://gateway.pipeworx.io/google_docs/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 0.2.1

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

mcp-google_docs

Google Docs MCP Pack — read, create, and edit Google Docs via OAuth. Reuses the google_sheets OAuth connection (same Google OAuth client + scopes).

Part of Pipeworx — an MCP gateway connecting AI agents to 1879+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

Tool	Description
`docs_get`	Retrieve a Google Doc by ID. Returns title, formatted body content, and document structure.
`docs_get_text`	Extract plain text from a Google Doc without formatting or structure. Use when you need raw text content only.
`docs_create`	Create a new Google Doc with a title. Returns the document ID needed for editing operations.
`docs_insert_text`	Insert text at a specific position in a Google Doc (e.g., position 0 for start, position 50 for middle).
`docs_append_text`	Add text to the end of a Google Doc. Use when insertion position doesn't matter.
`docs_replace_text`	Find and replace all occurrences of text in a Google Doc with new text.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "google_docs": {
      "url": "https://gateway.pipeworx.io/google_docs/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/google_docs/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1879+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack runs against a connected google_docs account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect google_docs, then call POST https://gateway.pipeworx.io/v1/tools/docs_get with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/docs_get. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "google_docs": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-google_docs"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-google_docs

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Google_docs data" })

The gateway picks the right tool and fills the arguments automatically.

License

MIT

Google Docs

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Google Docs?

Does Google Docs need an API key?

What transport does Google Docs use?

When was Google Docs last checked?

Documentation

mcp-google_docs

Tools

Quick Start

What this endpoint actually serves

No MCP client? Call it over HTTP

Standalone (no gateway account)

Using with ask_pipeworx

More

License