Claude (web)
Connect Part3 to claude.ai as a Connector — personal install or Team admin rollout.
Claude supports MCP servers via its Connectors feature. Anyone with a Pro, Team, or Enterprise plan can add Part3 — the only difference is who controls the install.
Personal install (Pro)
Each user adds Part3 to their own account.
In Claude, go to Settings → Connectors → Add custom connector.
Name: Part3. URL: https://mcp.part3.io. Leave headers and any other
fields blank.
Claude opens a browser to the Part3 sign-in page. Sign in with your Part3 account, approve the consent screen, and you're done.
In any chat, click the + menu → Tools and connectors and toggle
Part3 on. Tools appear under the model's tool picker.
Team / Enterprise rollout (admin-controlled)
On Team and Enterprise plans, an admin installs Part3 once at the organization level and chooses which workspace members can use it. Members don't need to add the connector themselves — they just toggle it on in chat.
In Claude, go to Settings → Connectors as a workspace admin. (If you don't see admin controls, you're not on a Team / Enterprise plan or don't have admin permissions.)
Click Add connector at the organization level (not "personal"). Name
it Part3, URL https://mcp.part3.io. No headers, no secret.
Pick whether all workspace members get the connector, or scope it to a subset. Each member who uses it goes through the OAuth flow once with their own Part3 account — Claude does not share tokens between users.
Each member toggles Part3 on under + → Tools and connectors the
first time they use it. They're prompted to sign in to Part3 on their
first tool call.
Per-user identity, always
The MCP server authenticates each user individually — even when an admin installs the connector for the workspace, every Part3 tool call still carries the calling user's Part3 identity, and the server enforces their org and project permissions. Admins can't impersonate other users via this connector.
Prime-only access
MCP is currently limited to users who are a Project Prime on at least one project, plus super-duper-admins. Workspace members who aren't Primes will see an access-denied page when they try to authorize.
Verify
Open any Claude chat, toggle Part3 on, and ask:
Using Part3, list my active projects.
If Claude returns a project list scoped to your Part3 access, you're wired up.
Troubleshooting
See the Claude Code troubleshooting section — the causes and fixes apply to Claude on the web as well.