MCP & APImcp.remote-pro.ai

OAuth 2.1 authorisation

Remote Pro Ai uses OAuth 2.1 to authorise account access for MCP tools and the REST API. Clients register dynamically, run the authorisation code flow with PKCE, and receive access tokens that last 60 minutes. Users approve each scope on a consent screen in English or Arabic and can revoke access at any time.

Developer preview until live: the MCP server and the platform API are not running yet. Tools, endpoints and examples on these pages describe the interface we are building; a call made today returns nothing.

Register an OAuth client

  • Discovery: https://mcp.remote-pro.ai/.well-known/oauth-protected-resource points to the authorisation server metadata at https://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.

POST /oauth/register
{
  "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

ScopeGrants
proposals:readRead your organisation's proposals and quotes
proposals:writeCreate draft proposals in Client OS
squads:readRead squads, roster and engineer status
timesheets:readRead submitted and approved timesheets
invoices:readRead invoices, credits and e-invoice files
documents:readRead 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

  1. 1Generate a code_verifier and its S256 code_challenge.
  2. 2Send the user to /oauth/authorize with client_id, redirect_uri, scope, state, code_challenge and code_challenge_method=S256.
  3. 3The user signs in to Client OS (SSO, passkey or email code) and approves the scopes.
  4. 4Exchange the code at /oauth/token with the code_verifier.
  5. 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.

ClientUserRemote Pro Aicode_verifier → S256 code_challenge/oauth/authorizeSSO · passkey · email code → approve scopesredirect_uri?code=…&state=…POST /oauth/token + code_verifieraccess_token (60 min) + refresh_tokenAuthorization: Bearer <access_token>

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.

Frequently asked questions

Not for the 5 public tools. OAuth is needed only for account features: estimates at your contracted rates, proposals filed in Client OS, and the REST API for squads, timesheets, invoices and documents. Users approve each scope on a consent screen.

Authorisation code with PKCE (S256), as required by OAuth 2.1, plus refresh tokens. The implicit flow, the password grant and plain PKCE challenges aren't supported. Clients can register dynamically under RFC 7591 or be created by an admin in Client OS.

Access tokens last 60 minutes. Refresh tokens last 30 days and rotate on every use; if an old refresh token is reused, the whole token chain is revoked to protect the account. When a refresh token expires, the user signs in and approves the scopes again. Admins can revoke tokens at any time in Client OS.

No. Scopes are read-only except proposals:write, which creates drafts. Approvals, payments and signatures always happen in Client OS with the user's own session and, where required, a second-factor check. Even with every scope approved, an assistant can only read account data and create draft proposals for a person to review.

Any Admin can revoke it in Client OS under Settings › Integrations, and the user who authorised it can too. Developers can call the revocation endpoint. Revocation is immediate and the assistant must ask the user to approve again to reconnect.