Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Gdocs MCP
Overview
Description from the maker (original English)
Treat a Google Doc like a local file: content editing, tracked-changes review, comments, tables.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"gdocs": {
"command": "npx",
"args": [
"-y",
"@dasasian/gdocs-mcp"
]
}
}
}Run this in your terminal
claude mcp add gdocs -- npx -y @dasasian/gdocs-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gdocs": {
"command": "npx",
"args": [
"-y",
"@dasasian/gdocs-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"gdocs": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dasasian/gdocs-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dasasian, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32696 servers in this category
- Published to the registry more recently than 82% of the other 32696 servers in this category
- Basic checks equal to or better than 100% of the other 32696 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Gdocs MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 7 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
LexPact UK Contracts
by Idadabhai
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@dasasian/gdocs-mcp
An MCP server that lets an AI agent (like Claude Code) treat a Google Doc like a local file — read it, edit it by content, review and resolve suggestions, manage comments, and work across tabs and multiple Google accounts.
Status: beta. The tool surface is complete and every change is verified against the live API, not just unit tests.
Why this exists
Most Google Docs MCP servers treat a doc as flat text. This one fills the gap nobody else does:
- Suggestions you can read and act on.
list_suggestionsshows each pending tracked change with Docs' own summary, the change in its sentence (Pay within [30→45] days), its author and time;apply_suggestionsaccepts or rejects each one on its own, as the check and the cross do in Docs.read_doccan render them inline as/. - File-like editing.
edit_docmatches a unique snippet of text (like a localEdit) and rewrites it — indices are never exposed. - Comments on their text. Read threads (author, time, the text each is on, replies, resolved status), reply, resolve, and add a comment on the text you quote, which stays on that text as it moves.
- Tabs as sub-files. A doc is a folder of tabs:
drive lslists them,drive mvrenames, reorders and nests them. - Multiple accounts. Authorize several Google accounts; pick a default per project.
What you can ask for
You don't call tools. You ask in plain language and the agent drives them.
Fill a template without rebuilding it
*"Copy the Proposal Template into /Clients/Acme, name it 'Acme Q3 Proposal', then fill in the client name, the dates, and the pricing table."*
The copy keeps the letterhead, the logo at its exact size, the fonts and the page setup — everything a markdown round-trip cannot rebuild. Then only the words that change are edited. The alternative is retyping a document you already have.
A whole review pass in one instruction
*"Show me the pending suggestions as a diff, accept the typo fixes, reject anything that changes meaning, then reply to the open comments and resolve the ones that are settled."*
Four tools, one sentence, and the judgement in the middle is the part you wanted help with. Most Docs integrations cannot see tracked changes at all, let alone act on them safely.
More: publishing a folder of markdown as a Drive tree, auditing many docs for style drift, pulling a doc back into your repo with its images → [docs/recipes.md](docs/recipes.md).
Install
npm install -g @dasasian/gdocs-mcpOr from source:
git clone https://github.com/dasasian/gdocs-mcp && cd gdocs-mcpnpm install && npm run build npm link # makes gdocs-mcp available globally, same as the published package
Then follow the setup below exactly as an installed user would. (npm link symlinks the gdocs-mcp binary to your build; see CONTRIBUTING.md for the dev workflow.)
Setup
You need a Google Cloud OAuth client (one-time). Each user creates their own — this keeps your credentials yours and avoids Google app-verification for the restricted Drive scope.
- Create a project + enable APIs (or use the setup guide):
gcloud projects create my-gdocs-mcpgcloud config set project my-gdocs-mcp gcloud services enable docs.googleapis.com drive.googleapis.com
2. **OAuth consent screen** (Cloud Console → APIs & Services → OAuth consent screen): User type **External**, add yourself as a **Test user**. For long-lived tokens, set publishing status to **In production** (avoids the 7-day refresh-token expiry).- OAuth client → Create credentials → OAuth client ID → Desktop app. Download the JSON and save it as
~/.config/gdocs-mcp/client_secret.json. - Authorize an account (opens a browser):
gdocs-mcp add-accountRepeat for each Google account you want to use.
Configure your MCP client
In a project's .mcp.json (Claude Code) or equivalent:
{"mcpServers": { "gdocs": { "command": "gdocs-mcp", "env": { "GDOCS_DEFAULT_ACCOUNT": "you@example.com" } } } }
GDOCS_DEFAULT_ACCOUNT sets which authorized account this project uses by default — so a work project and a personal project can point at different accounts without re-authorizing. Any tool call can override it with an account argument.
Prefer it available in every project? Register once at user scope: claude mcp add gdocs -s user -e GDOCS_DEFAULT_ACCOUNT=you@example.com -- gdocs-mcp. Then a project can pin its own defaults with a .gdocs-mcp.json — the account, and a default folder for new docs:
{ "account": "work@company.com", "folder": "https://drive.google.com/drive/folders/…" }write_doc creates only from a path (/Reports/Q3 Report). Given a bare name (Q3 Report) it creates nothing: it refuses, tells the agent to tell you the doc will go in the default folder, and hands back the full path to call. A new doc at the top of My Drive (/Q3 Report) is refused once the same way, and the identical call repeated goes through if you want it there. The default folder's path is also in write_doc's description, read when the server starts. With no default it says to name a folder (~/Q3 Report). See docs/setup.md for the full resolution order.
You don't have to edit that file by hand — just tell the agent *"make damithsc@gmail.com my default account for this project"* or *"make my Manuscripts folder the default here,"* and it writes the .gdocs-mcp.json for you via set_project_default (searching for the folder by name if needed).
Tools
The table below is the reference. For what to actually *ask for*, see What you can ask for above, or the full set in [docs/recipes.md](docs/recipes.md).
| Tool | Description |
|---|---|
read_doc | Read as markdown + inline HTML. Opens with a block (the named styles as CSS: p, h1–h6, .title, .subtitle); a paragraph shows style="…" only where it differs from its rule — alignment, spacing, line height, indent — and text color/size/font come back as , so styling is visible and round-trips. Modes: clean · tracked ( / ) · accepted · rejected. segment: body (default) / header / footer / all — a body read always reports what the headers/footers hold, so a letterhead never reads as empty. Document text that would parse as markup is marked literal — 4. Term , 5 \* 3, \\ for a real backslash; a line that starts or ends with a space or tab reads as ⇥Indented clause and the writer keeps every space and tab inside , so a read written back gives the same document. A page break reads as on its own line, and writes back as one. Every element in a paragraph reads (#58): a footnote as [^1] with its note as a [^1]: … line at the end, a date as Nov 15, 2026 , a person or Drive link chip as Jane Doe , a dropdown as with its list once as a after the block, a horizontal rule as ---, a column break as , an equation and a page-number field as an empty / whose title says to edit them in Docs. A table of contents is not read |
edit_doc | Replace a unique text snippet (string-anchored, markup-tolerant; a table matches as its rows, a pipe table or the HTML of a styled one). new_string is the full markdown write_doc takes — headings, lists, tables, images, page breaks — with contentFile for long text and baseDir for relative image paths. Inserting is an edit: quote the anchor and write it back with the new content after it. Text that comes back unchanged is kept (its style, comments and suggestions stay), a match that ends in a table puts new blocks after the table, an anchor mid-paragraph splits the paragraph, and a new block carries its own style rather than its anchor's. An empty doc, tab, header or footer has no anchor: use write_doc. `suggest: true` sends the edit as suggestions for a person to accept or reject in Docs, and the result lists their ids in suggestions; it defaults to false, a direct edit. Same words with different markup is a style-only edit — no delete, no insert. A table edit that changes rows, columns or merges is a comparison: quote the rows around the change and write the rows you want, and only the difference is sent (insertTableRow, deleteTableRow, insertTableColumn, deleteTableColumn, mergeTableCells, unmergeTableCells, plus the text of the cells that changed), so the other cells keep their comments and style; a new row or column copies its neighbour's style, a moved row or column is a delete and an insert and asks (confirmLoss) when comments quote its text, and a change that cannot be read cleanly is refused with what to quote. A table is never rewritten whole. Editing a rule in the block restyles the whole doc through one updateNamedStyle. A page break is a line of its own, so new_string Title page\n puts the next paragraph on a new page, and an anchor can span one. Elements: one an edit gives back unchanged is kept (a person chip inside a sentence you reword, a footnote, a dropdown, a rule), one it drops is deleted, a new one is created (createFootnote, insertDate, insertPerson, insertRichLink, insertDropdown), and one the API cannot make (a column break, an equation, a page-number field, a link chip to anything but a Drive file) is refused before anything is sent, saying what to write instead. A footnote's note is edited by quoting its [^1]: … line, a dropdown's list by quoting its line. A chip's text is Google's: a chip given other words is refused |
get_page_setup / set_page_setup | Read / set document-level page setup: margins, page size (preset or explicit), orientation (File > Page setup) |
| write_doc | Write like the local Write: a path that names nothing is created — a doc in a folder (/Work/Contract), a tab in a doc (/Work/Contract/Notes), a child tab (/Work/Contract/Part 2/Ch.4) — and never asks. A path that names something is replaced, and the first call is refused with a loss summary: paragraphs, comments, suggestions, tab stops, links to bookmarks, page-number fields, section breaks, a table of contents, column breaks, equations, dates in a format the API can only read and link chips to anything but a Drive file, plus a confirmLoss string. Footnotes, pers
Only the beginning is shown; read the rest in the repo