Gemini CLI Integration

PostQuickAI for Google Gemini CLI

Google's Gemini CLI meets the universal MCP protocol. Add PostQuickAI once, then ask Gemini to schedule posts, generate content, or pull analytics — no custom code required.

1. Add to settings.json

Edit ~/.gemini/settings.json (or .gemini/settings.json for project scope):

{
  "mcpServers": {
    "postquickai": {
      "command": "npx",
      "args": ["-y", "@postquickai/mcp"],
      "env": {
        "POSTQUICKAI_API_KEY": "$POSTQUICKAI_API_KEY"
      }
    }
  }
}

Then export the key in your shell (e.g. in ~/.zshrc):

export POSTQUICKAI_API_KEY=pq_live_your_key_here

2. Optional — restrict tools

Block destructive operations for added safety:

{
  "mcpServers": {
    "postquickai": {
      "command": "npx",
      "args": ["-y", "@postquickai/mcp"],
      "env": { "POSTQUICKAI_API_KEY": "$POSTQUICKAI_API_KEY" },
      "excludeTools": ["deleteContentGroup", "deletePost", "deleteVideo", "disconnectAccount"]
    }
  }
}

3. Restart and test

Restart Gemini CLI, then ask it:

"List my PostQuickAI content groups"
"Plan 5 posts for this week grounded in my brand voice, schedule them for the morning slots"
"Show me last 30 days of analytics — which platform drove the most engagement?"
"Generate a carousel about our onboarding flow, schedule it for Thursday at noon"

API + Agent access

MCP server, Skills, and REST API are all included with the API add-on on any paid plan.

FAQ

Frequently Asked Questions

Global: ~/.gemini/settings.json. Project-scoped: .gemini/settings.json in your repo root. MCP servers are defined under the top-level mcpServers key.

Use environment-variable expansion. In settings.json, set "POSTQUICKAI_API_KEY": "$POSTQUICKAI_API_KEY" — Gemini CLI pulls the value from your shell env at runtime instead of hard-coding it in the config file.

Yes. MCP servers load at startup. Restart the Gemini CLI process for changes to take effect.

Yes. Gemini CLI supports excludeTools and includeTools arrays per server. Example: "excludeTools": ["deleteContentGroup"] blocks destructive operations while keeping read/write tools available.

Gemini CLI doesn't natively read AGENTS.md, but you can reference it in your system prompt or custom commands config. The MCP tools still work identically.

Troubleshooting

"Failed to connect to postquickai"

Almost always a config format issue. Make sure command is just npx and args is an array — never put the whole command in one string. Also fully quit and restart your agent after editing config.

"API add-on required" / 403 errors

MCP and REST API access both require the API add-on on your plan. Enable it at postquick.ai/pricing.

"Missing POSTQUICKAI_API_KEY"

Generate a key at postquick.ai/dashboard/api. Keys start with pq_live_. Put it in the env block of your MCP config.

Rate limit exceeded

Basic plan: 30 req/min, 5k/day. Pro plan: 120 req/min, 50k/day. See rate limits in the API docs.

Gemini CLI-specific issues

Still stuck? See the developer docs or email support@postquick.ai.

Also works with

PostQuickAI is agent-native — same API, same MCP server, same skills bundle across every major AI coding agent.

Ready to ship?

Start free trial