Skip to content
gongong AI
Start free
Included on every plan

Let an agent actually run your social accounts.

Gongong AI ships a Model Context Protocol server, so Claude — or any MCP client — can draft, repurpose, schedule, publish, read analytics and answer comments through the same domain services the app uses.

Get an API key — freeREST API docs
  • Every plan and the trial
  • Scoped keys
  • Idempotent writes

Connect

One config block

The server speaks MCP over HTTP and authenticates with the same scoped API key the REST API uses. Grant it only the scopes the agent needs.
mcp.json
{
  "mcpServers": {
    "gongong": {
      "url": "https://gongong.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer ${GONGONG_API_KEY}"
      }
    }
  }
}

Before you connect

  • Create a key in Settings → API keys and give it only the scopes the agent needs.
  • Keys are workspace-scoped, so an agent cannot reach another client’s content.
  • Leave approvals on while you build trust — the agent drafts, a human ships.
  • Every tool call is audit-logged with the key that made it.

Tools

Eight tools, the whole loop

These map onto the same services the portal calls, so an agent can never do something the product would not.
  • create_postCreate a post and its per-account targets, optionally scheduling in the same call.
  • generate_contentGenerate platform-tailored drafts with variants, in a brand voice.
  • repurpose_sourceTurn a URL, PDF, transcript or thread into a multi-platform post set.
  • schedule_postSchedule an existing post now, at a time, at the next free slot, or at the best time.
  • next_free_slotResolve the next open slot for an account from its queue rules.
  • get_analyticsRead cross-account or per-post analytics for a date range.
  • list_accountsList connected accounts with health, scopes and follower counts.
  • reply_to_commentReply to an engagement in the unified inbox.

What it looks like

A week of posting, in a conversation

Illustrative example of the tool sequence an agent runs. Nothing publishes without the approval rules your workspace already has.

Take the release notes at example.com/changelog and get Tuesday and Thursday covered on X and LinkedIn.

Called repurpose_source on that URL — it found three angles. Drafting two posts per network in your Acme brand voice.

Called next_free_slot for both accounts, then schedule_post. Tuesday 13:30 on X, Thursday 08:45 on LinkedIn — both your best-performing slots. All four are in review, nothing is live yet.

How did last week’s thread do?

Called get_analytics: 24k impressions, 3.1% engagement, up 40% on your median. The hook in part one carried it — I saved that pattern to your hook library.

Availability

Not an enterprise add-on

Competitors gate automation behind their top tier. That is the assumption this product was built against.
  • Free trial · MCP included
  • Starter · MCP included
  • Creator · MCP included
  • Team · MCP included
  • Agency · MCP included

Rate limits scale, access does not

Higher plans get more headroom per key, but no plan — including the fourteen-day trial — has the API or the MCP server switched off.

Point your agent at it tonight

Create a workspace, generate a scoped key, paste the config block. Fourteen days free, no card.

Start free — no cardRead the REST docs

No credit card · Cancel anytime · Every plan includes the API and the MCP server