Quip MCP Server

Created By
zxkanea year ago
Model Context Procotol(MCP) server for fetching Quip document
Overview

What is Quip MCP Server?

Quip MCP Server is a Model Context Protocol (MCP) server designed for fetching and interacting with Quip documents, specifically spreadsheets.

How to use Quip MCP Server?

To use the Quip MCP Server, you can either run it directly using uvx or install it via pip. Set up the required environment variables, including your Quip API token, and run the server to start fetching spreadsheet data.

Key features of Quip MCP Server?

  • Retrieve spreadsheet content from Quip documents in CSV format.
  • Select specific sheets by name.
  • Handle authentication via Quip API token.
  • Provide error messages for non-spreadsheet documents.
  • Store spreadsheet content locally for efficient access.
  • Support for large spreadsheets with truncation and resource URIs for complete content access.

Use cases of Quip MCP Server?

  1. Extracting data from Quip spreadsheets for analysis.
  2. Integrating Quip spreadsheet data into other applications.
  3. Automating data retrieval from Quip for reporting purposes.

FAQ from Quip MCP Server?

  • Can I retrieve data from any Quip document?

Only documents that are spreadsheets can be processed. Non-spreadsheet documents will return an error.

  • Is there a limit to the size of spreadsheets I can access?

Yes, large spreadsheets may be truncated, but a resource URI will be provided to access the complete content.

  • How do I authenticate with the Quip API?

You need to set the QUIP_TOKEN environment variable with your Quip API token.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zxkane
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

3 hours ago