MCP
MCP connector setup
WPORT ships two remote MCP servers. Once added to Claude or ChatGPT, you can ask in chat for your resumes, your company's jobs, or your talent pool — without leaving the conversation or writing any code.
No API key required. You only paste a URL — leave token / header / client secret empty and the platform completes the OAuth flow itself.
① Pick a line
Choose by the identity you need, or add both — they are two independent connectors with separate authorizations.
| Line | URL | What you get |
|---|---|---|
| Job seeker | https://mcp.wport.me/personal | 8 read-only tools: resumes, public jobs, authorized connections |
| Employer | https://mcp.wport.me/enterprise | 11 read-only tools: jobs, talent pool, campaigns, company, API keys, usage |
② What's the same on all four platforms
- Paste the URL only; leave every other field empty — no key, secret or header.
- Hit connect → you're sent to wport.me to sign in (redirects to /auth if needed) → the consent page lists exactly what's being granted → you press Approve → it returns automatically and the connector shows as connected.
- Every tool is read-only. It cannot edit resumes, submit applications, touch jobs / talent pool / API keys, or revoke your sign-in sessions.
- Set it up once per account. The connector is bound to your Claude / ChatGPT account, not a device — after adding it on the web, the desktop app and other browsers pick up the same connector and share one authorization.
- Access tokens are refreshed by the platform automatically; revocation takes effect immediately (every call is verified against the backend, never cached).
③ Claude web (claude.ai)
Settings → Connectors → Add custom connector → paste the URL → Connect.
Three OAuth client options are offered; pick “Use Anthropic's hosted client metadata” — the UI marks it Recommended and Detected, and it needs no extra fields.
④ Claude desktop
Nothing to configure. A connector added on claude.ai shows up in the desktop app and shares the same authorization — not a separate one. Consequently, revoking it signs out both web and desktop at once.
⑤ ChatGPT web (chatgpt.com)
Prerequisites: a Plus / Pro (or higher) plan with developer mode enabled — otherwise there is no entry point for custom MCP.
Path (ChatGPT calls these “apps”, not “connectors”): Apps → Browse directory → “New” at top right → “Create MCP app”.
The dialog needs two fields: a name (your choice) and the server URL. Leave authentication on the default OAuth and do not touch “Advanced OAuth settings” — let the platform handle discovery. Tick the required risk acknowledgement to enable “Create”, then press Continue to authorize.
⑥ ChatGPT desktop
Nothing to configure — connectors added on the web appear under Apps → Installed. Note the desktop app has two modes (ChatGPT / Codex) in the top-left; MCP tools only work in ChatGPT mode.
Command-line tools such as Codex CLI are not supported at this time.
FAQ
I connected earlier; new tools were added but calling them says “insufficient permission”.
The scope granted at authorization time is frozen into that grant. Later additions on the WPORT side are not back-filled into existing connections. The only way to get them: remove the connector on the platform and connect again, going through consent afresh.
After reconnecting, the old grant is still alive — revoke it as described in the last question.
company_view keeps returning 403 and reconnecting doesn't help.
The scope behind company_view is only issued to OWNER / ADMIN roles. A JOB_MANAGER is blocked twice: consent never issues it, and the backend rejects the call anyway.
The fix takes both steps: first have an OWNER / ADMIN change your role, then remove the connector and reconnect. Scope is frozen into the grant, so a role change alone does nothing.
Does pressing Disconnect in Claude / ChatGPT revoke the authorization?
No. Disconnect only removes the connection on the platform's side; the grant on WPORT remains active. To actually revoke it, use the CLI:
# Check which account the CLI is currently signed in as
wport whoami
# Not the account your MCP connector uses? Sign in again (--force is required
# once you are already logged in, otherwise the command does nothing)
wport login --force
# Find that connection's enc_id and revoke only that one
wport sessions list
wport sessions revoke <enc_id>The list shows only device names and timestamps — it does not label job-seeker vs employer grants, so match by authorization time before revoking. If you revoke the wrong one, just reconnect.
The wport login here is the job-seeker OAuth flow, not wport enterprise login (that one uses an API key and has no sessions command). If an enterprise account cannot sign in with it, or the grant does not appear in the list, contact the platform to have it revoked.
Don't reach for wport sessions revoke --all-others to remove a single connector — it revokes every connection on the account except the CLI you're running from, including your other MCP connector and CLI sign-ins on other devices.