Transparency: this article contains affiliate links. If you purchase hosting through my link, I will receive a small commission at no additional cost to you.
This is a submission for the Gemma 4 Challenge: Write About Gemma 4.
The Problem: My Tokens Are Flying to Google Cloud
A few weeks ago, I shared how I set up Gemini CLI for managing Pressable servers directly from the Fedora terminal: no browser, no extra clicks - just commands, and the server infrastructure obeys.
But the euphoria quickly turned into a question: "Where are my confidential tokens being processed?"
The access key to the production server was flying to Google Cloud. Logs, PHP versions, site structure - everything was passing through someone else's data center. It's like giving your apartment keys to your neighbors: they might be decent people, but it's more peaceful when the keys are only with you. π
Solution: I switched to Gemma 4 - an open model from Google with an Apache 2.0 license, which gives full control over the data. And I found a hybrid approach for those whose laptop physically can't handle 32 GB of RAM: I run Gemma 4 through Google AI Studio, getting all the power of the model without expensive hardware.
Gemini CLI vs Gemma 4: Comparison for DevOps
Before diving into the terminal, let's put the dots over the "i". Here are the key criteria that influenced my choice:
| Criterion | Gemini (Cloud) | Gemma 4 (API / Local) |
|---|---|---|
| Confidentiality | Data is transmitted to Google servers π | Data does not leave the perimeter. Even through the Google AI Studio API, it is not used for training π‘οΈ |
| License | Proprietary π | Apache 2.0 - free commercial use, modification, distribution π |
| Context Window | Up to 1 million tokens π | 128K tokens - enough for analyzing large server logs β |
| Advanced Thinking | Yes π‘ |
thinking: true - models 26B and 31B have a thinking mode, ideal for diagnostics π§ |
| Cost | Paid after limits are exhausted πΈ | Free tier in AI Studio π |
| Autonomy | Requires internet βοΈ | Can work fully offline on your own server π |
| Customization | Limited β | Full freedom: fine-tuning, running on your own hardware βοΈ |
For managing WordPress hosting through Pressable MCP, I chose Gemma 4 31B (Dense) - the most powerful model in the lineup with thinking: true, capable of analyzing complex API responses and making informed decisions.
We also recommend reading: AI WordPress Hosting Management via Linux CLI
Step 1: Creating an API Key for Gemma 4 in Google AI Studio
Any path begins with the first step. We will receive the access key not in Google Cloud, but in Google AI Studio - this is free and does not require a bank card.
- Go to aistudio.google.com
- In the left menu, select API Keys
- Click Create API key and select a project (or create a new one, for example,
Pressable Gemma 4 Agent) - Copy the generated key
β οΈ IMPORTANT: the key will be shown only once. Save it immediately.
Now, export the key to an environment variable in the Fedora terminal:
export GEMINI_API_KEY="AIzaSy...your_new_key"
Step 2: First Run of Gemma 4 in the Linux Terminal
The most interesting moment - checking if the model responds. We use gemini-cli, explicitly specifying the model through the --model parameter:
gemini --model models/gemma-4-31b-it -p "Say hello from Gemma 4 31B"
Response:
Hello! Gemma 4 31B here. How can I help you today?
The model works! π€
Step 3: Connecting Pressable MCP to Gemma 4
Now, the main thing: connect Gemma 4 to Pressable MCP, so that the model can directly manage hosting through the Model Context Protocol.
3.1. Removing the Old Configuration
gemini mcp remove pressable
3.2. Adding the Pressable MCP Server
gemini mcp add pressable https://mcp.pressable.com
3.3. Specifying the Authorization Token
Open the configuration file:
nano /mnt/DATA/pressable-mcp-project/.gemini/settings.json
Add the Pressable Access Token to the headers section:
{
"mcpServers": {
"pressable": {
"url": "https://mcp.pressable.com",
"headers": {
"Authorization": "Bearer YOUR_PRESSABLE_ACCESS_TOKEN"
}
}
}
}
3.4. Checking the Connection Status
gemini mcp list
We see the desired green status - Connected! π’
Step 4: Gemma 4 as an AI Administrator of the Server
Launch an interactive chat with Gemma 4:
gemini chat -m models/gemma-4-31b-it
Give a combat task (in English - this is how the API works most accurately):
> Please list all the sites on my Pressable account
and tell me the PHP version of shchoiyak-sandbox.
Here, the magic of the Model Context Protocol happens: Gemma 4 understands that it needs the search_sites tool and requests permission to execute it. Choose Allow once or Allow all server tools for this session.
The model receives raw JSON from the Pressable API, analyzes it thanks to the thinking: true mode, and provides a clear response:
- Domain: shchoiyak-sandbox.mystagingwebsite.com
- PHP Version: 8.5
- State: live
- Datacenter: BUR (Burbank, CA)
Result: without any browser and login to the control panel - all critical information is right in the terminal.
Conclusion: Why Gemma 4 for DevOps is the Right Choice
Switching from Gemini CLI to Gemma 4 + Pressable MCP is not just a model replacement. It's a fundamental change in approach to security and control over data:
- β Confidential tokens do not leave your perimeter
- β Apache 2.0 license - complete freedom for commercial projects
- β
thinking: truemode for deep analysis of server logs - β Free access through Google AI Studio
- β Ability to work fully offline on your own server
Yes, running Gemma 4 31B locally requires a powerful server. But even through Google AI Studio, it's free, secure, and preserves the main thing - openness and independence.
Try Pressable for Your WordPress Projects
Want to manage servers like a real AI-ninja? Refuse routine clicking and switch to infrastructure created by the same people who write the WordPress core.
π Try AI management from Pressable today
And if you need fast and stylish creatives for your new site's social media - use the free graphic editor SMM Turbo.





Top comments (0)