Google’s Gemini is a generative artificial intelligence (AI) powered conversational assistant that can help you understand, build, extend, and operate applications. You can ask questions about architecture, best practices, documentation, support, and more.
For more information, refer to:
In both installation methods below, you must ensure the CLOUDBEES_PERSONAL_ACCESS_TOKEN environment variable is set before booting the CLI.
You can also set this variable in your environment configuration.
|
MCP client configuration examples are provided for demonstration purposes only, and they do not constitute an endorsement or recommendation. Review and adapt configurations to meet your organization’s environment and security requirements. |
Installation
Google’s Gemini CLI is available by following the instructions at https://github.com/google-gemini/gemini-cli.
Make sure that your CLI is able to communicate with Google’s LLM by running some test commands with the Gemini CLI.
MCP Configuration
Configure the MCP extension
You can configure an MCP extension to connect with the CloudBees MCP MCP server.
You must acquire your organization ID first and then place it directly into the configuration. For more information, refer to how to retrieve your organization ID. |
The MCP configuration should be added to your ~/.gemini/settings.json
file:
Docker-based MCP configuration
If you prefer to use the Docker-based CloudBees MCP MCP server, you can configure it as follows:
{ "mcpServers": { "cloudbees": { "command": "docker", "args": [ "run", "--rm", "-i", "--env", "CLOUDBEES_PERSONAL_ACCESS_TOKEN", "cloudbees/cloudbees-mcp:latest", "stdio", "--mode=platform", "--organization-id=<ORGANIZATION_ID>" ], "env": {}, "timeout": 120000, "disabled": false } } }