Gemini CLI

Gemini CLI Social Media MCP Setup

Gemini CLI connects to a social media MCP server through an httpUrl field plus headers in its settings file. Point httpUrl at https://mcp.blotato.com/mcp, add blotato-api-key as a header, and the terminal agent gets publishing and scheduling across nine platforms.

Endpoint https://mcp.blotato.com/mcp API key header

Connect Gemini CLI See pricing

Updated July 2026

How to connect Gemini CLI to social media

Connect your social accounts in Blotato and copy your API key from Settings then API.
Add a server entry to your Gemini CLI settings using the httpUrl field, not a command.
Set httpUrl to https://mcp.blotato.com/mcp.
Add blotato-api-key as a header with your key as the value, then restart the CLI.

settings.json entry using httpUrl, not command

{
  "mcpServers": {
    "blotato": {
      "httpUrl": "https://mcp.blotato.com/mcp",
      "headers": {
        "blotato-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Gemini CLI MCP documentation showing remote server configuration — Gemini CLI's own MCP documentation, showing where the remote server config goes.

How do I know it worked?

Ask Gemini CLI to list your connected accounts. It calls blotato_list_accounts and returns your platforms, which confirms both the connection and the authentication in one step. If you see your accounts, setup is done.

First prompt to run

What social media accounts do I have connected?

An AI agent answering "what social accounts do i have connected?" by calling Blotato and listing 10 connected social media accounts across Twitter, Bluesky, Instagram, Threads, LinkedIn, Facebook, YouTube, Pinterest, and TikTok — The reply you are looking for: the agent calls Blotato and lists every connected account. Here it returns 10 accounts across all nine platforms.

Worth knowing before you rely on it: analytics prompts only return data for X, Instagram, Facebook, Threads, and Bluesky. The other four platforms publish normally but report no metrics yet.

What breaks, and how to fix it

The Gemini CLI trap is the field name. Its config supports a command entry for local stdio servers and an httpUrl entry for remote ones, and a hosted endpoint placed in the command field will not connect. Use httpUrl. The second thing to know is that its OAuth flow needs a browser and a redirect on localhost, so on a headless box, an SSH session without forwarding, or a container, use the header instead of /mcp auth.

What is different about Gemini CLI

Gemini CLI distinguishes local and remote servers by which field you fill rather than by a transport setting, so the whole difference between a working and a non-working config is one key name. It also ships per-server tool filtering: includeTools acts as an allowlist and excludeTools as a denylist, which is the cleanest way on this list to give an agent publishing tools while withholding anything that spends credits. Run /mcp to list what a server actually exposed, and /mcp auth to manage OAuth per server.

Vendor documentation: Gemini CLI MCP setup. For how a client discovers and calls tools once connected, see the MCP client concepts reference.

FAQ

Gemini CLI social media FAQs

01 Can Gemini CLI post to social media?

Yes. Gemini CLI cannot reach a social account on its own, because it has no platform credentials. Connecting it to Blotato's hosted MCP server at https://mcp.blotato.com/mcp gives it tools to publish and schedule across nine platforms: X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest. Gemini CLI authenticates with api key header.

02 How do I connect Gemini CLI to social media?

03 How do I set up Gemini CLI for social media?

Setting up Gemini CLI for social media takes one connection. Connect your social accounts in Blotato, then give Gemini CLI the hosted MCP endpoint https://mcp.blotato.com/mcp and authenticate with api key header. For Gemini CLI specifically that means: settings.json entry using httpurl, not command. Once it loads, Gemini CLI can publish and schedule to X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest from a plain-language prompt.

04 What is the best way to manage social media with Gemini CLI?

Let Gemini CLI do the drafting and decision making, and let a publishing layer hold the accounts and the schedule. The thing that makes this work on Gemini CLI in particular: Gemini CLI distinguishes local and remote servers by which field you fill rather than by a transport setting, so the whole difference between a working and a non-working config is one key name. It also ships per-server tool filtering: includeTools acts as an allowlist and excludeTools as a denylist, which is the cleanest way on this list to give an agent publishing tools while withholding anything that spends credits. Run /mcp to list what a server actually exposed, and /mcp auth to manage OAuth per server.

05 What goes wrong when connecting Gemini CLI?

06 Does Gemini CLI need to be running for a scheduled post to go out?

No. Scheduling runs on Blotato rather than inside Gemini CLI. Once the agent queues a post, it publishes at the scheduled time whether or not Gemini CLI, your terminal, or your laptop is on. This is the practical difference between an agent that drafts and a system that runs unattended.

07 Do I need a developer app or platform API keys to use Gemini CLI this way?

No. Blotato holds the platform integrations and manages the OAuth tokens, including refreshes. You connect each social account through a normal login flow instead of registering your own app on every network and waiting for review. Gemini CLI never handles a platform credential.

08 What can Gemini CLI not do on social media?

Publishing and scheduling cover all nine platforms, but the rest is uneven and worth knowing before you build against it. Analytics covers X, Instagram, Facebook, Threads, and Bluesky. Comments and direct messages cover Instagram and Facebook. Keyword-triggered DM automation is not available at all. None of that varies by agent: it is the same surface whichever client you connect.

09 How much does it cost to connect Gemini CLI?

Starter is $29/mo flat for 20 connected accounts, and the price does not scale with posting volume. API and MCP access is not part of the 7-day trial: generating a key activates the paid Starter plan, so plan on subscribing rather than trialing it.

Connecting a different agent?

Same endpoint, same accounts, one setup per client. The AI agents for social media hub covers what all of them share, including every tool your agent can call.