Choose your appLesson 6 of 9 · 6 steps

Connect Antigravity

Use the browser sign-in bridge and a compact tool list.

Video coming soon

Your next step is ready.

Follow the complete written guide below.
The video will join it here when it’s ready.

Start the written lesson

Before you start

Complete Install EMCP Free and Pro and Connect an AI agent.
Have the named app installed with MCP support available.

Let’s do this, step by step.

Step 01

Start the four-step wizard

Open EMCP Tools → Setup → Connection → MCP. Check Server status. In Step 1 select Antigravity; in Step 2 choose the sign-in method used below. OAuth needs HTTPS and OAuth sign-in enabled under Advanced settings, then Save.

Start on the intended WordPress site. In Connection, choose Antigravity, then choose how to sign in. The following instructions are shown in Step 3. Keep the wizard open so we can verify the first call in Step 4.

Step 02

Use Compact mode

Open EMCP Tools → Tools, enable Compact tool mode, and save.

This gives Antigravity a smaller advertised tool list. The underlying enabled actions remain available. Client limits can change, so we will verify the connection instead of assuming a fixed number.

Step 03

Prepare the local bridge

Install a supported Node.js runtime on the computer running Antigravity. Open its MCP configuration.

The small bridge runs on your computer and opens the sign-in page. The EMCP guide requires Node 18 or newer; use a maintained version compatible with your app.

Step 04

Add the generated configuration

Copy the Antigravity OAuth configuration from Connection. It runs npx with mcp-remote and your full server URL. Preserve other servers.

Save the generated block rather than typing every bracket yourself. This route passes the complete endpoint to the bridge, not just the homepage.

Step 05

Sign in and reconnect

Start the connection, approve WordPress in the browser, and inspect its tools.

Seeing list-tools, get-tool-schema, and call-tool is expected. Ask the AI to discover the page-listing action through those tools. If none appear, follow connection diagnosis.

Step 06

Confirm Step 4 with a real request

After adding the connection, click I’ve added it, continue in WordPress. Reload the app and send the read-only prompt. Check the wizard’s successful first call and compare records with Pages. On failure or No call yet, inspect the reason and Run a server test.

Return to WordPress and continue to Test the connection. Reload your app, then ask it to list pages. Check the wizard’s result and the actual page titles. A server test is a useful diagnosis if the call fails, but it does not prove the app completed its request.

Copy and adapt

                    Identify the connected WordPress site URL. List accessible pages with titles, IDs and status. Do not create, edit or delete anything.

You’re done when…

The app reads real page records from the intended site without changing anything.

Keep the reference handy.

The docs cover tool details and requirements for this lesson.

You only need the guide for the app or builder you use. Ready to build? Try an Elementor draft or use Gutenberg.