Name: Quip MCP Server
Author: AvinashBole

LABSCO SUMMARY

Four working operations and one that is not.

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.

What it is

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.

What you get

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

Requirements

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, and python on your PATH with Quip's official Python client (quip.py from the quip-api repository) — the server runs the bundled scripts/quip_edit.py for every read and edit. 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.

Setup effort

Build from source — git clone https://github.com/AvinashBole/quip-mcp-server.git

See installation options

USE CASES

01

Pulling a spec into the conversation

Read the document by its thread ID and work from its actual content instead of a pasted excerpt.

quip_read_document

02

Adding to a running log

Append the new entry to the end of the document without opening Quip.

quip_append_content

03

Putting the latest update at the top

Prepend the summary so the newest note is the first thing a reader sees.

quip_prepend_content

04

Rewriting a document wholesale

Replace the content in one call when the new version is generated rather than edited.

quip_replace_content

5 tools

Listed in project docs. Your client may show a different list.

quip_read_document

quip_append_content

quip_prepend_content

quip_replace_content

quip_create_document

BEFORE YOU INSTALL

What to know first

Tools you get

5 tools named in the project's documentation. quip_create_document is listed but does not work; creating a document currently redirects to the web interface.

Requires

Node.js v18 or higher
python on PATH, with the official Quip Python client (quip.py)
QUIP_ACCESS_TOKEN in your environment

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

You clone and build this one yourself.

Server setup

TERMINAL

git clone https://github.com/AvinashBole/quip-mcp-server.git
cd quip-mcp-server
npm install
npm run build

Save quip.py, the official Quip Python client from https://github.com/quip/quip-api/tree/master/python, into the scripts/ folder of your clone — the server runs scripts/quip_edit.py with python, and that script imports quip (the quip package on PyPI is an unrelated project)

Add the configuration to your client; <YOUR_PATH_TO_QUIP_MCP_SERVER> is the absolute path of your clone and <YOUR_QUIP_ACCESS_TOKEN> is your Quip access token

MCP Clients

Any MCP client

ANY MCP CLIENT · JSON

{
  "mcpServers": {
    "quip": {
      "command": "node",
      "args": [
        "<YOUR_PATH_TO_QUIP_MCP_SERVER>/build/index.js"
      ],
      "env": {
        "QUIP_ACCESS_TOKEN": "<YOUR_QUIP_ACCESS_TOKEN>",
        "QUIP_BASE_URL": "https://platform.quip.com"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Quip MCP Server