Choose remote MCP for cloud projects and already-synced records. Use the separate local connector only when you need access to a folder on this computer.
Any Agent may be used if its host has the required capabilities. No vendor is the default or certified entry point.
Two ways to connect
Remote MCP
HTTPS + browser OAuth + read-only cloud project and record data
Endpoint: https://portraitpayai.com/api/mcp
Your host must support remote MCP over Streamable HTTP and browser-based OAuth authorization with PKCE. Adding a URL in chat or pasting a prompt alone does not install or connect an MCP server.
It can:
See the projects your account is allowed to access.
See records synced by the authorizing user, not every team member.
See the status of a local folder connection.
View and revoke your own Agent connection when the corresponding scopes are granted.
It cannot:
Read files on your computer.
Accept a local path.
Upload original files.
Run a local scan.
Run a sync.
Modify project data or widen sharing.
Confirm copyright, originality or final approval for you.
A local Agent + a folder you chose + local file capability
Runs a local program on this computer, so it can read folder metadata.
Only ever touches the one folder you selected in the dialog.
May send filenames, stages, sizes, and optional locally computed SHA-256 values; it does not send original file contents.
Requires the fixed-version package, which you can check against its SHA-256.
This is the advanced path for local files. It requires a local process and your explicit folder selection; Windows is the only guided platform today.
The local connector is currently limited to invited pilot accounts. If connect or pairing returns AGENT_PAIRING_DISABLED, stop; remote MCP above does not need this download.
Remote MCP host requirements
Your host must support remote MCP over Streamable HTTP and browser-based OAuth authorization with PKCE. Adding a URL in chat or pasting a prompt alone does not install or connect an MCP server. No Agent host has been certified by this release. Check your host's own MCP documentation; if it cannot complete this flow, do not treat a prompt as a substitute.
Host setup examples (field names, not screenshots)
Host UIs change frequently. These are starting points, not guaranteed labels; use your host's current MCP/connector documentation. The required capability is a remote MCP server URL plus browser OAuth authorization-code flow with PKCE. Never paste a token or password.
Claude Desktop: look for Settings → Connectors / Developer / MCP. If the version has a remote connector URL field, use the endpoint. Older/local-only builds use a JSON config under the mcpServers key; follow that host's documented bridge and do not invent a URL field.
Cursor: look for Settings → MCP → Add new MCP server. If it offers HTTP/URL or remote server fields, use the endpoint; if it only offers command/args, use its documented stdio bridge rather than pretending the URL is a command.
ChatGPT web / hosts without MCP settings: a chat prompt cannot add a remote MCP server. If the product has no MCP/connector configuration, stop and use a host that documents remote MCP support.
Generic JSON: field names vary by host: url, serverUrl, endpoint or a host-specific nested key. This schematic is not a universal schema: { "mcpServers": { "portraitpay": { "url": "https://portraitpayai.com/api/mcp" } } }
Remote MCP: copy this connection request
Your host must support adding a remote MCP server and completing browser OAuth. The prompt cannot configure a host that lacks those capabilities.
The host handles OAuth discovery, PKCE and browser authorization. Never paste a token.
Local connector: copy this task to your Agent
The Agent prepares the tool. You choose the folder, sign in, and approve each sensitive step.
Checking whether the local connector is enabled…
Local connector: steps you must approve
Choose the project folder in the Windows dialog.
Sign in and choose the matching project in your browser.
Read the preview, then approve or decline the local sync dialog.
Advanced users: manual installation and technical details
What is in the package?
A small PortraitPay CLI plus the official portable Node.js 22 runtime. It runs from your user folder; it does not install software system-wide or require administrator rights.
The package includes a sample/ folder with fictional project files so you can try the whole flow without pointing it at any real work.
Pilot only — download unavailable in this deploymentportraitpay-agent-cli-0.2.0.zip
The hash checks download integrity. It is not an independent signature.
This package is not an installer and not a security mechanism. It installs nothing on your system, and the SHA-256 only tells you whether your download arrived intact - it is not a certification of anything.
What you will be asked to approve
Choosing the one local project folder and creating the local state folder inside it 06_整理记录/.portraitpay/
Preview reads selected file bytes on this computer to calculate SHA-256. It does not upload file contents or originals.
A separate local dialog lists the filenames, stages, sizes, and any SHA-256 values to be sent before sync. Declining sends nothing.
The grant is limited to the chosen project/folder and expires after 24 hours. You can revoke it sooner in the project page.
Windows is the only guided path for the local connector today. Remote MCP needs no local install; this release has not certified any Agent platform.
