echoia®
Echoia

Connect Gemini to your social media accounts

Google offers MCP in several places, and they do not work the same way. The one that works with Echoia today for personal accounts is Antigravity CLI, Google's agent for the terminal, which replaced Gemini CLI for individual users in June 2026. Gemini CLI still serves enterprise licences. Here is the setup for both, and where the Gemini app stands.

Works, with limits
Works onAntigravity CLI, or Gemini CLI on enterprise licences
Connects withKey in a header
Setup timeAbout 3 minutes

Works today in Antigravity CLI, and in Gemini CLI on enterprise licences. Not in the Gemini app yet: its custom apps expect a sign-in flow that Echoia does not offer.

What you can ask Gemini

“List the negative comments from the last 24 hours, newest first.
“Schedule the post in launch.md for Friday at 9am on LinkedIn and X.
“Which of my accounts grew the most this month?

Gemini gets six tools from Echoia (accounts, posts, stats, creating a post, reading comments, replying) across Instagram, Facebook, TikTok, YouTube, X, LinkedIn, Threads, Bluesky, Pinterest and Google Business, limited to what your key allows.

Before you start

Antigravity CLI, installed and signed in with your Google account.
Or Gemini CLI, if your organization has a Google Workspace or Gemini Code Assist Standard or Enterprise licence.

STEP 1 OF 2

Create your Echoia key

Gemini connects with a key you create and can revoke at any time. It takes a minute.

  1. 1
    Open the Developers settings

    Sign in to Echoia, open Settings, then Developers.

  2. 2
    Create a key and choose what it may do

    Name it after the assistant so you recognise it later, and tick its permissions (explained further down). If you have several workspaces, choose which ones it can reach.

  3. 3
    Copy the key now

    It starts with eko_ and is shown only once: Echoia keeps only a fingerprint of it. If you lose it, revoke it and create a new one.

STEP 2 OF 2

Connect Gemini

Pick the one you use. You can do both with the same key.

OPTION A

Antigravity CLI

  1. 1
    Open the MCP config file

    Antigravity reads the MCP servers available in every project from ~/.gemini/config/mcp_config.json. Create the file if it does not exist yet. For one project only, use .agents/mcp_config.json at the project's root instead.

  2. 2
    Add Echoia

    Add this entry with your key in place of the placeholder. Note the field name serverUrl: Antigravity no longer reads the older url and httpUrl fields, and a server declared with them silently stays offline.

    ~/.gemini/config/mcp_config.json
    {
      "mcpServers": {
        "echoia": {
          "serverUrl": "https://mcp.echoia.io/mcp",
          "headers": {
            "Authorization": "Bearer eko_your_key"
          }
        }
      }
    }
  3. 3
    Check the connection

    Start Antigravity CLI, type /mcp and press Enter. Echoia should be listed with its tools. If it shows an error, the connection log in the same panel says why: a 401 means the key is wrong or revoked.

OPTION B

Gemini CLI

  1. 1
    Add the server

    Put your key in the ECHOIA_API_KEY environment variable and run this command. The transport must be set to http explicitly: Gemini CLI defaults to a local transport that ignores headers.

    Terminal
    gemini mcp add --transport http echoia https://mcp.echoia.io/mcp \
      --header "Authorization: Bearer $ECHOIA_API_KEY"
  2. 2
    Check the connection

    Start Gemini CLI and type /mcp. Echoia should appear with its six tools.

Which permissions to give Gemini

Read

Accounts, posts, stats and comments. Looks at everything, changes nothing.

Write

Drafts, scheduled posts and media uploads. A scheduled post goes out at its time.

Engage

Replies to comments in public, as your account.

Publish

Posts immediately, with no window to change your mind.

Our advice for Gemini: Terminal agents work through long tasks with little supervision. Give the key Read and Write, and add Publish only if you want posts to go out without passing through your calendar first.

Limits worth knowing

The Gemini app at gemini.google.com is not supported yet. Its custom apps are built around a sign-in flow in which Gemini registers itself with the server and asks you to approve it. Echoia authenticates with keys, so we cannot promise that connection works. When we add sign-in, this page will say so.
Agents in the terminal can upload an image from your disk through Echoia's media API before attaching it to a post. A picture shown to a chat cannot be attached the same way.

Questions

Who can use custom apps in the Gemini app?

According to Google, people aged 18 and over in the United States, signed in with a personal Google account, in English, with Keep Activity turned on. Work and school accounts cannot use them yet.

I used Gemini CLI before June 2026. What changes?

Google retired Gemini CLI for free, Google AI Pro and Ultra users on 18 June 2026 and moved them to Antigravity CLI. Your MCP servers move from ~/.gemini/settings.json to ~/.gemini/config/mcp_config.json, and the address field is now called serverUrl.

Is my key safe in the config file?

It is as safe as the file. Keep the file out of any shared folder or repository. If it leaks, revoke the key in Echoia under Settings, Developers: it stops working on the next request.

Ready to try it with Gemini?

Create a free Echoia account, connect your social accounts, and your key is one click away. No card needed.