MCP & APImcp.remote-pro.ai

MCP tools reference

The Remote Pro Ai MCP server exposes 5 tools. 4 are public and read-only: search_talent, check_availability, estimate_squad_cost and get_security_docs. The fifth, request_proposal, creates a draft and requires explicit user confirmation. All 5 share the same input conventions, error codes, limits and versioning.

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.

The 5 MCP tools

ToolAnnotationsTypical next step
search_talentread-onlycheck_availability
check_availabilityread-onlyestimate_squad_cost
estimate_squad_costread-onlyrequest_proposal
get_security_docsread-onlyRequest access on the Trust Center
request_proposalcreates a draft; needs confirmationUser opens the magic link
Download OpenAPI

Public and authenticated use

Every tool works anonymously. With an OAuth token, the same tools become account-aware: estimate_squad_cost applies your contracted rates, check_availability includes profiles your organisation is holding, and request_proposal files the draft in Client OS instead of emailing a magic link.

Conventions

  • Dates are ISO 8601 (YYYY-MM-DD) and interpreted in the client's time zone when relevant.
  • Currencies are ISO 4217 codes: SAR, AED, USD or EUR. Amounts are decimal strings, never floats.
  • Seniority is one of mid, senior or lead.
  • Practice is one of ai_data, cybersecurity, cloud_complex_systems, game_development, mobile_web, design, marketing, business_development, sales.
  • Lists are paginated with an opaque cursor and next_cursor.
  • Every result includes structuredContent matching the output schema, plus a short text summary for hosts that only show text.

Error codes

CodeMeaningWhat to do
invalid_argumentAn input failed validationRead the message; it names the field
not_foundA profile_id or quote_id doesn't existSearch again or create a new estimate
quote_expiredThe quote_id is older than 30 daysCall estimate_squad_cost again
consent_requiredrequest_proposal called without user confirmationShow the summary and ask the user
unauthorizedThe action needs an OAuth tokenStart the OAuth flow
forbidden_scopeThe token lacks a required scopeReconnect with the scope
rate_limitedToo many requestsWait for Retry-After seconds
unavailableTemporary outageRetry with backoff; check status

Limits

  • Anonymous: 30 requests per minute and 1,000 per day per IP.
  • Authenticated: 120 requests per minute per organisation.
  • request_proposal: 5 per hour per email address.
  • Results per page: up to 25.

Versioning

Tool names are stable. Additive changes, like a new optional field, ship without notice in the changelog. Breaking changes ship as a new version (for example search_talent_v2) with at least 90 days' overlap before the old version is removed.

Frequently asked questions

4 of them: search_talent, check_availability, estimate_squad_cost and get_security_docs. They're annotated as read-only, so hosts can run them without asking the user each time. Only request_proposal creates anything, and it requires explicit user confirmation before the call. Some hosts may still ask before the first call, depending on their own settings.

Errors return a stable code, such as invalid_argument or quote_expired, plus a human-readable message naming the field or limit involved. Build your logic on the code and show the message to users. The table on this page lists every code and the recommended action.

Amounts are decimal strings with an ISO 4217 currency code, such as SAR or EUR, to avoid floating-point rounding. Estimates also include the VAT note and assumptions so assistants can explain the figure accurately. Convert amounts to numbers only for display, never for further calculation.

Not without warning. Additive changes are backward compatible. Breaking changes ship as a new versioned tool with at least 90 days' overlap, announced in the changelog and by email to registered OAuth clients. The old version keeps working until the published removal date, and the changelog gives a migration note for every breaking change.

You receive a rate_limited error and HTTP 429 with a Retry-After header. Wait that many seconds before retrying. If your use case needs higher limits, authenticate with OAuth or contact us with your expected volume. Use exponential backoff for retries.