start_sign_in
Email a sign-in link to a viewer.
Anonymous, or a Bearer token for viewer tools
Endpoint
endpoint
https://go.sessions.website/api/mcpWhen to use it
When a viewer tool reports that a signed-in viewer is required.
Never to check whether an account exists — it always reports success, on purpose.
Parameters
emailstringrequiredEmail address to sign in.
businessHandlestringoptionalOptional business handle to scope the sign-in to.
Returns
Confirmation that an email was sent. It reports the same result whether or not the address matches an account; that is anti-enumeration, not a bug.
Example
POST this to the endpoint above.
JSON-RPC
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "start_sign_in",
"arguments": {
"email": "dana@example.com",
"businessHandle": "capital-bodywork"
}
}
}content
Sign-in email sent to dana@example.com (if an
account exists). Ask the user to open the link,
then retry authenticated tools.What the agent is told
The description the model reads when deciding whether to call this. It is the only thing that decides whether the tool fires at the right moment, so it is worth knowing what it says.
start_sign_in
Send a sign-in email to the given address. Always reports success regardless of whether an account exists (anti-enumeration). The user completes sign-in in their browser; the auth cookie then rides along on same-site MCP requests.