Use your social media tools in Google Antigravity

What gets set up

The block writes three things on your computer, and nothing anywhere else:

• A skill: a document that teaches the agent how to work with your account safely. It drafts by default, checks the profiles, date, time and time zone with you before scheduling, and publishes only when you ask for it in that conversation.
• A connection: an entry in Antigravity's MCP configuration that points at your account. Antigravity 2.0, the Antigravity IDE and the Antigravity CLI read the same configuration, so the connection reaches all three.
• A permission: a rule that lets this connection's tools run without Antigravity asking you before each one. Without it, the app asks once per tool, and this connection has more than sixty.

Nothing is downloaded, so your computer has nothing to warn you about. Pasting the block again on a computer that is already set up repairs the setup instead of adding a second one.

Before you start

• Google Antigravity 2.0 on macOS, Linux or Windows, signed in.
• Access to your account's API Console: open the account menu at the top right and choose API Console.
• You do not need to create an API key first. When you approve the connection in your browser, a key is created for this application and connected for you.
• Do not paste an API key into an Antigravity or Gemini conversation. Nothing in the setup asks you for one.

Set up the connection (once per computer)

1. In the API Console, open Connect your tools and choose Google Antigravity.
2. Under Add a connection, use the copy button for your computer: macOS (which also covers Linux) or Windows.
3. Open Antigravity, start a new conversation, paste the block and send it.
4. Antigravity asks permission to run the block. The block writes to files in your home folder, which the agent's terminal sandbox does not allow, so it asks to run the block outside the sandbox. Choose Yes, allow this time. You do not need to allow it always.
5. The agent reports each step as it completes: the setup file was written, the connection was added, and the tools were allowed. It then prints three numbered steps. Do them in order.
6. Quit Antigravity completely and open it again, before you answer any other prompt. The app reads the connection, the skill and the permission only when it starts.
7. Open Settings, then Customizations, find the connection under Installed MCP Servers, and choose Authenticate. A browser window opens.
8. In the browser, review the request, leave Create a new API key for this application selected (or open Use an existing key instead to reuse a key you already have), and choose Approve. If the browser shows you a code, copy it back into Antigravity and choose Submit.
9. Start a new conversation and ask: List my social profiles.

You should see the profiles your connected key can access. If nothing is listed, open API Console, then API keys, and check that the key has access to at least one workspace.

Why the restart comes before any prompt: Antigravity keeps its permissions in memory while it runs and writes them back to disk whenever you answer a permission prompt. If you answer one before restarting, the app writes its old list over the permission the block just added, and you are back to one prompt per tool. Restart first and that cannot happen.

Add the connection by hand instead

If you prefer not to paste a block, the setup page shows the same connection as a short entry you can add yourself.

1. In Antigravity, open Settings, then Customizations, then Open MCP Config.
2. Add the entry shown under Or add the connection by hand on the setup page inside mcpServers, and save.
3. Choose Authenticate next to the new connection and approve it in the browser.
4. To stop Antigravity asking before each tool, open Settings, then General, then Permission Settings, and add the rule shown on the setup page. It has the form mcp(connection-name/*). Or choose Yes, and always allow the first time each tool asks.

The by-hand route does not install the skill, so tell the agent your ground rules yourself: create drafts by default, never publish unless asked, confirm the profiles, date, time and time zone first, and never repeat a credential back.

Using the tools

Ask for what you want in plain language: draft three posts for next week, schedule this post to Instagram and LinkedIn on Tuesday at 10am, show me last month's published messages, set up a giveaway. The agent creates drafts by default and checks with you before anything is queued, scheduled or published.

Two things to know:

• Start a new conversation after setting up. A conversation that was open before the connection existed does not see it.
• The permission you set up removes the per-tool prompt. The agent still asks you before it publishes, because the skill tells it to. Those are two different things, and the second one is deliberate.

Fix a problem

Antigravity asks permission for every tool.

• You answered a permission prompt before restarting, or the block ran before the permission could be written. Quit Antigravity completely, paste the block again, allow it to run outside the sandbox, and restart before answering anything else.
• Or add the rule by hand: Settings, then General, then Permission Settings, and add mcp(connection-name/*) using the name shown next to the connection under Customizations.

The approval prompt shows the whole block, three times.

• That is Antigravity offering to always allow that exact command, at three scopes. Choose Yes, allow this time. The block asks the agent to save it to a file and run the file, which keeps the prompt to one short line; an agent that pastes the text inline shows this longer prompt instead. Either way the setup is the same.

The agent edited files itself instead of running the block, or asked to read and write files one by one.

• Its terminal sandbox refused the block and the agent worked around it by hand. That leaves the setup incomplete. Paste the block again and, when asked, allow it to run outside the sandbox.

The connection shows Unauthorized, with an Authenticate button.

• The connection is not signed in. Choose Authenticate and approve it in the browser. This also happens if your account was briefly unreachable while Antigravity was connected: the app drops its sign-in, and one Authenticate restores it. Your permission and skill are unaffected.

The connection shows Bad Gateway.

• Your account was unreachable for a moment, usually during an update. Wait a minute and use the refresh control next to Installed MCP Servers. If it then shows Unauthorized, choose Authenticate.

The tools do not appear in a conversation.

• Quit the app completely and open it again, then start a new conversation.
• Check the connection is listed and switched on under Settings, then Customizations, then Installed MCP Servers, and that it does not show Authenticate.
• Check the skill is listed under Settings, then Customizations, then Skills. Its name begins with social-media-workflow. If it is missing, paste the block again.

The agent asks you for an API key, invents settings, or answers from the web.

• The connection is not active in that conversation. Never paste a key. Work through The tools do not appear above, then start a new conversation.

Nothing is listed when you ask for your profiles.

• The connected key has no workspace access. Open API Console, then API keys, and give the key access to at least one workspace.

It works in the desktop app but not in the Antigravity CLI.

• The connection is shared, so the CLI can reach your account once it is signed in there too. The skill is written where the desktop app and the IDE read skills; the CLI reads skills from its own folder, so tell it your ground rules in the conversation or copy the skill folder there.

For more help, open Fix a problem in the API Console.

Disconnecting

To sign Antigravity out of your account, open the setup page in the API Console and choose Disconnect on the connection. This does not revoke your API key, and every other tool that uses that key keeps working. To remove access entirely, revoke the key under API keys.

To remove the files from the computer, delete the connection under Settings, then Customizations, then Installed MCP Servers, remove the permission rule under Permission Settings, and delete the skill folder whose name begins with social-media-workflow. Your API key is not changed by removing them.