quip

This MCP server provides a bridge between Claude and Quip documents, enabling AI-assisted read/write operations on Quip. It exposes tools to read a document, append content, prepend content, replace content, and (in theory) create new documents. Once the MCP server is running and connected to Claude, you can invoke the tools via the Claude interface using the dedicated MCP tool names (e.g., quip_read_document, quip_append_content, quip_prepend_content, quip_replace_content, quip_create_document). Each tool accepts a JSON payload with the required fields (for example, threadId for reads, and content payloads for writes). The server delegates the actual work to a Python script (quip_edit_fixed.py) that performs the Quip API calls, using the provided access token.

To use, configure your Claude integration to point at the quip MCP in your MCP settings. Then, in Claude, request a tool like quip_read_document and supply the necessary arguments (e.g., the Quip document threadId). The response will contain the requested content or the result of the modification operation. The create_document tool is currently unsupported and redirects users to the Quip web interface.

Prerequisites:

• Node.js v18 or higher
• TypeScript (for building/ts tooling, if applicable)
• Python with the quip library installed (for quip_edit_fixed.py usage)
• A valid Quip access token with appropriate permissions

Installation steps:

1. Clone the repository:

git clone https://github.com/AvinashBole/quip-mcp-server.git
cd quip-mcp-server

2. Install dependencies:

npm install

3. Build the project (if a build step is required by your setup):

npm run build

4. Configure MCP settings (see mcp_config example below) and ensure you have a valid Quip access token.

Configuration example (in your MCP config):

{
  "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": []
    }
  }
}

Notes and tips:

• Ensure QUIP_ACCESS_TOKEN has the necessary scopes to read and modify documents.
• QUIP_BASE_URL should point to the Quip API base (default is https://platform.quip.com).
• The server relies on the Python script quip_edit_fixed.py via the PYTHON_SCRIPT_PATH configuration; make sure this script exists at the path the server expects.
• The create_document operation is noted as unsupported in the current implementation and will redirect to the Quip web interface.
• If you encounter authentication errors, verify token validity and that the token is correctly loaded by the Node process (env variables are passed through to the Python layer).
• When upgrading dependencies, re-run npm install and rebuild as needed to ensure compatibility with the MCP framework.