Post to social from Gemini CLI
Ask Gemini CLI to write a post and publish or schedule it on your connected social accounts through PostOnce.
- No credit card
- 3 min setup
Set up your connection
Connect Gemini CLI to PostOnce
Sign in with PostOnce. No API key.
- 1
Prepare your PostOnce account
You need API access on your plan; it is checked when you sign in. You can check accounts before connecting a social account; publishing needs a connected destination.
- 2
Install the PostOnce extension
Run this command in your terminal. It adds the PostOnce MCP server and its posting rules to Gemini CLI.
Terminal · Gemini CLIgemini extensions install https://github.com/postoncehq/postonce-gemini-extension - 3
Sign in with PostOnce
Start Gemini CLI and run /mcp auth postonce. Your browser opens PostOnce’s sign-in and consent page; select Allow access and return to Gemini CLI.
To disconnect later, revoke the app in Preferences → AI agents → Connected apps.
- 4
Check the connection
Run /mcp in Gemini CLI and confirm postonce shows as connected. Then ask Gemini to show your connected social accounts.
Try this promptShow my connected social accounts.
Expect account names, platforms, and IDs from
list_active_accounts. Choose actual accounts before asking the agent to publish.
Requires a PostOnce account with API access. You sign in with PostOnce; no API key.
Start with one useful action
Find your accounts
Show my connected social accounts.
Use the returned names and IDs to choose your targets. If nothing appears, connect an account in the dashboard.
Publish an update
Help me publish a product update. First show my connected accounts, then ask me to choose the destinations and confirm the exact text before publishing.
After creation, ask for the post ID and each destination’s delivery status. A queued post is still waiting to publish.
Set up crossposting
Show my connected accounts and the available crossposting options. Help me choose a supported source and destinations, then confirm the workflow before creating it.
A created workflow applies to future matching source posts. Inspect the workflow in PostOnce before relying on it.
Know what your agent can access
Connected accounts and scoped actions
PostOnce uses the permissions you approved during consent and your existing account permissions. Your available destinations come from your connected accounts; media and text requirements still vary by platform.
Media needs a supported upload path
The hosted server cannot read a file path on your computer or assume access to a chat attachment. For a first media post, use a supported publicly accessible media URL and have the agent validate the selected platform’s requirements before publishing.
Help me publish an image from a public media URL. Ask me for the URL, text, and connected destination accounts; check the platform requirements and confirm the post before creating it.
Questions before connecting
Do I need a particular PostOnce plan?
You need PostOnce API access on your plan. Your entitlement is checked during sign-in and consent. Connecting an assistant does not change your plan.
What if my agent shows no social accounts?
A successful empty account result means the connection worked. Connect or reconnect a social account in PostOnce before publishing, then ask again. Check that you authorized the intended PostOnce account and accounts:read permission.
How do I check a failed or queued post?
Ask the agent to get the post using its returned ID and inspect each target’s status and error. Review the post in the dashboard. Check the existing result before creating another post to avoid duplicates.
How do I disconnect or reconnect?
Revoke the matching app in Preferences → AI agents → Connected apps and remove the connection from your assistant. To reconnect, start its Connect flow again and review the requested permissions.