At the end of October, Google opened a plugin catalog for Antigravity, its new platform for agentic development. We built a Publora plugin, submitted it and are now waiting to hear back.
I don't write the code myself. Claude does that, while I ask questions, test things and deal with the submissions. I've become fairly familiar with the last part over the past year.
Chrome rejected our extension twice. Canva took forty-seven days and five versions. Zapier sent us through eight rounds. By now, when I hear "plugin marketplace," I expect documentation, several forms, a reviewer and at least one email explaining what we've done wrong.
Antigravity asked us to fill out a Google Form.
No sign-in, no plugin field, no timeline
It's called the "Antigravity Plugin Interest Form." You don't even need to sign in to Google to submit it.
There's no dedicated field for the plugin repository, so we put our GitHub link in the Documentation URL field. There's nowhere to provide a test account either. Google's documentation calls the catalog "curated," but I couldn't find any published review criteria or expected turnaround time.
We submitted the form and got a confirmation that it had been received. Nothing else so far.
The catalog is only a couple of weeks old, so I don't know whether this is the entire review process or just the first step. The documentation is there, although I still have questions about how some of it works. I'll write about that once we've had a chance to test more.
For now, here's what we submitted and what I managed to check.
What we actually submitted
The plugin is small: two JSON files, nine skills and a logo. The MCP server configuration is one line:
{ "serverUrl": "https://mcp.publora.com/mcp" }
There's no client ID or API key in the configuration. Antigravity uses dynamic client registration with our server, so users don't have to copy a key into the plugin.
The rest is mostly instructions. plugin.json contains three starter prompts, including "show my connected accounts" and "write a LinkedIn post about the latest change in this repo and save it as a draft."
The nine skills contain platform-specific rules and limits.
The gotchas you can already see
The first thing worth checking is OAuth discovery. The address declared in /.well-known/oauth-protected-resource has to match the MCP server address exactly. Antigravity checks this.
We also tested dynamic client registration with Antigravity's callback URL. The server returned 201 for registration, followed by a 302 redirect to the Publora sign-in page.
There were a few smaller surprises.
On the data-collection consent screen, the checkbox is selected by default. Pressing Space clears it, but pressing Enter selects it again. I found this out by trying to get past that screen.
The installer prints ERROR: logging before google.Init during startup. Despite the word ERROR, this wasn't a failure in our tests. The installation continued normally.
And when running agy in the VS Code terminal, part of the interface was invisible, including button labels. The same interface displayed correctly in the regular macOS Terminal. I spent some time looking for buttons that were technically there.
What I checked by hand
I ran agy plugin validate --strict. It passed without errors and detected all nine skills and the MCP server.
Installation worked both from a local folder and directly from GitHub. OAuth completed successfully, and Antigravity reported "signed in to mcp.publora.com."
I called list_connections and got the connected social accounts. I also checked the Bluesky skill: it loaded and correctly identified the 300-character limit.
Then I created a Mastodon draft and deleted it.
That's as far as I tested the publishing workflow. I didn't publish a live post or schedule one, so I can't say those operations work yet. I also tested the CLI, not the graphical Antigravity IDE.
I'll test the rest separately. I'd rather find the problems myself than have the first person who installs it discover them for me.
Google seems to be moving in before it's built
While testing, I noticed something else.
I tried signing in to Gemini CLI with a regular Google account and got this message: "this client is no longer supported… migrate to the Antigravity suite."
At the same time, the Gemini CLI catalog hadn't been updated since mid-October, and our extension never appeared there.
I don't know what Google's longer-term plans are for the two products. But from the outside, it's a strange moment: the new catalog is accepting submissions through a basic form, while at least one sign-in path for the older tool is already pointing users toward Antigravity.
We'd spent time trying to get into the Gemini CLI catalog. Now we're applying to another one, also run by Google. I hope we picked the right door this time.
Where we are now
The plugin is public on GitHub: publora-team/antigravity-publora, under the MIT license. We've submitted the form and are waiting.
There's no published review timeline that I could find, and we haven't been approved yet.
I checked the marketplace announcement and a catalog cache from November 16, which contained more than eighty plugins. I didn't find any social media schedulers. That might mean there's room for Publora, although it tells us nothing about whether Google will accept it.
If we're approved, I'll write a proper setup guide and add Antigravity to our documentation. For now, the plugin is available on GitHub for anyone who wants to try it.
After Chrome, Canva and Zapier, I was prepared for another long review. Instead, I've submitted a Google Form and have no idea when someone will look at it.
I keep checking my email anyway.
Have you submitted anything to the Antigravity catalog yet? Did anyone get back to you, and how long did it take?
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.