Skip to content

Commit 1a7fade

Browse files
smultanimherrman
andauthored
docs for gemini (#2157)
* docs for gemini docs for gemini * Fixing URL Fixing URL --------- Co-authored-by: mherrman <[email protected]>
1 parent ea9835a commit 1a7fade

File tree

1 file changed

+57
-1
lines changed

1 file changed

+57
-1
lines changed

pages/docs/features/mcp.mdx

Lines changed: 57 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ After the organization admin enables MCP:
8181

8282
## Implementation Guide
8383

84-
### Prerequisites (for Claude Free & Cursor)
84+
### Prerequisites (for Claude Free, Cursor & Gemini CLI)
8585
**Install Node.js (if needed):**
8686
```bash
8787
brew install node
@@ -171,6 +171,62 @@ npx -y mcp-remote https://mcp.mixpanel.com/sse --allow-http
171171

172172
---
173173

174+
### Option 4: Google Gemini CLI
175+
176+
**Additional Requirements:**
177+
- [Gemini CLI](https://github.com/google/gemini-cli) installed
178+
- Command line access
179+
180+
**Setup Steps:**
181+
1. Install the Gemini CLI by following [Gemini CLI installation instructions](https://github.com/google-gemini/gemini-cli?tab=readme-ov-file#-installation).
182+
2. Authenticate to Google Gemini using your Google account:
183+
```bash
184+
gemini
185+
```
186+
3. Configure Mixpanel MCP as a remote server and authorize:
187+
```bash
188+
npx -y mcp-remote https://mcp.mixpanel.com/sse --allow-http
189+
```
190+
Running this command will provide a link in your terminal to authorize your access with Mixpanel. Follow the authorization steps in your browser. After logging in via OAuth, you should see a confirmation message.
191+
192+
4. **Verify Configuration (or Create It Manually):**
193+
After authorization, your `settings.json` file for the Gemini CLI should be updated automatically. You can find this file at `~/.gemini/settings.json`. To check, run:
194+
```bash
195+
ls -la ~/.gemini
196+
cat ~/.gemini/settings.json
197+
```
198+
The contents should be similar to the following:
199+
```json
200+
{
201+
"theme": "Default",
202+
"selectedAuthType": "oauth-personal",
203+
"mcpServers": {
204+
"mixpanel-remote": {
205+
"command": "npx",
206+
"args": [
207+
"-y",
208+
"mcp-remote",
209+
"https://mcp.mixpanel.com/sse",
210+
"--allow-http"
211+
]
212+
}
213+
},
214+
"preferredEditor": "vim"
215+
}
216+
```
217+
This configuration ensures that the Gemini CLI knows how to connect to the Mixpanel remote server.
218+
If `settings.json` is not available, create it manually using the same contents as above.
219+
220+
221+
5. Complete Mixpanel authorization via the provided link (if not already done).
222+
6. Run the Gemini CLI
223+
Once configured, you can use the Gemini CLI with the specified model by running this command:
224+
```bash
225+
gemini
226+
```
227+
228+
---
229+
174230
## Use Case Examples
175231

176232
**Channel Performance Analysis**

0 commit comments

Comments
 (0)