Propper MCP Server

Disclaimer

The Propper MCP Server is provided "as is" and "as available" without warranty. You may experience bugs or performance issues, and the feature may change as Propper refines it. By using the MCP Server, you acknowledge you do so at your own discretion and risk. Users should have a "human in the loop" to confirm tool actions and review the accuracy of AI output.

Propper provides a Model Context Protocol (MCP) server that lets Claude and other MCP clients interact with your Propper workspace. Connect to https://mcp.propper.ai/mcp using Streamable HTTP and OAuth 2.0 with PKCE.

This guide covers the custom connector in Claude web and Desktop. For a complete workflow with skills, start with Use Propper in Claude, install the Cowork plugin, or follow the Claude Code setup.

Prerequisites

• A Claude account with custom connectors available under your plan and organization policy. See Anthropic's current availability.
• A Propper account. If you don't have one, choose Sign up on the Propper sign-in page that opens when you connect: you verify your email, Propper creates a 14-day trial organization for you, and the connection continues where it left off. Ongoing API access is included on Business plans; see current pricing.
• For Claude Team or Enterprise setup, an Owner or Primary Owner adds the connector before members connect their accounts.

Personal Claude setup

Open Customize → Connectors → Add in Claude and follow the connector setup below. On a personal account, you add the connector yourself. On Team or Enterprise, an Owner or Primary Owner adds it for the organization.

Propper supports dynamic client registration, so a compatible client registers itself. You do not need to create an OAuth client or paste a key for the standard setup.

Step 1: Add the Propper connector (admin)

note

This step only needs to be done once per Claude organization. If your admin has already added the Propper connector, skip to Step 2.

The screenshots below were captured from Claude on the web on September 18, 2026. Labels can vary by Claude version and account.

1. Open Customize → Connectors, or go directly to the Connectors directory.

2. Click Add to open Add custom connector. Some interface versions show + → Add custom connector or Add → Custom → Web in organization settings.

3. Enter the following details:

   • Name: Propper
   • URL: https://mcp.propper.ai/mcp

4. Click Continue. Claude checks the server URL and sign-in settings; follow the remaining setup prompts, then connect your account. If Claude says a connector with this URL already exists, use the existing Propper connector instead of creating another one.

If your interface shows OAuth Client ID and Client Secret under Advanced settings, leave them blank for the standard connection. Dynamic client registration handles it.

Only if your organization requires a manually managed client: an authorized Propper administrator can create one under Settings → OAuth Clients → Create MCP Client. Review its redirect URIs and permissions for the intended client, then enter the generated credentials in Claude's Advanced settings. Do not put credentials in a conversation.

Step 2: Connect your account

Each user in your Claude organization connects their own Propper account.

The screenshots below illustrate the connection flow; available permissions and labels may differ from your current account.

1. Open Customize → Connectors → Yours in Claude, or use the Connectors settings page in an older interface.

2. Open the Propper custom connector and choose Connect. If it already shows Connected, continue to start using Propper.

3. You'll be redirected to the Propper sign-in page. Enter your email and sign in.

4. Select the intended Propper organization and review the requested permissions against the scope guide. Authorize only a connection whose requested access is appropriate for your workflow, then click Authorize.

5. You'll see a confirmation that the connection was successful. You'll be redirected back to Claude automatically.

6. Back in Claude, open the Propper connector and confirm that it shows Connected.

Step 3: Start using Propper in Claude

Enable Propper for the conversation through + → Connectors. Start with a read-only request to confirm the right organization and access:

• "Show my connected Propper organization and list my recent agreements."
• "Which agreements are waiting on signatures, and whose turn is next?"
• "Prepare an NDA draft for Jordan Lee. Ask me for the recipient's email address and show me the draft before sending."

Install the Propper skills for guided document checks, generation, and signing workflows. Generation requires Propper Gen access; document questions in Locker require Locker AI private-beta access. The server does not apply signatures or send reminder emails.

Permissions and approvals

Tools act within the connected Propper organization, subject to the OAuth grant, your role, and product access. A connection does not grant permissions beyond your account's access.

Scope	Allows
openid, offline_access	Identity and refresh tokens for an ongoing connection.
sign:read	Read agreements, templates, documents, and signing status.
sign:write	Create and edit draft agreements, recipients, documents, and fields; create and import Sign templates; delete draft agreements.
sign:send	Send agreements, create an agreement from a Sign template and send it, generate a document from a Gen template and send it, and void agreements already in flight.
org:read, users:read	Read organization information and members.
users:write	Invite members, change roles, remove members, and cancel pending invitations.
docgen:read	Read generation templates and generated-document records.
docgen:write	Create or update generation templates, generate documents, and preview HTML/Markdown templates as HTML.
locker:read	Read and search Locker documents and extracted risks, including document questions where available.
locker:write	Upload, register, update, and delete Locker documents; extract risks and update a risk's workflow state.

The per-tool scope reference covers additional actions. PDF/URL and DOCX-source previews require docgen:preview, which is reserved for platform use and unavailable to MCP clients. For a PDF, generate the document and retrieve it through Propper's document download flow.

Keep tool approvals enabled for writes. Review the agreement, documents, recipients, and signing order before sending. Creating an agreement from a Sign template sends it immediately unless Claude is asked to keep it as a draft, and generating a document from a Gen template and sending it happens in one step. Voiding cancels a sent agreement and notifies recipients; deletion applies to drafts. Removing a member ends that member's sessions in the organization. The skills instruct Claude to request explicit confirmation for these actions.

Troubleshooting

I don't see the Propper connector in my settings

On Team or Enterprise, an Owner or Primary Owner must add the custom connector first. See Step 1. For a personal account, use personal setup. Also confirm that you selected the intended Claude organization.

The authorization page shows an error

Make sure you're signing in with an email address that belongs to an active Propper organization. If your organization uses SSO, sign in through your SSO provider.

Claude says it can't access Propper

Check that Propper is enabled for this conversation. If authentication has expired, disconnect and reconnect from Customize → Connectors. Verify the URL is exactly https://mcp.propper.ai/mcp.

A tool reports a missing scope or permission

Check the required scope in the reference, then reconnect to review the grant. If access is still denied, ask your Propper administrator to check your role and product access. Repeating the same tool call does not change its permissions. Do not request docgen:preview for an MCP connection; use HTML preview or the generated-document download flow instead.

I want skills or a terminal connection

See Propper Skills for Cowork and organization installation, or Propper in Claude Code for plugin and MCP-only setup.