Skip to main content
Gemini CLI is Google’s command-line AI assistant. You can connect it to TryPost’s MCP server to manage your social media scheduling with natural language.

​
Prerequisites

​
Setup

1

Open the settings file

Edit your Gemini CLI settings at ~/.gemini/settings.json:
{
  "mcpServers": {
    "trypost": {
      "httpUrl": "https://app.trypost.it/mcp/trypost",
      "oauth": {
        "enabled": true
      }
    }
  }
}
With oauth.enabled, Gemini CLI discovers TryPost’s OAuth metadata from the URL and registers dynamically. For project-level configuration, create .gemini/settings.json in your project root instead.
2

Restart Gemini CLI and sign in

Close and reopen Gemini CLI. The first TryPost call prompts you to sign in — Gemini CLI prints the authorize URL or opens your browser. Approve and return to the terminal.
3

Verify the connection

Ask Gemini to interact with your TryPost account:
List all my TryPost posts
Gemini CLI uses "httpUrl" for HTTP-streaming servers (not "url"). The "url" field is used for SSE transport only.
For headless environments, use a Personal Access Token instead of OAuth:
{
  "mcpServers": {
    "trypost": {
      "httpUrl": "https://app.trypost.it/mcp/trypost",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Create the key from Settings > API Keys on the TryPost dashboard.

​
Example prompts

Create a new signature called "Growth Hacking"

What workspace am I connected to?

Show me all my labels