Yes. The Gemini CLI supports MCP servers through the gemini mcp add command, the same way Claude Code does, so the local OwnerRez MCP server you build works with Gemini with no changes. Point it at the same index.js and ask Gemini about your bookings, properties, guests, and payments.
What works today
The Gemini CLI reads MCP servers from ~/.gemini/settings.json and supports both local (stdio) and remote (HTTP) servers. Because the OwnerRez server in our guide runs locally over stdio, it drops straight into Gemini's config, no hosting or rewriting required.
As with Claude, the server is read-only by default, so Gemini can read your OwnerRez data but cannot change anything, and your account email and Personal Access Token stay in environment variables on your own machine.
The hosted API route
If you would rather call an API than run and maintain a server, there is a hosted middle path: the RapidEye API exposes OwnerRez as a hosted connector, so the credential handling and token care above happen on our side and your assistant or script calls one consistent surface. The catalogue is machine-readable, which means an AI agent can discover it and hand you the next step on its own.