MCP & APImcp.remote-pro.ai

MCP App: interactive squad builder

The Remote Pro Ai MCP App is an interactive squad builder that renders inside AI assistants that support MCP Apps. Search results appear as team cards, and a live quote updates as the user changes levels or team size. It covers 3 views (team cards, quote and summary) and falls back to text everywhere else.

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.

MCP App team cards and a live quote

  • Team card: headline · seniority · experience_band / chips top_skills / Available availability / buttons Add to squad · Remove
  • Quote panel: Monthly estimate: monthly_total currency · excl. VAT / Quote quote_id · valid until valid_until / buttons Change level · Get a proposal

n engineers · earliest start date · lane lane

Where it works

Hosts that implement the MCP Apps extension, including Claude and ChatGPT. The app is declared as a ui:// resource on each tool result; hosts that don't support it ignore it and show the text result.

State lives in the quote_id

The app keeps no client-side state worth losing. Every change calls estimate_squad_cost and returns a new quote_id, so the squad can be reopened later, shared or passed to request_proposal. Quote IDs stay valid for 30 days.

Text fallback

Without MCP Apps support, the same data returns as a compact text table (role, level, start, monthly estimate) with a deep link that opens the squad on remote-pro.ai with the quote pre-loaded.

  • Fallback link text: Open this squad on remote-pro.ai

Security and data handling

  • Runs in the host's sandboxed frame with a strict content security policy and no third-party scripts.
  • Shows anonymised profiles only; no names, photos or contact details.
  • Talks only to mcp.remote-pro.ai through the host's tool-call bridge.
  • "Get a proposal" always routes through request_proposal, which needs the user's confirmation.

Example session

  1. 1User: "I need a small team to build an Arabic RAG assistant on Azure, starting next month."
  2. 2The assistant calls search_talent; 4 team cards render: Lead AI engineer, Senior ML engineer, Senior data engineer, Mid full-stack engineer.
  3. 3The user removes the full-stack card and changes the data engineer to Mid. The quote panel updates with a new quote_id.
  4. 4The user selects Get a proposal. The assistant shows the confirmation summary; the user agrees; request_proposal sends the magic link.
Read the integration guide

Frequently asked questions

It's an interactive interface that appears inside supporting AI assistants when they use the Remote Pro Ai MCP server. Instead of a list of text, users see team cards and a live quote they can adjust, then move to a proposal without leaving the chat.

Hosts that support the MCP Apps extension, including Claude and ChatGPT. In hosts without it, the same tools return a text table and a deep link to remote-pro.ai, so every user can complete the same journey. No setup is needed beyond connecting the server.

No meaningful state. Every change creates a new quote_id through estimate_squad_cost, and the quote_id is the state. That's why a squad can be reopened, shared or turned into a proposal for up to 30 days. Closing the chat loses nothing.

No. It shows the same anonymised profiles as search_talent, with no names, photos or contact details. Personal details are shared only in the booking flow on remote-pro.ai after an NDA and an accepted interview request. The app never asks for them.

No. The Get a proposal button routes through request_proposal, which requires the assistant to show a summary and receive the user's explicit confirmation. Nothing is booked, signed or charged from inside the app. Booking, signature and payment happen only on remote-pro.ai in the user's own session.