Grok

Grok

Custom connector

Connect Botvee to Grok as a custom MCP connector. Grok discovers Botvee’s live tools and uses the same OAuth, permissions, confirmation, isolation, and audit controls already used by ChatGPT and Claude.

Before you start

  • A Botvee account with access to the workspace you want to manage
  • A Grok plan or organization where custom connectors are enabled
  • On Grok Business or Enterprise, a team administrator may need to add Botvee before members can connect it

Botvee connection URL

Use this public HTTPS endpoint for the custom connector:

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

How to connect Grok

  1. 1

    Open Connectors

    Go to grok.com/connectors

  2. 2

    Add Botvee

    Click New Connector, choose Custom or Other, and name it Botvee

  3. 3

    Enter the endpoint

    Paste the Botvee MCP server URL shown above

  4. 4

    Complete OAuth

    Continue with OAuth, sign in on Botvee’s secure page, review permissions, and click Allow access

  5. 5

    Verify

    Let Grok discover the tools, then ask which Botvee account is connected before reading or changing workspace data

Note

Grok must connect to the public HTTPS endpoint. Do not use localhost, a private IP address, an API key, or a Botvee password.

What Grok can do

AreaAvailable actions
AI agentsReview, create, and update accessible agents
InboxRead conversations and waiting counts
Support ticketsReview, create, claim, update, and assign tickets
EmailRead received email and save drafts without sending
BookingsReview and update bookings
LeadsReview and add leads
EcommerceReview products, orders, COD, recovery, stock alert, and post-delivery data

Security and confirmation

  • Botvee uses OAuth with PKCE and rotating refresh tokens
  • The connection follows the current Botvee user’s permissions instead of creating a separate superuser
  • Grok must describe the exact intended write and wait for explicit user confirmation
  • Draft tools do not send email, and ticket notes do not notify customers
  • Every MCP call is auditable in Botvee

Prompts to test

Grok 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.

Disconnecting

Remove Botvee from Grok Connectors to stop future access. Reconnecting requires a fresh Botvee authorization.

Troubleshooting

  • New Connector is unavailable: Ask the Grok organization administrator to enable or add custom connectors
  • Grok cannot reach the server: Confirm the URL is exactly the public HTTPS Botvee MCP endpoint
  • Authentication repeats: Remove the connector and connect again so OAuth registration and tokens are recreated
  • Data is limited: Check the connected Botvee user’s role, AI agent assignments, channels, and dashboard sections

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