setup-mcp

Files (1)

• SKILL.md

SKILL.md (first lines)

# Setup MCP

Configure Model Context Protocol (MCP) servers for Antigravity, connecting the agent to external tools, databases, APIs, and local services.

This is a user-invoked skill (`/setup-mcp`). It walks developers through selecting transport types, configuring server definitions, injecting environment variables safely, and verifying server connectivity.

## Target Configuration Files

Antigravity discovers MCP servers from two primary configuration files:

1. **Project-level**: `.agents/mcp_config.json` (or `.agent/mcp_config.json`)
   - Located at the repository root.
   - Ideal for project-specific tools: local development databases, repository-scoped filesystem servers, repo git tools, and project mock servers.
   - Can be committed to version control to share tool configurations across the team (without committing secrets).

2. **Global**: `~/.gemini/config/mcp_config.json`
   - Located in the user's home directory.
   - Ideal for personal credentials, global developer utilities, cross-project integrations, and machine-wide services.

Both files use the standard `mcpServers` object format:

```json
{
  "mcpServers": {
    "<server-name>": {
      ...
    }
  }
}
```

## Supported Transports & Schemas

### 1. Stdio Transport (Local Process)

Used for local command-line tools, scripts, or package runners (`npx`, `uvx`, `node`, `python`). The language server spawns the child process and communicates via standard input and standard output.

**JSON Schema:**

```json
{
  "command": "executable-name-or-path",
  "args": ["arg1", "arg2"],
  "env": {
    "ENV_VAR_NAME": "value"
  },
  "cwd": "/optional/working/directory"
}
```

- `command` (string, required): Executable name on `PATH` (for example `npx`, `uvx`, `node`, `python`) or an absolute path to a binary.
- `args` (array of strings, optional): Command-line arguments passed to the executable.
- `env` (object, optional): Environment variables injected into the child process.
- `cwd` (string, optional): Working directory for process execution.

### 2. SSE Transport (Server-Sent Events)

Used for remote MCP services accessible over HTTP via Server-Sent Events.

**JSON Schema:**

```json
{
  "serverUrl": "https://mcp.example.com/sse",
  "headers": {
    "Authorization": "Bearer YOUR_TOKEN"
  }
}
```

- `serverUrl` (string, required): Full HTTP(S) URL of the remote SSE endpoint.
- `headers` (object, optional): Custom HTTP headers for authentication and routing.

### 3. HTTP Transport (Streamable HTTP Endpoint)

Used for remote MCP servers using streamable HTTP or REST endpoints.

**JSON Schema:**

```json
{
  "url": "https://mcp.example.com/api",
  "headers": {
    "Authorization": "Bearer YOUR_TOKEN",
    "X-Custom-Header": "value"
  }
}
```

- `url` (string, required): Full HTTP(S) URL of the MCP endpoint.
- `headers` (object, optional): Custom HTTP headers such as bearer tokens or API keys.

## Common Server Recipes

### PostgreSQL Server (`@modelcontextprotocol/server-postgres`)

Exposes PostgreSQL database inspection and query tools.

```json
{
  "mcpServers": {
    "postgres": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-postgres",
        "postgresql://user:password@localhost:5432/mydb"
      ]
    }
  }
}
```

Or using an environment variable for credentials:

```json
{
  "mcpServers": {
    "postgres": {

From fderuiter/agy-skills, MIT.

More from fderuiter/agy-skills