quilt

Quilt MCP Server provides a runtime for the Quilt data catalog MCP tooling, exposing a suite of 84+ data-tools that can search, analyze, and manage data packages. It runs under uvx and can be used in multiple deployment modes (local, remote, or legacy Quilt3 backends). To start, run the server via uvx quilt-mcp (local deployment by default) or install the tool globally and execute quilt-mcp. The server reads configuration from environment variables such as QUILT_CATALOG_URL and QUILT_REGISTRY_URL to connect to your catalog and registry, and supports deployment presets like remote (platform + http) and legacy (quilt3 + stdio). You can also configure it through MCP configuration files by adding a quilt server with the uvx invocation and the appropriate environment variables.

Prerequisites:

• Python 3.11+ or the uv tooling installed (uvx)
• Access to the internet to pull dependencies
• Optional: Docker for local testing (not required)

Installation steps:

1. Install uv (uvx) if you don’t have it:
   • Follow uv documentation to install uv on your platform: https://uv.docs
2. Install the Quilt MCP server tooling (via uvx):
   • uvx quilt-mcp
   • If you prefer a global install, use the provided command in the Quick Start (uv tool install quilt-mcp) and then run: quilt-mcp
3. Prepare environment variables (example):
   • export QUILT_CATALOG_URL=https://quilt-catalog.example.com
   • export QUILT_REGISTRY_URL=https://quilt-registry.example.com
   • export QUILT_DEPLOYMENT=local
   • export QUILT_MULTIUSER_MODE=true
   • export AWS_PROFILE=default
   • export QUILT_SERVICE_TIMEOUT=60
4. Start the MCP server:
   • uvx quilt-mcp
   • Or if installed globally: quilt-mcp
5. Optional: use Claude integration or custom MCP clients by configuring mcp.json with the quilt server entry.

Note: Refer to the README for deployment mode options and additional environment variables.

Tips and common considerations:

• Deployment modes: local uses platform + stdio; remote uses platform + http; legacy uses quilt3 + stdio. Set QUILT_DEPLOYMENT accordingly or rely on uvx default.
• Ensure QUILT_CATALOG_URL and QUILT_REGISTRY_URL are reachable from the MCP server process.
• For testing and remote access in development, you may use NGROK or Docker-based testing workflows described in the README, but exercise caution with credentials.
• The MCP supports a variety of tools; core package operations include package_create, package_update, and package_delete. Expect read/write operations to flow through the catalog API in multiuser mode.
• If you experience SyntaxWarning from jsonlines during setup, it is a known benign warning in some environments; review the troubleshooting section in the README for context.