Register an OAuth client
- Discovery:
https://mcp.remote-pro.ai/.well-known/oauth-protected-resourcepoints to the authorisation server metadata athttps://mcp.remote-pro.ai/.well-known/oauth-authorization-server. - Registration endpoint:
POST https://mcp.remote-pro.ai/oauth/register(RFC 7591). Send client_name, redirect_uris and the scopes you need.
Prefer a fixed client? Admins can create one in Client OS under Settings › Integrations.
{
"client_name": "Acme Procurement Assistant",
"redirect_uris": [
"https://assistant.acme.example/callback"
],
"grant_types": [
"authorization_code",
"refresh_token"
],
"token_endpoint_auth_method": "none",
"scope": "proposals:read proposals:write"
}Scopes
| Scope | Grants |
|---|---|
proposals:read | Read your organisation's proposals and quotes |
proposals:write | Create draft proposals in Client OS |
squads:read | Read squads, roster and engineer status |
timesheets:read | Read submitted and approved timesheets |
invoices:read | Read invoices, credits and e-invoice files |
documents:read | Read contract and certificate metadata |
There are no write scopes for timesheets, invoices or contracts. Approvals, payments and signatures always happen in Client OS. · note More account tools are planned for 2027.
The flow
- 1Generate a code_verifier and its S256 code_challenge.
- 2Send the user to /oauth/authorize with client_id, redirect_uri, scope, state, code_challenge and code_challenge_method=S256.
- 3The user signs in to Client OS (SSO, passkey or email code) and approves the scopes.
- 4Exchange the code at /oauth/token with the code_verifier.
- 5Call the MCP server or REST API with Authorization: Bearer access_token.
PKCE is required for every client. The implicit flow and plain code challenges aren't supported.
Tokens
- Access tokens: 60 minutes.
- Refresh tokens: 30 days, rotated on every use. Reusing an old refresh token revokes the whole chain.
- Tokens are bound to one organisation. Users with several organisations authorise each separately.
Revocation
- Endpoint:
POST https://mcp.remote-pro.ai/oauth/revoke(RFC 7009).
Users and admins can also revoke any connected assistant in Client OS under Settings › Integrations. Revocation takes effect immediately.
What users see
client_name wants to access org_name
This lets client_name act for you in Remote Pro Ai. It can:
- Scope lines: See your proposals and quotes · Create draft proposals · See your squads and engineers · See timesheets · See invoices · See contract details
It can't approve, pay or sign anything. You can revoke access at any time in Settings › Integrations.
The screen follows the user's language setting. The Arabic version is right-to-left with the same scope lines.