Remote MCP

Use `gitinit` directly from AI coding agents.

The hosted MCP server exposes the same generator that powers the website. Agents can discover stacks, preview scaffold shape, generate a scaffold, and download the same zip artifact a human would get from the UI.

Endpoint

https://gitinit.arnayshukla.com/api/mcp

Transport

Streamable HTTP

Typical agent flow

1. Call `list_stacks` or `list_options` to understand the available surface.

2. Call `preview_scaffold` to inspect the worktree and visible source wiring.

3. Call `generate_scaffold` to get a short-lived artifact URL.

4. Download the generated zip from the returned URL.

Notes

Artifact URLs are intentionally short-lived and should be fetched promptly by the calling agent.

Clients only need the hosted MCP endpoint: https://gitinit.arnayshukla.com/api/mcp.

If your agent supports instructions such as `AGENTS.md`, add a short rule telling it to use the `gitinit` MCP server whenever it needs to scaffold a new backend service.

Tool surface

list_stacks

Returns the supported stack lanes and their native run/test commands.

list_options

Returns the supported categories and options for a selected stack.

preview_scaffold

Builds a structured worktree preview, run/test commands, and visible wiring summary.

generate_scaffold

Returns scaffold metadata and a short-lived URL for downloading the generated zip.

Client setup examples

Start with the generic remote MCP shape, then use the client-specific example that matches your coding agent.

Generic remote MCP config

{
  "mcpServers": {
    "gitinit": {
      "url": "https://gitinit.arnayshukla.com/api/mcp"
    }
  }
}

Cursor

Cursor reads MCP config from `~/.cursor/mcp.json` or project-local `.cursor/mcp.json`.

{
  "mcpServers": {
    "gitinit": {
      "url": "https://gitinit.arnayshukla.com/api/mcp"
    }
  }
}

Codex CLI

codex mcp add gitinit --url https://gitinit.arnayshukla.com/api/mcp

Codex config.toml

Codex can also be configured directly through `~/.codex/config.toml`. The CLI and IDE extension share the same MCP config.

[mcp_servers.gitinit]
url = "https://gitinit.arnayshukla.com/api/mcp"

Antigravity

Antigravity commonly manages MCP servers through a `mcp_config.json` file or its managed MCP editor.

{
  "mcpServers": {
    "gitinit": {
      "serverUrl": "https://gitinit.arnayshukla.com/api/mcp"
    }
  }
}

Example scaffold request

This is the same request shape the hosted MCP tool surface accepts for `preview_scaffold` and `generate_scaffold`.

{
  "request": {
    "stack": "java-spring-maven",
    "projectName": "inventory-service",
    "identifiers": {
      "groupId": "com.example"
    },
    "selections": {
      "database": "postgres",
      "cache": "redis",
      "messaging": "kafka",
      "tracing": "opentelemetry",
      "auth": "jwt",
      "authorization": "rbac",
      "rateLimit": "inMemory"
    }
  }
}