Gemini

Gemini

Custom connector

Connect Botvee to Gemini through Google’s MCP connected-app support. Gemini uses the same secure Botvee tools as ChatGPT and Claude, with access limited to the signed-in user’s current workspace role and assignments.

Before you start

  • A Botvee account with access to the workspace you want to manage
  • Gemini Apps Developer Mode for browser testing, or Gemini CLI for a local developer connection
  • Permission to add a custom MCP app or edit Gemini CLI settings

Botvee connection URL

Copy this exact public HTTPS endpoint into Gemini:

Botvee MCP server URLtext
https://api.botvee.ai/mcp

Connect from Gemini Apps

  1. 1

    Open Developer Mode

    Go to gemini.google.com/devmode, or open Gemini Settings and choose Gemini Apps Developer Mode

  2. 2

    Create the app

    Click Create new and enter the Botvee MCP server URL shown above

  3. 3

    Use OAuth

    Choose Dynamic Client Registration in the Authentication tab; Botvee does not require a client secret

  4. 4

    Approve Botvee

    Sign in on the secure Botvee page, review the requested permissions, and click Allow access

  5. 5

    Verify tools

    Confirm Botvee tools appear under Available actions, save the app, then use @Botvee in a chat

Connect from Gemini CLI

Add the configuration below to your user or project Gemini settings file, restart Gemini CLI, then run /mcp auth botvee. The browser opens Botvee sign-in and approval. After connecting, use /mcp list to verify the tools.

Gemini CLI settings.jsonjson
{
  "mcpServers": {
    "botvee": {
      "httpUrl": "https://api.botvee.ai/mcp"
    }
  }
}

Note

Gemini CLI discovers Botvee’s OAuth endpoints and registers a public PKCE client automatically. No Botvee password, token, client ID, or client secret belongs in the settings file.

What Gemini can do

AreaAvailable actions
AI agentsList agents, read full settings, create agents, and edit agent details
InboxRead conversations and show waiting and active counts
Support ticketsList, create, claim, update, and assign tickets within the user’s permissions
EmailRead received email and save drafts without sending
BookingsList and edit bookings
LeadsList and add leads
EcommerceView feature status, products, orders, COD activity, recovery, stock alerts, and post-delivery activity

Security and confirmation

  • Botvee uses OAuth authorization code flow with PKCE and short-lived access tokens
  • Refresh tokens rotate and can be revoked by disconnecting
  • Every request re-checks the user’s current Botvee role and workspace access
  • Gemini must show the exact intended change and receive explicit confirmation before a write tool is used
  • Every tool call is recorded in Botvee’s MCP audit log

Prompts to test

Gemini test promptstext
Which Botvee account is connected?

Show my AI agents, waiting inbox count, and latest unassigned support tickets. Do not change anything.

Prepare one safe test change, show the exact before and after values, and wait for my explicit confirmation before using a write tool.

Troubleshooting

  • OAuth asks for a client ID: Choose Dynamic Client Registration instead of Manual Client Registration
  • Gemini CLI reports a missing issuer parameter: Let it use discovered OAuth metadata, or set authorizationResponseIssParameterSupported to false only when configuring the issuer manually
  • Tools are missing: Sync the schema in Developer Mode, or run /mcp reload in Gemini CLI
  • The wrong account is connected: Disconnect Botvee, sign out of Botvee in the browser, and connect again

Can’t find what you are looking for? Contact support