home / mcp / quip mcp server

Quip MCP Server

quip mcp server

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "avinashbole-quip-mcp-server": {
      "command": "node",
      "args": [
        "path/to/quip-server/build/index.js"
      ],
      "env": {
        "QUIP_BASE_URL": "https://platform.quip.com",
        "QUIP_ACCESS_TOKEN": "YOUR_QUIP_ACCESS_TOKEN"
      }
    }
  }
}

This MCP server provides programmatic access to Quip documents, letting you read, append, prepend, and replace content from AI assistants. It acts as a bridge between your MCP client and Quip, enabling smooth document interactions without manual steps.

How to use

You connect your MCP client to the Quip MCP Server and choose one of the available tools to operate on a Quip document. Core capabilities include reading a document by its thread ID, appending content to the end, prepending content to the beginning, replacing the entire content, and creating new documents (creation is currently redirected to the web interface). Use these tools to automate routine document edits as part of your assistant workflows.

Operational pattern: choose the tool that matches your desired action, provide the document identifier (threadId), and supply the content you want to add or replace. The server processes your request and returns the resulting document data or status, so your assistant can confirm the outcome and continue the conversation.

How to install

Prerequisites you need to prepare before installation are listed below. Make sure you have each item configured before proceeding.

Node.js v18 or higher is required to run the MCP server runtime.

TypeScript is needed to build the project.

Python with the Quip library installed is required for scripting interactions with Quip documents.

A valid Quip access token is necessary to authorize operations against your Quip workspace.

Step-by-step setup commands

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

Configuration and usage notes

After building, configure the MCP server so your assistant can reach Quip. The following MCP configuration runs the server locally using Node.js to execute the built index. It also provides the required environment variables for Quip access.

{
  "mcpServers": {
    "quip": {
      "command": "node",
      "args": ["path/to/quip-server/build/index.js"],
      "env": {
        "QUIP_ACCESS_TOKEN": "your-quip-access-token",
        "QUIP_BASE_URL": "https://platform.quip.com"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Operating notes

The server expects a Python script named quip_edit_fixed.py to implement the document operations. The script handles the following actions: read, append, prepend, and replace. Make sure the script is accessible at the path used by the runtime environment so the MCP server can execute it as needed.

Available tools

quip_read_document

Fetch and return the content of a Quip document by its thread ID.

quip_append_content

Append new content to the end of an existing Quip document.

quip_prepend_content

Prepend content to the beginning of a Quip document.

quip_replace_content

Replace the entire content of a Quip document with new content.

quip_create_document

Create a new Quip document (currently redirected to the web interface).