FamRelay

Get started

Connect your assistant in a few minutes.

FamRelay has no app to install. You add it to the assistant you already use, sign in once, and from then on you just ask. The people you share with do the same on their side. Or start on your own: add it to two of your assistants and pass details between them.

Connector address https://api.famrelay.ai/mcp

Does your assistant ask for an API key instead of signing in? FamRelay supports that too. Create a key at api.famrelay.ai/account.

Before you start

Three things you’ll need.

An assistant that takes connectors

FamRelay connects through the Model Context Protocol (MCP), the open standard assistants use to add outside tools. If yours lets you add a “custom connector” or “MCP server” by address, it can use FamRelay.

A Google account

You sign in to FamRelay with Google. The email on that account is your FamRelay address: it’s how other people share with you.

Someone to share with, or a second assistant

Each person connects their own assistant, with their own sign-in. They don’t need the same assistant as you. You only need their email address. Or connect a second assistant of your own and pass details between the two.

Set it up

Four steps, done once.

After this, there’s nothing to open or check. Sharing and receiving both happen in your normal chat.

Setting this up for a partner or parent? Send them this page. Everyone signs in for themselves, so nobody holds anyone else’s access.
  1. Step 1 · Add the connector

    Give your assistant FamRelay’s address.

    In your assistant’s settings, find the place to add a custom connector and paste in this address. Call it “FamRelay”.

    https://api.famrelay.ai/mcp
    Where to find it in Claude
    1. Open Settings, then Connectors.
    2. Choose Add custom connector.
    3. Name it FamRelay and paste the address above.
    4. Choose Add, then Connect.

    Add it on the web or desktop app. Once it’s added, it’s available in the mobile app too.

    Where to find it in ChatGPT
    1. Open Settings, then Apps & Connectors.
    2. Under Advanced settings, turn on Developer mode. Custom connectors need it.
    3. Choose Create. Name it FamRelay and paste the address above as the MCP server URL.
    4. Leave authentication on OAuth, then create it.

    Custom connectors are set up on the web, and need a paid ChatGPT plan.

    Where to find it in Grok
    1. In the Grok app on your phone, open Settings, then Connectors.
    2. Choose Custom connector.
    3. Paste the address above.
    4. Complete the sign-in when Grok opens it.

    On a computer, the same thing is at grok.com/connectors. Once added, FamRelay also works by voice in a Tesla that’s signed in to the same Grok account, for asking and for sharing. FamRelay with Grok in a Tesla.

    Where to find it in Meta Muse

    Muse connects to FamRelay with OAuth sign-in, the same way as Claude and ChatGPT. You don’t need an API key. Paste this into a chat with Muse and it adds the connector for you:

    Can you add a custom connector called FamRelay, an MCP server at https://api.famrelay.ai/mcp? It supports OAuth sign-in (OAuth 2.1 with dynamic client registration), so connect it with OAuth, not an API key. If an OAuth client ID is needed, it's meta-ai, with no client secret. Use it to send facts to my other AI assistants and to my family. Also check it periodically for updates from my other assistants and my family, remember the facts, and let me know about them.

    Muse then shows a Connect button. Choose it, and the FamRelay sign-in page opens: choose Continue with Google, then Allow, as in step 2. You’re sent back to Muse, connected.

    The Muse phone app may still show a box asking for a client ID: type meta-ai and leave the secret empty. If Muse says FamRelay doesn’t support OAuth, or asks for an API key, tell it: “FamRelay supports OAuth. Its sign-in details are published at https://api.famrelay.ai/.well-known/oauth-authorization-server.” Whether Muse can check on a schedule depends on your Muse plan. If it can’t, just ask it: “Anything new on FamRelay?”

    If it asks for a client ID or an API key

    FamRelay uses OAuth sign-in. Claude, ChatGPT, Grok and Meta Muse all connect this way: the assistant registers itself, opens the FamRelay sign-in page, and you choose Allow. No key, client ID or secret is needed.

    Asked for a client ID? Type meta-ai, and leave any client secret box empty. Your email address won’t work there. The FamRelay sign-in page then opens, and you carry on with step 2.

    Asked for an API key? First look for an OAuth option in the connector settings and choose it. Only if the assistant has no OAuth option at all, give it an access key instead:

    1. Open api.famrelay.ai/account and sign in with Google.
    2. Under Create an access key, name the assistant and choose Create key.
    3. Copy the key. It’s shown only once.
    4. Back in your assistant, paste it into the API Key box and add the connector. You can skip step 2 below.

    Paste the key only into the assistant’s secure key box, never into the chat itself. Treat it like a password: it works for a year, or until you disconnect it on the same page.

    Another assistant

    Look in its settings for “connectors”, “integrations”, “tools” or “MCP servers”, and add a remote server with the address above. Sign-in is automatic: FamRelay tells the assistant how to start it. If your assistant can’t add connectors yet, tell us which one you use.

    Sign-in is OAuth. FamRelay supports OAuth 2.1 sign-in for every assistant, including Claude, ChatGPT, Grok and Meta Muse. Choose OAuth whenever the assistant offers it. Access keys from api.famrelay.ai/account are an optional alternative, only for assistants whose connector settings have no OAuth option.

    Menu names move around as assistants update. If yours looks different, search its help for “custom connector”.

    Using more than one assistant? Add FamRelay to each one and sign in with the same Google account.

  2. Step 2 · Sign in and allow

    Tell FamRelay it’s really you.

    Your assistant opens a FamRelay page. Choose Continue with Google, check the email it shows, then choose Allow. You’re sent straight back to your assistant.

    What you’re allowing

    • Prepare shares for you. Nothing is sent until you say yes in the chat.
    • Read what people have shared with you, and let them see when it was read.

    That’s all. FamRelay can’t see your conversations, your assistant’s memory or your Google account beyond your name and email.

  3. Step 3 · Add your people

    Tell your assistant who’s who.

    Save the people you share with by name, so you can say “Sam” instead of an email address. Use the email they sign in to FamRelay with.

    Save Sam as a FamRelay contact. Her email is sam@example.com.
    Saved. You can share with Sam by name from now on.

    Only passing details between your own assistants? Skip this step. There’s nobody to add.

  4. Step 4 · Share something

    Try it with one small detail.

    Ask in your own words. Your assistant shows you exactly what it would send, to whom, and until when. Nothing leaves until you say yes.

    Let Sam know the plumber’s coming tomorrow between 8 and 10.
    Here’s what I’d share with Sam: Plumber visit, tomorrow 8–10 AM, fixing the hot water. Access ends tomorrow evening. Send it?
    SSam’s assistant · once Sam has connected too
    Has anyone shared anything with me?
    Alex shared a plumber visit: tomorrow, 8–10 AM, to fix the hot water.

    On your own? Try “Send this to my other assistants”, then ask the second one “What did I send myself on FamRelay?”

    Examples are illustrative. Your assistant’s exact wording will differ.

Everyday use

There are no commands. Just ask.

These are examples, not magic words. If your assistant doesn’t pick it up, mention FamRelay by name: “Use FamRelay to let Sam know…”

Share

Send only the details someone needs.

Let Sam know about this invite.
Send Mum and Dad my flight times, until I land.

Receive

See what others have shared with you.

What’s been shared with me?
Anything new on FamRelay?

Update

Plans change. Recipients get the new version.

The pickup’s moved to 3:15. Update what I shared with Nana Jo.

Stop sharing

With one person, or everyone.

Stop sharing the holiday house details with Riley.

Check the record

What you’ve shared, and who has read it.

What am I sharing right now?
Has Sam seen the plumber details?

Manage your people

Add, list or remove saved contacts.

Who are my FamRelay contacts?
Remove Riley from my contacts.

Between your own assistants

Send a detail from one assistant, pick it up in another. Connect both with the same Google account. It works by voice in the car too, with Grok in a Tesla.

Send this trip plan to my other assistants.
What did I send myself on FamRelay?

Good to know

How FamRelay behaves today.

FamRelay is live and still early. Here’s exactly what to expect, including the parts that aren’t built yet.

Arrival

How does the other person find out?

Their assistant shows it the next time they ask what’s been shared, or on a scheduled check-in if their assistant supports those. FamRelay doesn’t send notifications yet, so for anything urgent, tell them it’s there.

Addresses

What if they haven’t signed up yet?

You can still share. The item waits, encrypted, and is there when they connect an assistant and sign in with that email. It must be the email on their Google account, so check which one they use.

What moves

What can a share contain?

A title, up to 20 short details (such as “Time: Sunday 2:00 PM”) and an optional note. Files and images aren’t sent: your assistant reads the flyer and shares the facts you approve.

Lifespan

How long does a share last?

Until the end date you choose, up to 90 days. If you don’t pick one, it’s 30 days. After that it’s gone from FamRelay. You can stop sharing sooner at any time.

People

Who can I share with, and what do they see?

Up to 10 people per share. Each one sees the details and that it came from you. They don’t see who else received it. You can see when each person’s assistant read it.

Your own assistants

Can I send something to my other assistants?

Yes. Ask one assistant to send it to your other assistants, and approve it as usual. Every assistant connected to your account can then read it; you can’t pick just one yet. The others show it when you ask, not on their own. The same limits apply: up to 90 days, and nothing from the off-limits list.

Off limits

What shouldn’t I share?

FamRelay refuses passwords, PINs, access codes, card numbers and Social Security numbers. Please also keep health, financial and children’s sensitive records out of it. It’s built for everyday logistics.

Leaving

How do I disconnect or delete my data?

See every connected assistant, and disconnect any of them, at api.famrelay.ai/account. Then remove FamRelay from that assistant’s connector settings. To have your FamRelay data deleted, email privacy@famrelay.ai from the address you signed in with.

Cost

What does it cost?

Nothing at the moment. If that changes, we’ll say so clearly before you’re asked to pay for anything.

Your assistant is part of the picture. FamRelay keeps what you share encrypted and only releases it to the people you chose. Your assistant handles the details on the way in and out, under its own provider’s privacy terms. More on security.

Troubleshooting

If something doesn’t work.

The sign-in page says the link has expired

Sign-in links are short-lived and work once. Go back to your assistant’s connector settings and choose Connect again.

My assistant asks for a client ID, an API key or a token

FamRelay uses OAuth sign-in, so first choose OAuth in the connector settings if the assistant offers it. If it asks for a client ID, type meta-ai, not your email address, and leave the secret empty. If the assistant says FamRelay doesn’t support OAuth, that’s a mistake: its OAuth details are published at https://api.famrelay.ai/.well-known/oauth-authorization-server. Only an assistant with no OAuth option at all needs an access key: create one at api.famrelay.ai/account and paste it where the assistant asks for the key. There’s nothing to set up on a server, whatever the assistant suggests.

Meta Muse shows an error when I add FamRelay

Muse connects with OAuth sign-in, so choose Connect in Muse, sign in with Google and choose Allow. If Muse tells you FamRelay doesn’t support OAuth, tell it that it does, and point it at https://api.famrelay.ai/.well-known/oauth-authorization-server. If the Muse phone app says something went wrong after you sign in, add FamRelay from the website version of Muse instead: open muse.ai in a browser, sign in, and connect it there. Once it’s added, it’s available in the app too. Still stuck? Email hello@famrelay.ai. An access key from api.famrelay.ai/account also works as a stopgap.

The Google sign-in window doesn’t appear

It opens as a pop-up. Allow pop-ups for api.famrelay.ai in your browser, then choose Continue with Google again.

My assistant doesn’t use FamRelay when I ask

Check the connector is switched on for the chat you’re in: some assistants make you enable it per conversation. Then say it by name: “Use FamRelay to let Sam know…” Your assistant may also ask permission the first time it uses each FamRelay action.

The other person can’t see what I shared

Three things to check. Have they connected their own assistant? Did they sign in with the same email you shared to? And have they asked their assistant what’s been shared with them? It won’t announce it unprompted.

My other assistant can’t see what I sent myself

Check that both assistants are signed in to FamRelay with the same Google account: api.famrelay.ai/account lists every assistant on yours. Then ask the second one directly: “What did I send myself on FamRelay?” It won’t bring it up unprompted.

My assistant says it can’t share something

FamRelay refuses details that look like passwords, codes, card numbers or Social Security numbers. Remove that detail and try again. A draft you didn’t confirm within 30 minutes also expires: just ask again.

My assistant says it needs to reconnect

A connection that hasn’t been used for 30 days signs itself out. Choose Connect in your assistant’s connector settings and sign in again. Nothing you’ve shared is lost.

I don’t have a Google account

Google is the only sign-in for now. Other ways to sign in are planned. Email hello@famrelay.ai and we’ll let you know when they’re ready.

Still stuck? Email hello@famrelay.ai and a person will help.

Technical detailsFor developers and anyone connecting a custom client
  • Endpoint. https://api.famrelay.ai/mcp, MCP over Streamable HTTP (stateless, JSON responses).
  • Authorisation. OAuth 2.1 with PKCE (S256) and dynamic client registration, for every client, Meta Muse included. Authorization endpoint https://api.famrelay.ai/authorize, token endpoint https://api.famrelay.ai/token, registration https://api.famrelay.ai/register. Metadata: /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource on api.famrelay.ai. Public clients use token auth method none.
  • Scopes. famrelay.share to prepare and send, famrelay.receive to read what’s shared with you.
  • Tokens. Access tokens last an hour. Refresh tokens last 30 days and rotate on every use.
  • Access keys. Optional, only for clients that can’t do OAuth at all: create a key at api.famrelay.ai/account and send it as Authorization: Bearer or X-API-Key. Keys last a year and are stored only as hashes.
  • Limits. 10 recipients and 20 details per share, 100 sends per person per day.

Early access

Tell us how it went.

FamRelay is new, and what you run into shapes what we build next. Write to us, or join the pilot to work with us more closely.

Send feedback Join the pilot