# Connect Gemini CLI to Tesselith

> Add Tesselith to Gemini CLI and schedule social posts from your terminal with Google's Gemini.

Canonical: https://tesselith.com/ai-agents/gemini-cli

**Before you start:** You need Gemini CLI installed and a Tesselith workspace on Pro, Team or Agency (every new workspace starts with a 14-day Pro trial) with at least one channel connected.

## Quick setup

```bash
# 1. Add the Tesselith MCP server for your user
gemini mcp add -s user --transport http tesselith https://api.tesselith.com/mcp

# 2. Start Gemini CLI and sign in
gemini
/mcp auth tesselith
```

## Step by step

### 1. Add the server

-s user saves it to ~/.gemini/settings.json for every project; without it, it's saved to the current project's .gemini/settings.json.

```json
{
  "mcpServers": {
    "tesselith": {
      "httpUrl": "https://api.tesselith.com/mcp"
    }
  }
}
```

### 2. Sign in with /mcp auth

Start gemini and run /mcp auth tesselith. A Tesselith window opens. Sign in, pick the workspace, untick anything you don't want the agent to do, and click Allow access.

### 3. Check it's connected

Run /mcp. Tesselith should show as CONNECTED with its tools. Outside a session, gemini mcp list does the same.

### 4. Ask Gemini

Ask Gemini to list your Tesselith channels, then to draft or queue a post. It confirms each tool call unless you trust the server.

## With an API key

For headless runs, pass a key as a header. In Tesselith, open Settings → Developers, create an API key and tick only the scopes the agent needs. Keys start with tsl_live_ and are shown once, so store it in your password manager or a secret store.

```bash
gemini mcp add -s user --transport http \
  --header "Authorization: Bearer $TESSELITH_API_KEY" \
  tesselith https://api.tesselith.com/mcp
```

## Troubleshooting

- **Connects as SSE and fails:** The entry uses url instead of httpUrl. Use httpUrl, or re-add with --transport http.
- **Server not found in other projects:** The default scope is the project. Re-add it with -s user.
- **DISCONNECTED after a 401:** Run /mcp auth tesselith again, or use an API key header.

## Questions people ask

### Where does Gemini CLI store the sign-in?

Tokens are saved in ~/.gemini/mcp-oauth-tokens.json.

### Should I use --trust?

Only if you're happy for Gemini to call every Tesselith tool without asking. Leave it off so scheduling and publishing need your approval.

Docs: https://geminicli.com/docs/tools/mcp-server/

---
Tesselith · https://tesselith.com · Full site index: https://tesselith.com/llms.txt