Commerce
setClientPortalPath
Set Client Portal Path
Put a client's portal on the Space's custom domain at /labs/client/<uniqueid>, e.g.
Ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "put Kurt's portal on teka.ai", and it calls setClientPortalPath.
Example call
The MCP tools/call params, with the required arguments only.
{
"arguments": {
"appId": "<appId>",
"domain": "<domain>"
},
"name": "setClientPortalPath"
}Arguments
appIdstringrequiredThe client portal's Studio app idclientEmailstringoptionalThe client the path is for. Omit when the portal admits one clientconfirmbooleanoptionalMust be true: the owner agreed to change the domaindomainstringrequiredThe Space's verified custom domain, e.g. yourstudio.com
Returns
The uniqueid is a public token minted once per client and kept, so calling again returns the same path; it is never a Cloud id or an email.
Declared limits
domain: maximum length 253
Ask for it
The Cloud routes these requests to this verb.
- put Kurt's portal on teka.ai
- give the client a teka.ai link
- set the portal path
Pair it with
The verbs that finish the job.
Questions
What does setClientPortalPath do?
Put a client's portal on the Space's custom domain at /labs/client/<uniqueid>, e.g. It is one of the tools The Cloud MCP server gives every connected AI.
How do I use setClientPortalPath from Claude or ChatGPT?
Connect your AI to The Cloud at https://mcp.thecloud.so/mcp and sign in once. Then ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "put Kurt's portal on teka.ai", and it calls setClientPortalPath.
Is setClientPortalPath safe to let an AI call?
setClientPortalPath widens who can see or receive something, so the owner approves every call explicitly. An AI cannot approve it for itself.
Connect
One endpoint gives your AI this tool and every other one: connect Claude, ChatGPT, Cursor or Gemini, read what The Cloud is, or see pricing.