Connecting Seayora to Gemini Enterprise

How a Google Workspace administrator adds Seayora to Gemini Enterprise as a custom MCP server, and what is and is not possible on Google's other Gemini surfaces.

If your organisation runs Gemini Enterprise, an administrator can connect Seayora directly. It needs no approval from Google and none from us: you register our MCP server against your own tenant, your people sign in with their own Seayora accounts, and each of them sees exactly the properties, leases and jobs they would see on the website.

This is the one Gemini surface that is genuinely self-serve. Read "What about the Gemini app?" below before you start, because the answer there is different and it is better to know first.

Before you start

Gemini Enterprise, and an administrator account holding the Discovery Engine Editor role. The connection is made in the admin interface, not by an end user.
A Seayora account for each person who will use it. The connection does not create accounts and does not share one — each person authorises it individually and sees only their own portfolio.
Nothing to install, and no credential from us to paste. Seayora publishes its own OAuth configuration, so Gemini reads what it needs.

The address

https://seayora.com/mcp

Streamable HTTP, JSON-RPC 2.0. Gemini Enterprise supports Streamable HTTP only — the older SSE transport is deprecated there and is refused — which is what Seayora serves, so there is nothing to switch.

Adding it

In the Gemini Enterprise admin interface, add a custom MCP server data store.
Give it the address above as the server URL and choose Streamable HTTP as the transport.
Choose OAuth 2.0 for authentication. Seayora supports dynamic client registration, so there is no client id or secret for you to obtain — if the form insists on one, point it at https://seayora.com/.well-known/oauth-authorization-server and it will discover the endpoints itself.
Choose the permissions your organisation should be able to grant. They are the same permission list as everywhere else in Seayora; the Permissions reference article describes each one.
Save, then have one person connect and ask a question about their own portfolio to confirm it end to end.

What your people can then ask

Which units are behind on rent, and by how much.
What repairs are open across a building, and which have been waiting longest.
What a lease says, when it ends, and what notice is required.
What sales tax applies to a job, line by line, with the statute behind each decision.
Anything else the tools cover — the catalogue each person sees is already narrowed to the permissions they hold.

What it can change

By default, nothing directly. Most workspaces stage every write as a proposal that a person approves in Seayora, and the assistant is told plainly when that has happened so it cannot report a change as made. Publishing a listing is never automated on any setting. The Approvals article covers this in full.

What about the Gemini app?

The consumer Gemini app is a different product with a different connector model, and its connectors are arranged directly with Google rather than added by a developer — there is no public listing route, for us or for anyone else. So Seayora will not appear in a list inside the Gemini app, and that is not something either of us can change from this end.

If you use Gemini through the Antigravity or Gemini CLI tooling, you can point it at the address above the same way you would any other MCP server; it is the same endpoint and the same sign-in.

For everyone else, Claude and ChatGPT both connect in a few clicks — see Connecting Claude, ChatGPT or Your Own Agent.

Frequently asked questions

Does Google see our property data?

Only in the sense that the assistant reads it to answer a question, the same as any other connector. Seayora sends data only to the person who authorised the connection, scoped to what their own account can see, and every call is logged on our side. Google's handling of what passes through Gemini is governed by your agreement with Google.

Can one connection serve the whole company?

No, and deliberately. Each person authorises their own connection and sees their own portfolio. A single shared credential would mean everybody saw everything, which is not how permissions work anywhere else in Seayora.

Is this a different product from the API?

No. The MCP server and the REST API read the same data through the same permission checks. An assistant cannot see anything the API would have refused.

Related guides

Related features and guides

Connecting Claude, ChatGPT or Your Own Agent — Documentation. Step-by-step instructions for connecting Claude, ChatGPT, an MCP-capable agent framework, or plain HTTP software to your Seayora account.
Permissions Reference — Documentation. Every permission an assistant or API key can hold, what it unlocks, and which ones can change records — generated from the server.
Approvals: How an Assistant Proposes Changes — Documentation. Why a connected assistant usually proposes rather than performs, what the Approvals queue is, and the one action that can never be automated.
Single Sign-On (SSO) — Feature. Single sign-on with supported providers, so your team authenticates through your existing identity provider instead of another password.
Seayora vs Innago — Comparison. Seayora vs Innago, compared: Innago is free to landlords and recovers its cost from transaction and tenant fees; Seayora is free to start with published rates and adds a marketplace, maintenance network and accounting.