Connect Spine to Gemini

Check availability first

Google currently requires a personal Google Account, age 18 or over, location in the US, English and Keep Activity enabled for custom apps. Work and school accounts are not supported by this feature. You add the app on the web; after connection, it can be used on web and mobile.

These restrictions come from Google’s custom app instructions. Availability and interface labels can change. This is a documented client path, not a completed test of the new Spine service.

Add the connection

1. Get your Spine account and base access through personal onboarding.
2. Open Gemini on the web and go to Settings → Connected Apps. Some layouts put Connected Apps under Personal Intelligence.
3. Under Custom apps, choose Add a custom app.
4. Enter the MCP server URL supplied during onboarding. The new Spine service targets https://app.spine-kb.com/mcp.
5. Select Next and complete the sign-in and consent steps with your own Spine account.

Google documents additional credentials for servers without Dynamic Client Registration. Do not paste a password or secret into a chat to configure access.

Use Spine in a conversation

Type @ and choose your connected app to select it explicitly. Include the full private Spine document link and your task, or name the relevant base when necessary. Ask the agent to follow Spine’s agent entry, load the current server guide and read your personal context for the selected base.

Gemini Apps connects directly to the remote MCP. Installing a local Antigravity plugin does not install this connection or deliver its skill to Gemini web/mobile. The server’s tool descriptions and guide remain important for bootstrap. Google currently requires manual confirmation for write actions.

The new endpoint’s OAuth, real conversations, bootstrap delivery and mobile behaviour still require verification after deployment. Access to a custom app does not grant access to every Spine base or document.