Why Connect Grok?
- Analytics on demand: Get a full report for any date range
- Close content gaps: See what your bot could not answer and add the missing answers
- Routines: Let a Grok Bot routine check your chatbot every week and report what it found
- Install the widget from your project: Grok Build gets your embed snippet and adds it to your code
- No API key: OAuth handles the connection
Prerequisites
- A BubblaV account. You can create one during the sign-in step
- Grok Bot, or the Grok Build CLI
Connect BubblaV
Grok Bot
1
Add the app
Open Connect apps, search for BubblaV, and add it. You can also ask your Bot: “Add the BubblaV app.” If BubblaV is not in the list yet, ask your Bot: “Add the MCP server https://www.bubblav.com/mcp.”
2
Authorize BubblaV
Select Authenticate (on the phone, Authorize). The BubblaV sign-in page opens. Sign in, select the website (chatbot) to connect, choose Full access or Read only, and approve. If you do not have a website, choose to create a chatbot without one.
3
Try it
Ask “How is my BubblaV chatbot performing this month?” or “Which questions could my chatbot not answer last week?”
Grok Build (CLI)
Install the BubblaV plugin. It adds the MCP server and two skills: add-chat-widget and manage-custom-tools./mcps, select BubblaV, and press i to sign in.
After you approve, BubblaV creates an API key in your account for the connection. The key is named after the app that connected, for example Grok. Grok Bot connects through Cursor’s connector service, so its key can show as Cursor.
What You Can Ask
For the full tool reference, see the MCP Server developer guide. For ready-to-use prompts, see AI Agent Workflows.
Privacy
- One connection gives access to one website (chatbot)
- Conversations and leads can contain your visitors’ names, email addresses, and messages. Grok sees this data when a tool returns it
- Grok Bot keeps the OAuth token on its connector service. The Bot calls tools without receiving the token
- BubblaV logs every tool call. See Integrations → MCP Settings → Audit Logs
- See the Privacy Policy
Rate Limits
MCP calls are metered separately from your chatbot messages, on a rolling 30-day window:
When you exceed the limit, requests return a
429 with a Retry-After header. Check your usage under Integrations → MCP Settings in the dashboard.
Disconnect or Switch Website
Revoke the API key for the connection in your BubblaV dashboard. Then connect BubblaV again and pick the website you want during sign-in.Troubleshooting
BubblaV shows 'Needs auth' or 'Disconnected' in Grok Bot
BubblaV shows 'Needs auth' or 'Disconnected' in Grok Bot
- Open Connect apps, open BubblaV, and select Authenticate (or Reconnect).
BubblaV shows 'Disabled by team admin'
BubblaV shows 'Disabled by team admin'
- Your team’s connector policy blocks BubblaV. Ask your admin to allow it.
Grok does not use BubblaV tools
Grok does not use BubblaV tools
- In Grok Bot, type
@and attach BubblaV to the task. - Name the task directly, for example “Use BubblaV to get my widget snippet.”
Next Steps
MCP Server
Full tool reference and other MCP clients
Custom Tools
Webhook tools you can create from Grok
Cursor
Use BubblaV from Cursor
