Open Settings → Connect your AI, choose New connection, name it, select scopes, and choose a 7-, 30-, or 90-day expiration. The token appears once. Copy it into a client supporting a remote MCP server and an Authorization header. Hosted assistants need a reachable HTTPS application origin; localhost is reachable only from the same computer.
{
"mcpServers": {
"ralti": {
"url": "https://app.your-domain.example/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_PERSONAL_CONNECTION_TOKEN"
}
}
}
}| Scope | Allowed behavior |
|---|---|
| Sheets and records | Discover schemas, search/read records, follow links, and calculate supported aggregates |
| Your connected inboxes | Read permitted synced Inbox/Sent messages and bounded conversations |
| Propose changes for review | Validate or save draft commands for normal Ralti review |
Connections belong to one user and one workspace. Neither tool arguments nor workspace headers can move a token into another workspace. Current membership, role, mailbox permissions, and connection scopes are checked when tools run and before results return. Only a token digest is stored; revoke a lost token and create another. Revocation also applies to checks before an active tool returns data.
Changes remain reviewable#
validate_changes checks a draft without saving it. propose_changes stores a completed request in Ask Ralti and returns a reviewUrl. Both require the current baseRevision; proposals also use an idempotencyKey to prevent duplicate deliveries. Open the review URL to inspect and apply the draft through Ralti’s ordinary revision checks and undo behavior. MCP tools do not apply operations, run workflows, send email, or read attachments.
Follow continuation cursors and coverage flags for complete reviews. Search rankings are bounded candidates, and record or email text remains untrusted content rather than instructions to the assistant.