Skip to main content

Connect Gemini

Google's Gemini connects to MCP servers in a few places. The most direct for an individual is the Gemini CLI; organizations can also register Rise centrally in Gemini Enterprise / Agentspace.

Before you start

  • The Rise server URL: https://mcp.risepeople.com/mcp
  • A Rise account with reporting access.
  • Gemini CLI installed and signed in, or access to Gemini Enterprise / Agentspace as an admin.

Gemini's MCP support evolves quickly. If a setting name differs, check Google's Gemini CLI documentation. The durable facts are the server URL and that authentication is OAuth.

Gemini CLI

The CLI reads MCP servers from a settings.json file — global at ~/.gemini/settings.json, or per-project at .gemini/settings.json in your working directory.

  1. Add Rise under mcpServers. Use httpUrl for the streamable-HTTP transport Rise uses:

    {
    "mcpServers": {
    "rise": {
    "httpUrl": "https://mcp.risepeople.com/mcp"
    }
    }
    }
  2. Start (or restart) the Gemini CLI and authenticate to Rise:

    /mcp auth rise

    A browser window opens for Rise sign-in. Log in and approve access (reports:read, plus reports:write if you want Gemini to save reports). The CLI stores the token and refreshes it for you.

  3. Confirm it's connected and see the available tools:

    /mcp list
  4. Ask a question:

    What's our average tenure by location?

    See more prompts on What you can ask.

If your build needs explicit OAuth details

Some environments require you to register an OAuth client rather than relying on automatic discovery. Register an OAuth application in Rise and use:

  • Authorization URL: https://api.risepeople.com/v1/oauth/authorize
  • Token URL: https://api.risepeople.com/v1/oauth/token
  • Scopes: reports:read reports:write
  • PKCE: enabled (use a public client)

Gemini Enterprise / Agentspace

If your organization uses Gemini Enterprise (Agentspace), an administrator can register Rise once for everyone:

  1. In the admin console, add a custom MCP server / tool.
  2. Server URL: https://mcp.risepeople.com/mcp; Authentication: OAuth 2.0, using the authorization and token URLs above and scopes reports:read reports:write.
  3. Publish it to the relevant users. Each user signs in to their own Rise account on first use — identity and permissions are always per-user.

Troubleshooting

SymptomFix
/mcp list shows Rise as disconnectedRun /mcp auth rise and complete the browser sign-in. Check the URL in settings.json uses httpUrl (not url).
No browser opens for authCopy the URL the CLI prints into a browser manually, or configure explicit OAuth client details (above).
Connected but "no reports"Your Rise account may not be enabled for the connector yet — email developers@risepeople.com.
"Insufficient scope" when savingRe-auth and approve reports:write. See insufficient-scope.

Remove it

Delete the rise entry from your mcpServers config (CLI), or remove the registered server in the Gemini Enterprise admin console. You can also revoke the token from your Rise account.