MCP Server
Give Claude, Cursor, and other AI assistants direct access to your Part3 data.
The Part3 MCP Server is a Model Context Protocol endpoint that exposes Part3 as a set of tools any MCP-compatible AI assistant can call — no custom code required.
Connect it once, then ask questions like:
- "What RFIs are overdue on the Riverside project?"
- "Bundle all current architectural drawings into a single PDF."
- "Show me the activity trail for submittal 04-21-06."
- "Has the electrical subcontractor been reading our emails?"
How it connects
Sign in with your Part3 account through a browser-based OAuth flow — no API keys, no client secrets, no headers. Your MCP client opens a browser to the Part3 sign-in page on first use; you approve a consent screen; tokens auto-refresh in the background after that.
Access is currently limited to Project Primes (and super-duper-admins). See Authentication for the full flow.
What the server gives you
- Pre-built tools for the most common queries — list projects, list documents, inspect activity, bundle drawings, investigate email delivery
- Acts as you — every MCP call carries your Part3 identity, so the server enforces your normal org and project permissions on every read and write
- No database access — the MCP server is a thin tool layer that calls the Part3 REST API over HTTPS for everything
- Stateless and horizontally scaled — tokens are looked up by hash on every request, so any MCP instance can handle any tool call
Setup
Pick your AI assistant to continue. Any MCP-compatible client works — pick the one closest to your setup and follow the one-liner.