Read, append, prepend and replace all work; document creation is declared unsupported and sends you to the web UI, so do not plan a workflow that starts with a new doc. The two-runtime setup is the real cost — Node for the server, Python with the `quip` library for the script it calls — so budget for both when you install.
An MCP server that bridges an assistant to Quip documents. It receives the call, runs a Python helper script against the Quip API with the right parameters, and returns the result — so document edits happen through a script you control rather than direct API calls from the model.
- A Quip document read back by its thread ID — `quip_read_document`
- Content added to the end of an existing document — `quip_append_content`
- Content added to the beginning — `quip_prepend_content`
- Document content replaced outright — `quip_replace_content`
- `quip_create_document` is present but currently unsupported — it redirects to the web interface
A valid Quip access token, set as `QUIP_ACCESS_TOKEN`, with `QUIP_BASE_URL` pointing at `https://platform.quip.com`. Node.js v18 or higher, TypeScript, and Python with the `quip` library installed — the server shells out to a script named `quip_edit_fixed.py` at the path in its `PYTHON_SCRIPT_PATH` constant, and that script has to support read, append, prepend and replace. Clone, `npm install`, `npm run build`, then point the config at `build/index.js`. The package is `quip-server` 1.0.0 under the ISC License.
Build from source — clone the repository and build it, then point your client at the binary