The new way to do real estate. Relotiva is a real-estate CRM with an AI assistant built in, and it runs as an MCP server, so the AI assistant you already use can read your pipeline, add notes and contacts, and set up your account with you.
MCP server URL
https://relotiva.com/api/connector/mcp
Pick your AI
Use the assistant you already pay for and already talk to. It works on your own Relotiva data, with your permission, and keeps its own name. Prefer not to? Tiva, the assistant built into Relotiva, does the same things inside the app.
Claude
Tested end to end
In Claude (web, desktop or phone), open Customize, then Connectors. Older versions call it Settings, then Connectors.
Choose Add custom connector. Name it Relotiva and paste the server URL.
Leave the OAuth Client ID and Secret empty. Relotiva registers Claude by itself.
Click Connect, sign in to Relotiva, and choose what Claude may do.
On a Team or Enterprise plan, an owner adds the connector first under Organization settings, Connectors. Then you connect it yourself.
The Free plan allows one custom connector.
ChatGPT
Not tested yet
On chatgpt.com, open Plugins (chatgpt.com/plugins), press +, then Add custom MCP server. Some plans call this Apps or Connectors and ask you to turn on developer mode first.
Name it Relotiva and paste the server URL under Connection.
Choose OAuth for authentication, read the warning, and create it.
ChatGPT opens the Relotiva sign-in and consent screen.
OpenAI offers custom MCP servers on some plans only (Business, Enterprise and Edu for certain; other plans vary). If you do not see the option, your plan does not have it yet.
Gemini
Not tested yet
If your Gemini app offers custom apps: on gemini.google.com open Settings, then Connected apps, then Add a custom app, and paste the server URL.
Sign in to Relotiva when it asks, and choose what Gemini may do.
Using the Gemini CLI instead? Add the server URL as "httpUrl" under mcpServers in settings.json. It finds the Relotiva sign-in by itself.
Custom apps are only on some Gemini accounts, and we could not confirm which from Google's own help pages.
Gemini Enterprise asks for an OAuth client secret. Relotiva does not issue those yet, so Gemini Enterprise cannot sign in today.
Other AI agent (developer)
Any MCP client
Point any MCP client that speaks Streamable HTTP at the server URL. If it can open a sign-in page, it signs in like Claude does.
If it cannot open a sign-in page (an API script, a local model, a server job), create a personal key and send it as Authorization: Bearer <key>.
Keep the key in the app's key setting or an environment variable. Never paste it into a chat.
A command-line agent that listens on localhost for the sign-in redirect can fail when the browser cannot reach it. Use a personal key there.
How it works
01
Add Relotiva as a connector
In Claude, open Customize → Connectors → Add custom connector and paste the server URL above. ChatGPT, Gemini and other MCP clients have their own way to add a custom MCP server with that URL; see Pick your AI.
02
Sign in with your email
Your AI client opens a Relotiva sign-in page. Sign in with your Relotiva account. New to Relotiva? Pick a plan at relotiva.com first: 14 days free, card required.
03
Approve what your agent may do
The consent screen lists what your agent is asking for. Reading your data comes with every connection; adding to Relotiva on your behalf and helping finish your account setup are each a separate checkbox. Untick one and it is not given.
04
Ask your agent to set you up
Back in your AI client, say “set up my Relotiva account”. It checks what is missing and walks you through the rest.
Things to ask
“Who in my pipeline is going cold?”
“Show me my hot leads and why they're hot.”
“Add a note to Riley: wants a 3-bed under 1.4M, flexible on timing.”
“Move the Parks to Offer.”
“What's on my calendar this week?”
“Draft a follow-up to Ana about Saturday's open house.”
“Set up my Relotiva account.”
Drafts land in Gmail or in Relotiva for you to read and send yourself. Your AI can never press send.
Get your day without asking
Relotiva can’t message your AI on its own; your AI comes to Relotiva. If your assistant can run scheduled tasks, set one up once: “Every weekday at 7:30 AM, ask Relotiva what I need to know today and tell me.” It brings you the same four things your Relotiva home shows, with a link for each.
See and undo what it did
Every note, call, stage move or contact your AI adds is marked Done by your AI, with the app or key name, on that contact’s timeline, so you can always tell its work from yours. The label is set by Relotiva, not by the AI, so it cannot be left off.
In Relotiva, Connectors lists every AI you connected by signing in or with a personal key, with what it may do. Disconnect any of them in one click, and it loses access immediately.
What stays with you
Connecting Gmail or Google Calendar takes one click on Google’s own consent screen. Your agent hands you the link; Google only accepts that approval from you. Nothing else needs the Relotiva app.
Your agent can never send an email or a text message, and can never delete anything. You can disconnect it at any time.
For agents
MCP server: https://relotiva.com/api/connector/mcp
Auth: OAuth 2.1 with PKCE. Discovery via the WWW-Authenticate header on a 401,
or https://relotiva.com/.well-known/oauth-protected-resource/api/connector/mcp
Scopes:
crm.read - Read your Relotiva data. Contacts, lead scores, pipeline totals, email performance, bounces, your Google Calendar events for the next few weeks, and which account setup steps you have finished.
crm.write - Add to Relotiva on your behalf. Add a contact, a note or a logged call, update a contact's details or pipeline stage, put an event on your own Google Calendar, save a Gmail draft, and send a request you have confirmed to the Relotiva team. It can never send email or SMS, and can never delete anything.
crm.onboarding - Help finish your account setup. Save your business mailing address (the one the law requires in your email footer) if none is on file yet. It cannot change an address you already have, connect your email, import contacts or send anything: for those it gives you the link to do it yourself.
offline_access - Stay connected. Keep working without asking you to sign in again every hour.
Request crm.onboarding to help a new user finish setup. Onboarding tools:
relotiva_onboarding_status
relotiva_onboarding_next_step
relotiva_onboarding_set_address
A new person picks a plan at relotiva.com/signup first (14 days free, card required).
Gmail and Google Calendar need the user's own click on Google's consent screen.
Full agent guide: https://relotiva.com/agents
For developers: personal keys
For apps that can’t open a sign-in page: the OpenAI or Gemini APIs, local models, your own scripts. Anything that can sign in should sign in instead.
In Relotiva, open Connectors and choose Create a personal key.
Name it after the app, choose read only or read and write, and choose 30, 90 or 365 days.
Copy the key. It is shown once; Relotiva stores only a fingerprint of it. Up to 10 keys can be live at a time.
Send it as a bearer token to the server URL above. Revoke it on the same page and it stops working on the next request.
# export RELOTIVA_KEY=rlv_pat_... (set once, so the key stays out of your history)
curl https://relotiva.com/api/connector/mcp \
-H "Authorization: Bearer $RELOTIVA_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
A read-only key sees only the read tools. Writes made with a key carry the same “Done by your AI” mark, with the key’s name. Treat a key like a password: put it in the app’s key setting or an environment variable, and never in a chat message (including to your own AI), a shared doc or a code repository.