Quip MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUIP_API_BASE | No | The base URL for the Quip API. Defaults to https://platform.quip.com. For custom domains, set to e.g. https://yourcompany.quip.com | https://platform.quip.com |
| QUIP_ACCESS_TOKEN | Yes | Your Quip API access token (generate one at https://quip.com/dev/token) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quip_get_userA | Get the current authenticated Quip user's profile, including name, email, and key folder IDs |
| quip_get_folderB | Get a Quip folder's contents, listing its child documents and subfolders |
| quip_get_documentA | Get a Quip document's content as markdown |
| quip_searchB | Search Quip documents by query string |
| quip_browse_folder_treeA | Recursively browse a Quip folder hierarchy, showing documents and subfolders as an indented tree |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource or action: user, folder contents, document content, search, and folder tree browsing. Even get_folder and browse_folder_tree differ in depth (single level vs. recursive tree), avoiding confusion.
All tools share the 'quip_' prefix and use a consistent verb_noun pattern (get_user, get_folder, get_document, search, browse_folder_tree). Renaming 'search' to 'search_documents' would be slightly more uniform, but the existing style is very predictable.
Five tools is well-scoped for a read-only Quip client, covering user, folder, document, search, and hierarchical browsing. Each tool earns its place without redundancy or bloat.
The set is strong for reading and searching Quip content, but lacks any mutation tools (create, update, delete) for documents or folders. If the server is intended to be read-only, it's fairly complete; otherwise, it has notable gaps.