Gemini CLI connects to remote MCP servers for terminal-based form ops
Lovanaut's post walks through connecting Gemini CLI to a remote HTTP MCP server — using FORMLOVA as the example — covering OAuth authentication, config scoping, and prompting strategies for creating and reviewing draft forms without leaving the terminal.
Score breakdown
The post provides a concrete, step-by-step path for wiring Gemini CLI to any remote HTTP MCP server with OAuth, demonstrating that the CLI can coordinate real product operations — not just generate text — from the terminal.
- 01The post uses FORMLOVA's MCP server at `https://formlova.com/api/mcp` as the remote HTTP MCP example.
- 02The Gemini CLI command to add the server is `gemini mcp add --transport http formlova https://formlova.com/api/mcp`.
- 03Project-scope vs. user-scope is controlled with the `-s user` flag; the post recommends project scope for a first test.
Lovanaut's post on Dev.to focuses narrowly on the Gemini CLI setup path for connecting to a remote HTTP MCP server, using FORMLOVA (`https://formlova.com/api/mcp`) as the example. The core command is `gemini mcp add --transport http formlova https://formlova.com/api/mcp`, with an optional `-s user` flag to make the server available across all projects rather than just the current one. For users who manage config directly, the correct key is `httpUrl` inside `mcpServers` — the post explicitly warns against using `command` (reserved for local stdio servers) or `url` (reserved for SSE endpoints).
OAuth is handled through Gemini CLI's built-in support for remote MCP server authentication.
OAuth is handled through Gemini CLI's built-in support for remote MCP server authentication. Running `/mcp auth formlova` triggers endpoint discovery, opens a local browser for the auth flow, and stores tokens for reuse. The post notes this requires a local browser and localhost callback, making it incompatible with headless containers or remote SSH sessions without browser access.
On the prompting side, the post advocates for prompts that go beyond a bare field list — including operational requirements like response handling, confirmation email copy, mobile comfort, and filtering logic — and that explicitly keep the first write action unpublished. A follow-up review prompt is recommended to check mobile input friction, required fields, confirmation copy, and workflow clarity before publishing. The post frames the preview URL and concrete review findings as the meaningful signal that the MCP loop is working correctly, rather than a text-only checklist response.
Key facts
- 01The post uses FORMLOVA's MCP server at `https://formlova.com/api/mcp` as the remote HTTP MCP example.
- 02The Gemini CLI command to add the server is `gemini mcp add --transport http formlova https://formlova.com/api/mcp`.
- 03Project-scope vs. user-scope is controlled with the `-s user` flag; the post recommends project scope for a first test.
- 04In direct config, remote HTTP servers must use `httpUrl` — not `command` (stdio) or `url` (SSE).
- 05OAuth authentication is initiated with `/mcp auth formlova`; the CLI handles endpoint discovery, browser flow, and token storage.
- 06The auth flow requires a local browser and localhost callback, so it does not work in headless containers or remote SSH sessions without browser access.
- 07The post recommends prompting the model to keep forms unpublished and return a preview URL, then running a structured review before publishing.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 16, 2026 · 23:11 UTC. How this works →