Quip Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Nov 1, 2026

Quip Automation API: thread search, thread content, folders. Needs token.

VerifiedSTDIODesktop onlyProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Local MCP server that connects an assistant to the Quip Automation API for searching threads, reading thread content and browsing folders.

What you can do
  • Search Quip threads
  • Read the content of a thread
  • Browse folders in the Quip account
  • Access is through the Quip Automation API, so the assistant works with the same threads and folders the token can see.
When to use it
Useful when your team keeps documents, notes or project material in Quip and you want an assistant to find and read that content without copy-pasting it into the chat.
Requirements
Runs as a local process, installed from the npm package quip-mcp over stdio, so Node.js is needed. A Quip API token is required; the manifest declares no environment variables or headers, so the token must be supplied some other way.
Before you install
The server needs a Quip API token, which grants access to the threads and folders that token can reach; treat it as a secret. The manifest declares no environment variables or headers, so check how the token is passed and stored before installing. The listed capabilities are read-oriented, but confirm whether any tool can modify Quip content.

Installation

In SourceWeft

  1. Open Quip Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.1LatestOct 1, 2026
  2. v1.0.0Sep 24, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.