The author's own note is the most useful thing on the page: Cursor connects and shows zero tools, so the working client here is Gemini CLI on the Windows side, and that is the setup to copy. Read the tool section with the version history next to it — the four `get_connpass_user_list`, `get_connpass_user_group_list`, `get_connpass_user_events` and `get_connpass_user_presenter_events` entries documented there belong to v1, which the v2 note describes as removed.
A Deno MCP server that puts Gemini's Google-search grounding behind a tool call. It runs from a local checkout or a Docker image, and the Deno permission flags in the documented launch restrict it to a single outbound host.
- Gemini answers grounded in Google search, callable from an MCP client — the v4 line of the project is the grounding server
- A pinned network permission on the launch line: `--allow-net=generativelanguage.googleapis.com`, so the process can reach that host and nothing else
- Three runtimes for the same server — Deno directly, a Node build via `npm ci` and `npm run build`, or Docker
- Repeatable checks: `deno task test:tokyo`, `deno task test:google_search` and `deno task test:google_search_simple`, plus a one-line `tools/list` probe you can pipe into the server
A Gemini API key as `GEMINI_API_KEY`, supplied through an `--env-file` or `-e` on the Docker run. Deno is the recommended runtime, and the client entry passes `--allow-net=generativelanguage.googleapis.com`, `--allow-read` and `--allow-env` alongside the env file. Docker is the alternative — `docker compose run --rm deno-gemini-grounding-mcp-server` as the client command, since MCP needs stdin and stdout. The npm package is `deno-gemini-grounding-mcp-server` 0.2.4, and the README marks `npx` as discouraged on supply-chain grounds.
One command plus a key — docker run -e GEMINI_API_KEY=XXXXXXXXXXXXXXXX deno-gemini-grounding-mcp-server, then supply credentials