Connect guide · API key (bearer header)

Connect Cubite LMS to Gemini CLI

In short: Gemini CLI connects to Cubite with a scoped API key: create the key in Admin, then your site, then Integrations; add a cubite entry under mcpServers in your Gemini settings with httpUrl https://cubite.io/api/mcp/mcp and an Authorization: Bearer header; restart Gemini CLI. The same shape works for any HTTP MCP client that can send a bearer header.

Steps

  1. 1

    Create a scoped API key

    In Cubite Admin, open your site, then Integrations, and create a key with only the scopes you need. The key is shown once; store it in a secret manager.

  2. 2

    Add the server to Gemini CLI

    Put this entry in your Gemini settings file (settings.json in the .gemini folder of your home directory or project).

    {
      "mcpServers": {
        "cubite": {
          "httpUrl": "https://cubite.io/api/mcp/mcp",
          "headers": {
            "Authorization": "Bearer ck_your_key_here"
          }
        }
      }
    }
    json
  3. 3

    Restart and check

    Restart Gemini CLI and list the MCP servers; the cubite server and its tools should appear. Ask for something concrete, such as listing courses.

Good to know

  • A key carries only the scopes you gave it; a write scope also grants the matching read (except forms:write, which never reads learner responses).
  • Rotate or revoke keys from the same Integrations screen.

Facts

  • Server URL: https://cubite.io/api/mcp/mcp (streamable HTTP)
  • Tools: 137, permissioned per connection or per key
  • Cost: included with every Cubite site ($290/mo or $2,900/yr)
  • Disconnect: Delete the key in Admin, then your site, then Integrations; every client using it loses access immediately.
Support

How can we help?

Send us a message and we'll get back to you shortly.

We typically respond within 24 hours

Connect Cubite LMS to Gemini CLI (MCP, API key) | Cubite