Connect Helios to Gemini

Connect Gemini to your Premium game server using the Helios MCP endpoint. First create a Helios API key on the correct server with View server status and View kits. Use a separate key for Gemini so you can revoke its access independently.

Gemini web app

1. Check your Google account

Google currently requires a personal Google Account, age 18 or over, a US location, English, and Keep Activity enabled. Work and school accounts do not currently support custom apps. Check Google's custom-app requirements if the option is missing.

2. Add Helios as a custom app

1. Open Gemini and go to Settings → Connected Apps. If needed, open Personal Intelligence first, then Connected Apps.
2. Under Custom apps, add this MCP server URL and choose Next:

https://api.heliosrce.com/mcp

3. Leave Additional settings blank. Helios registers the connection automatically; you do not need to enter a client ID or client secret.
4. Review Google's connection prompts. When the Helios connection page opens, paste your Helios API key there and choose Connect.
5. If Gemini asks for an app name, enter Helios and choose Connect to save it.

Keep your Helios API key out of chat messages and Google's Client secret field. Each connection uses the owner, server, permissions and expiry of the key you selected.

3. Test with a read

Back in Gemini, type @ and select Helios. Start with:

Use Helios to show the connected server name and list its kits.
Do not make any changes.

Confirm the returned server is correct. A read-only key cannot create, edit, install or delete kits.

What has been tested

Helios verified a Gemini web connection, automatic registration, server reads and kit-list reads on a testing server. These checks used a read-only key.

The Gemini web app did not display the interactive Kit Builder in our browser tests. It returned text or JSON instead of the embedded visual editor. Use ChatGPT, a compatible Claude client or the Helios dashboard for visual kit editing.

Live server changes through Gemini have not been tested. Giving a key write permissions does not approve a change: review the exact target and preview, then approve each requested change in the original chat. Read AI permissions and scope before granting additional access.

Gemini CLI

Gemini CLI can use the same endpoint with a Bearer key. Merge this entry into mcpServers in your user settings at ~/.gemini/settings.json (Windows: %USERPROFILE%\.gemini\settings.json). Preserve your existing settings and other servers.

{
  "mcpServers": {
    "helios": {
      "httpUrl": "https://api.heliosrce.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_HELIOS_API_KEY"
      },
      "trust": false
    }
  }
}

Replace YOUR_HELIOS_API_KEY in the private settings file with your key. Keep that file out of Git and do not share it. Leave trust set to false so tool confirmations remain enabled.

Restart Gemini CLI, run /mcp to check the connection, then try the read-only prompt above. This configuration is separate from the Gemini web custom-app connection; the browser acceptance checks above do not establish CLI acceptance. See the Gemini CLI MCP guide for client configuration details.

If the connection fails

• Custom apps is missing: check Google's eligibility requirements and the selected Google account.
• Authentication fails: check the MCP URL, leave Additional settings blank and reconnect with an unexpired Helios key.
• Helios is not being used: select Helios with @ and explicitly ask Gemini to use it.
• A tool is denied: check the key's permissions, the selected server's enabled/Premium status and your current Discord management access.
• The visual builder does not appear: use the Helios dashboard or another supported visual client; reconnecting does not establish embedded-editor support.

Manage or revoke the key in Manage Server → AI → Your API keys. See AI setup and access management for the shared permission rules.