Connect Finta MCP to Google Antigravity

Direct answer: In Google Antigravity IDE, open the raw MCP configuration and add Finta with serverUrl: "https://finta.ai/mcp". Then authenticate from Settings, Customizations, choose the intended Finta organization, and keep Antigravity's default Ask permission while you run a read-only verification.

Before you connect

Check	Recommended state
Finta access	You can sign in and identify the Finta organization you intend to use.
Antigravity	A current IDE release with custom MCP server support.
Configuration scope	Global for an individual test, workspace only after team review.
Permissions	Keep unconfigured MCP tools in Antigravity's default Ask mode.

This guide covers Google Antigravity IDE. Antigravity CLI and SDK use related configuration concepts, but they have different operating surfaces and are outside this page's scope.

Google's current Antigravity MCP guide is the source of truth for navigation, configuration fields, OAuth, and permissions.

Open the Antigravity MCP configuration

In the editor's agent side panel, select the … menu.
Choose MCP Servers.
Select Manage MCP Servers.
Choose View raw config.
Decide whether to use the global file at ~/.gemini/config/mcp_config.json or the workspace file at .agents/mcp_config.json.

Use the global file for an individual proof. Use the workspace file only when the team intends to share the server definition and has reviewed which tools may be used in that project.

Add the Finta server

Add this entry under mcpServers:

{
  "mcpServers": {
    "finta": {
      "serverUrl": "https://finta.ai/mcp"
    }
  }
}

Antigravity requires serverUrl for remote Streamable HTTP and SSE servers. Do not replace it with url or httpUrl. Those legacy fields are not supported in the current remote connection schema.

Finta publishes OAuth discovery metadata and a dynamic client registration endpoint, so this setup does not require you to paste a Finta client secret or bearer token into the configuration.

Authenticate Finta

Save the configuration.
Open Antigravity Agent Settings with Cmd+, on macOS or Ctrl+, on Windows and Linux.
Go to Customizations.
Find Finta and click Authenticate.
Complete the Finta sign-in flow in the browser.
Select the Finta organization you intend to use.
Copy the returned authorization code when prompted by Antigravity.
Paste the code into the Antigravity settings panel and select Submit.
Confirm that the server reconnects.

Antigravity stores MCP OAuth tokens in its local token store and refreshes expired tokens when the provider supports refresh. Do not copy that token file into a repository, shared drive, support ticket, or prompt.

Verify the connection safely

Use this prompt before enabling broader access:

List the Finta tools available in this connection. Then search my CRM for a contact I name. Do not create, update, send, schedule, enroll, archive, or delete anything.

Review the result against four checks:

Check	What to confirm
Server	Finta appears connected in MCP management.
Tools	The tool list is visible and limited to what you intend to use.
Organization	The record comes from the correct Finta organization.
Action	No record, message, task, meeting, or automation changed.

Tool discovery proves that Antigravity can see the server inventory. It does not prove that every tool is appropriate for every prompt.

Keep Antigravity in Ask mode first

Antigravity's current permissions system places unconfigured MCP tools in Ask mode by default. Preserve that boundary during setup.

Approve one tool call at a time.
Read the tool name and arguments before approval.
Enable only the Finta server or tools required for the current task.
Do not use a wildcard permission such as mcp(*) during initial testing.
Keep relationship notes and private CRM context out of workspace artifacts unless the workspace is approved for that data.
Revoke the connection when a device, project, or role changes.

Antigravity can control whether its agent may request a tool. Finta separately controls the organization, user permissions, validation, and current server-side action boundaries.

How Finta adds relationship context

Antigravity is designed to work across code and connected tools. Finta adds the capital and relationship layer: supported CRM contacts, companies, deals, network context, documents, communication context, tasks, and workflow state.

That combination can help a team build or debug an internal capital workflow against current records instead of an exported spreadsheet. It can also prepare a source-linked relationship brief before a user decides what should happen next. A connection or model recommendation does not establish trust, consent, investor interest, or permission to contact someone.

Troubleshooting

Antigravity rejects the configuration

Confirm that the server is inside the top-level mcpServers object and uses serverUrl, not url. Validate the JSON for missing commas or duplicated keys.

Finta appears but has not authenticated

Open Agent Settings, Customizations, and choose Authenticate next to Finta. Adding the JSON entry and completing OAuth are separate steps.

The browser flow completes but Antigravity stays disconnected

Confirm that the authorization code was pasted back into the Antigravity settings panel. Refresh the server from MCP management and inspect the connection log before deleting configuration.

Tools do not appear

Reload MCP servers from the manager, confirm Finta is not disabled, and check that specific tools are not listed under disabledTools.

A read request returns the wrong records

Disconnect Finta, authenticate again, and select the intended organization. Check the record directly in Finta before treating the response as complete.

Limitations

Google controls Antigravity availability, MCP navigation, OAuth handling, local token storage, permissions, and model behavior.
This guide does not cover Antigravity CLI, Antigravity SDK, or Google AI Studio.
A connected server does not make every tool suitable for automatic approval.
Finta results depend on the selected organization, user permissions, connected sources, data quality, product configuration, and current tool inventory.
Finta MCP does not guarantee complete records, correct model reasoning, introductions, replies, commitments, or fundraising outcomes.

Related guides

Verification status: August 21, 2026. The public Finta endpoint, Finta OAuth discovery metadata, and current Google Antigravity documentation were verified. An authenticated Antigravity IDE tool receipt remains a publication proof requirement.

Explore Aurora and connect Finta