Skip to main content
Glama
Flexcrit

Antigravity MCP Bridge

by Flexcrit
OverviewSchemaRelated ServersScoreDiscussions
Local

Antigravity MCP Bridge

A TypeScript-based Model Context Protocol (MCP) server template wired into the Antigravity agentic environment. It exposes tools over a stdio transport and ships with a ready-to-import SQLite skill for local database access.

Prerequisites

Requirement

Version

Node.js

≥ 18

npm

≥ 9

Antigravity

latest

Related MCP server: MCP TypeScript Starter

Project Structure

antigravity-mcp-bridge/
├── src/
│   └── server.ts          # MCP server — stdio transport + tools
├── skills/
│   └── sqlite_skill.json  # Antigravity Global Skill definition
├── dist/                  # Compiled JS output (after build)
├── auto_bridge.sh         # Detects MCP configs & writes env settings
├── tsconfig.json
├── package.json
└── README.md

1 · Starting the MCP Server

Build & run (recommended)

# Install dependencies (first time only)
npm install

# Compile TypeScript → dist/
npm run build

# Start the server
node dist/server.js

The server writes a startup message to stderr and listens for MCP messages on stdin/stdout.

Development mode (ts-node)

npx ts-node src/server.ts

Auto-bridge setup

Run auto_bridge.sh once after cloning (or whenever your MCP config changes). It scans well-known config locations, detects your Node environment, and writes .env.mcp plus a descriptor into ~/.antigravity/mcp/.

chmod +x auto_bridge.sh   # already done if you followed setup
./auto_bridge.sh

2 · Importing the SQLite Skill into Antigravity Manager

  1. Open the Antigravity desktop app and navigate to the Manager View (sidebar → 🧩 Manager).

  2. Click Import Skill (top-right of the Skills panel).

  3. In the file picker, navigate to:

    /path/to/antigravity-mcp-bridge/skills/sqlite_skill.json

    and select it.

  4. Antigravity will validate the skill schema and display a "SQLite Database Connector" card under the Data Sources category.

  5. Click Configure on the card and fill in the required field:

    • SQLite Database Path — absolute path to your .db / .sqlite file, e.g. /Users/sameer/data/myapp.db

  6. Click Save & Activate. The skill is now globally available to all agents.

Tip: You can activate / deactivate the skill at any time from the Manager View without removing the import.

3 · Testing the Connection with the Built-in Browser

Antigravity ships a built-in MCP Inspector browser that lets you call tools interactively.

Step-by-step

  1. Start the MCP server (see §1 above) so it is listening.

  2. In Antigravity, open Settings → MCP Servers and click + Add Server.

  3. Set:

    • Transport: stdio

    • Command: node /path/to/antigravity-mcp-bridge/dist/server.js

  4. Click Connect. The status indicator should turn green.

  5. Navigate to Tools tab inside the MCP Inspector.

  6. Select the system_status tool, leave the input blank (no parameters), and click Run.

  7. The response pane should display a JSON payload similar to:

    {
  "currentTime": "2026-04-23T02:19:15.000Z",
  "platform": "darwin",
  "release": "24.4.0",
  "architecture": "arm64",
  "hostname": "MacBook-Pro",
  "cpus": 10,
  "totalMemoryMB": 16384,
  "freeMemoryMB": 4096,
  "uptime": "3h 42m",
  "nodeVersion": "v22.0.0"
}

  8. To test the SQLite skill, ensure the skill is imported and configured (§2), then ask an agent: "List all tables in my database." The agent will invoke sqlite_list_tables via the MCP bridge automatically.

Available Tools

Tool

Description

system_status

Returns current UTC time and OS details

sqlite_query

Execute a read-only SQL SELECT

sqlite_execute

Execute a write SQL statement

sqlite_list_tables

List all tables in the SQLite DB

sqlite_describe_table

Describe columns of a table

Scripts

npm run build    # tsc — compile src/ → dist/
npm run dev      # ts-node src/server.ts (watch mode)
npm run start    # node dist/server.js

Adding More Tools

Open src/server.ts and call server.tool(name, description, inputSchema, handler):

server.tool(
  "my_new_tool",
  "Does something useful.",
  { param: z.string().describe("An example parameter") },
  async ({ param }) => ({
    content: [{ type: "text", text: `You passed: ${param}` }],
  })
);

Rebuild with npm run build and reconnect in Antigravity.

License

MIT

Created by:

Sameer Abrar, Flexcrit Inc

Available Tools

1 tool
system_statusA

Returns the current UTC time and key operating system details.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It indicates a read-only operation ('returns') but does not disclose any further behavioral traits such as side effects, permissions, or rate limits. For a simple query tool, this is adequate but not exemplary.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is efficient and front-loaded with the core action. No extraneous words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no sibling tools, the description is the sole source of output information. While it identifies the data types (time, OS details), it lacks specifics such as time format or which details are included. This is adequate but leaves gaps for an agent expecting structured output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, and schema coverage is trivially 100%. The description does not need to add parameter info. Following the baseline rule for zero parameters, a score of 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns current UTC time and key operating system details. The verb 'returns' and specific resources (UTC time, OS details) make the purpose unambiguous, and with no sibling tools, differentiation is unnecessary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving system status information without explicit when-not or alternatives. Since there are no sibling tools, the guidance is sufficient; however, a brief note about when to use (e.g., for diagnostics) would be more explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools.

Naming Consistency5/5

The single tool uses a clear snake_case name that is consistent with itself and readable.

Tool Count1/5

A single trivial tool (system_status) is far too few for a server named 'Bridge'; it feels incomplete and under-scoped.

Completeness2/5

The server only provides current time and basic OS details, missing common system metrics like CPU, memory, or disk usage, which are significant gaps.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • my-mcp-server

    junhang-dev
    F
    license
    Not graded
    quality
    D
    maintenance
    A TypeScript MCP server boilerplate with example tools (calculator, greet) and resources (system info), ready for extension and integration with Cursor.

  • mcp-blanko

    StenSeegel
    F
    license
    C
    quality
    D
    maintenance
    A TypeScript template for building MCP servers with placeholder tools and dual transport support (stdio + SSE).
    5

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Flexcrit/Antigravity-MCP-Bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server