gemini-pro-mcp 0.1.4__tar.gz

gemini_pro_mcp-0.1.4/.gitattributes

@@ -0,0 +1,4 @@
+* text=auto eol=lf
+*.png binary
+*.gif binary
+*.mp4 binary

gemini_pro_mcp-0.1.4/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,25 @@
+name: Bug report
+description: Something does not work
+labels: [bug]
+body:
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened?
+      description: The tool you called, what you expected, and what you got (error text helps).
+    validations:
+      required: true
+  - type: input
+    id: client
+    attributes:
+      label: MCP client
+      placeholder: Claude Code 2.x, Claude Desktop, Cursor...
+  - type: input
+    id: os
+    attributes:
+      label: OS and Python version
+  - type: textarea
+    id: notes
+    attributes:
+      label: Anything else
+      description: Never paste API keys, cookies or other secrets.

gemini_pro_mcp-0.1.4/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Questions and ideas
+    url: https://github.com/Muzaqil555/gemini-pro-mcp/discussions
+    about: Ask a question or share an idea in Discussions.
+  - name: Report a security issue
+    url: https://github.com/Muzaqil555/gemini-pro-mcp/security/advisories/new
+    about: Please report vulnerabilities privately, not in a public issue.

gemini_pro_mcp-0.1.4/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,14 @@
+name: Feature request
+description: An idea for a new tool or improvement
+labels: [enhancement]
+body:
+  - type: textarea
+    id: idea
+    attributes:
+      label: What would you like to do from Claude?
+    validations:
+      required: true
+  - type: textarea
+    id: how
+    attributes:
+      label: Which Google feature or API would it use?

gemini_pro_mcp-0.1.4/.github/dependabot.yml

@@ -0,0 +1,17 @@
+version: 2
+updates:
+  - package-ecosystem: uv
+    directory: /
+    schedule:
+      interval: weekly
+    groups:
+      python:
+        patterns: ["*"]
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: monthly
+  - package-ecosystem: docker
+    directory: /
+    schedule:
+      interval: monthly

gemini_pro_mcp-0.1.4/.github/pull_request_template.md

@@ -0,0 +1,7 @@
+## What and why
+
+## How I checked it
+
+- [ ] `uv run pytest`
+- [ ] `uv run ruff check . && uv run ruff format --check .`
+- [ ] Tried it in an MCP client (say which tool and what happened)

gemini_pro_mcp-0.1.4/.github/workflows/ci.yml

@@ -0,0 +1,40 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        python: ["3.10", "3.13"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: ${{ matrix.python }}
+      - run: uv sync
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run pytest -q
+
+  # The image MCP directories (Glama) run: it must start and answer tools/list.
+  docker:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - run: docker build -t gemini-pro-mcp .
+      - name: Server starts and lists its tools
+        run: |
+          printf '%s\n' \
+            '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"ci","version":"0"}}}' \
+            '{"jsonrpc":"2.0","method":"notifications/initialized"}' \
+            '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \
+            | (cat; sleep 15) | timeout 90 docker run -i --rm gemini-pro-mcp > out.jsonl || true
+          cat out.jsonl
+          grep -q '"gemini_ask"' out.jsonl

gemini_pro_mcp-0.1.4/.github/workflows/codeql.yml

@@ -0,0 +1,24 @@
+name: CodeQL
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  schedule:
+    - cron: "17 4 * * 1"
+
+jobs:
+  analyze:
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      contents: read
+    strategy:
+      matrix:
+        language: [python, actions]
+    steps:
+      - uses: actions/checkout@v7
+      - uses: github/codeql-action/init@v4
+        with:
+          languages: ${{ matrix.language }}
+      - uses: github/codeql-action/analyze@v4

gemini_pro_mcp-0.1.4/.github/workflows/publish.yml

@@ -0,0 +1,67 @@
+# Publishes to PyPI when a GitHub release is published, with PyPI trusted
+# publishing (no token stored here). One-time setup on pypi.org: Account ->
+# Publishing -> add a pending publisher for project "gemini-pro-mcp",
+# owner "Muzaqil555", repository "gemini-pro-mcp", workflow "publish.yml",
+# environment "pypi". Then set the repository variable PYPI_PUBLISH=true
+# (Settings -> Secrets and variables -> Actions -> Variables); until then,
+# releases skip this job instead of failing.
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+jobs:
+  publish:
+    if: vars.PYPI_PUBLISH == 'true' || github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+      - run: uv sync
+      - run: uv run pytest -q
+      - run: uv build
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+  # Lists the release in the official MCP Registry (server.json) once the
+  # PyPI upload is live. The registry checks the "mcp-name:" line in README.md
+  # and authenticates this repository with GitHub OIDC, so no secret is needed.
+  mcp-registry:
+    needs: publish
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+    env:
+      MCP_PUBLISHER_VERSION: v1.8.8
+    steps:
+      - uses: actions/checkout@v7
+      - uses: sigstore/cosign-installer@6f9f17788090df1f26f669e9d70d6ae9567deba6 # v4.1.2
+      - name: Download and verify mcp-publisher
+        run: |
+          set -euo pipefail
+          archive="mcp-publisher_linux_amd64.tar.gz"
+          base_url="https://github.com/modelcontextprotocol/registry/releases/download/${MCP_PUBLISHER_VERSION}"
+          curl -fsSL -o "$archive" "$base_url/$archive"
+          curl -fsSL -o "$archive.sigstore.json" "$base_url/$archive.sigstore.json"
+          cosign verify-blob \
+            --bundle "$archive.sigstore.json" \
+            --certificate-identity "https://github.com/modelcontextprotocol/registry/.github/workflows/release.yml@refs/tags/${MCP_PUBLISHER_VERSION}" \
+            --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
+            "$archive"
+          tar xzf "$archive" mcp-publisher
+      - name: Wait for the PyPI release
+        run: |
+          version=$(jq -r .version server.json)
+          for i in $(seq 1 30); do
+            curl -fsS "https://pypi.org/pypi/gemini-pro-mcp/$version/json" >/dev/null && exit 0
+            sleep 10
+          done
+          echo "gemini-pro-mcp $version is not on PyPI yet" >&2; exit 1
+      - run: ./mcp-publisher login github-oidc
+      - run: ./mcp-publisher publish

gemini_pro_mcp-0.1.4/.gitignore

@@ -0,0 +1,8 @@
+.venv/
+__pycache__/
+*.pyc
+.env
+dist/
+.pytest_cache/
+.ruff_cache/
+*.mp4

gemini_pro_mcp-0.1.4/CHANGELOG.md

@@ -0,0 +1,39 @@
+# Changelog
+
+## 0.1.4
+
+- Published on PyPI (`uvx gemini-pro-mcp`) and listed in the official MCP Registry as `io.github.Muzaqil555/gemini-pro-mcp`.
+- 0.1.3 was a Glama-only build of 0.1.2 and has no GitHub release.
+
+## 0.1.2
+
+- Every tool description now says when to use the tool rather than a related one, what it costs or changes, the valid values of each parameter with an example, and what it returns: `gemini_research`, `gemini_code`, `gemini_agents`, `gemini_models`, `jules_sources`, `jules_start`, `video_generate`, `video_check` and `image_generate`.
+
+## 0.1.1
+
+- Clearer tool descriptions for `gemini_ask`, `video_stitch`, `google_pro_benefits` and the `jules_*` tools: when to use each one, what it costs and what it returns.
+- `setup` and `doctor` commands, translations (Turkish, Russian, Azerbaijani), a comparison with other Gemini MCP servers, a Dockerfile, a Code of Conduct and a security policy.
+- Dependabot and CodeQL code scanning.
+
+## 0.1.0
+
+- `gemini_ask`, `gemini_research` and `gemini_models` run Gemini through the Antigravity CLI on your Google AI Pro/Ultra plan, read-only and sandboxed.
+- `video_generate`, `video_edit` and `video_check` use Gemini Omni Flash through the Gemini API.
+- `image_generate` creates and edits images with Nano Banana 2.1, 2 Lite and Pro.
+- Experimental Flow tools: `flow_generate`, `flow_approve`, `flow_reject`, `flow_collect` and `flow_status`. They drive flow.google.com in your own signed-in Chrome profile (`flow-login`), and spending credits always takes a separate `flow_approve` call.
+- `flow_make_video` and `flow_job` make a video of any length: Gemini writes a shot list, Flow generates each clip, and the clips are joined into one file.
+- `video_stitch` joins clips locally with a bundled ffmpeg.
+- `GEMINI_PRO_AUTO_APPROVE=1` is for users who pre-approve spending.
+- Every Flow feature is now reachable: `flow_tools` and `flow_open_tool` open any Flow tool, and `flow_page` and `flow_act` read and operate any Flow page or tool frame, including clicks, typing, uploads and downloads.
+- `flow_make_video` is more reliable: it saves its shot plan to `plan.json` and resumes from the clips already made. A failed clip is retried up to 3 times; Flow does not charge for failures.
+- The whole Google AI Pro plan is now covered: `google_pro_benefits` (a catalog of what the plan includes and how to reach each part), `gemini_app` and `gemini_app_result` (the Gemini app: 4 Argon, Deep Research, images, Veo, music, Canvas, files), `google_ai_mode` (AI Mode in Search), and `google_page` / `google_act` (any Google AI site, like a person; these replace `flow_page` / `flow_act`).
+- `GEMINI_PRO_ENABLE_BROWSER=1` enables all browser tools. Each site gets its own tab and lock, and Chrome no longer pauses background tabs.
+- Gemini Notebook (formerly NotebookLM): `notebook_list`, `notebook_create`, `notebook_add_sources`, `notebook_ask`, `notebook_studio` (Audio and Video Overviews, slide decks, mind maps, reports, flashcards, quizzes, infographics, data tables).
+- Antigravity: `gemini_code` lets Gemini edit a local folder (accept-edits mode, sandboxed terminal), and `gemini_agents` lists custom agents.
+- Jules: `jules_sources`, `jules_start`, `jules_status`, `jules_sessions`, `jules_approve_plan` and `jules_message` use the official REST API (`JULES_API_KEY`).
+- Fixed: concurrent browser connections reset Chrome's download handling and left 0-byte clips. The server now shares one connection, checks every download and falls back to the signed file URL.
+- Fixed: when Flow queues a clip at busy times, `flow_make_video` now waits for the clip it already paid for instead of generating it again.
+- Fixed: `flow_status` timed out after Flow put the Google account bar inside its plan badge. It now clicks the plan chip itself, and an unreadable balance shows as "unknown" instead of failing the check.
+- Setup instructions for Codex, the Antigravity CLI and the Gemini CLI.
+- `gemini-pro-mcp setup` adds the server to every MCP client it finds (Claude Code, Codex, Antigravity CLI, Gemini CLI). It uses each client's `mcp add` command where there is one, and otherwise edits the config file, keeping everything else in it and saving a backup. `--browser` and `--auto-approve` set the matching settings.
+- `gemini-pro-mcp doctor` checks the Antigravity sign-in, the API keys, Chrome and the Flow profile, and says how to fix each problem it finds. With `--flow` it also opens Flow and reads the credits.

gemini_pro_mcp-0.1.4/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+mhesenli7@std.beu.edu.az.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

gemini_pro_mcp-0.1.4/CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# Contributing
+
+Thanks for helping! Issues, ideas and pull requests are all welcome.
+
+## Setup
+
+```bash
+git clone https://github.com/Muzaqil555/gemini-pro-mcp
+cd gemini-pro-mcp
+uv sync
+uv run pytest
+uv run ruff check . && uv run ruff format --check .
+```
+
+Try your local copy in Claude Code:
+
+```bash
+claude mcp add gemini-pro-dev -- uv --directory /path/to/gemini-pro-mcp run gemini-pro-mcp
+```
+
+## Ground rules
+
+- **Never handle user credentials.** The server must not type, store or log passwords, cookies or API keys. Sign-in is always done by the user.
+- **No stealth.** Do not add fingerprint spoofing, CAPTCHA solving or any other bot-detection evasion. If Google blocks automation, the user decides what to do.
+- **Paid calls stay explicit.** Every tool that spends money or credits must say so in its description, so the model asks the user first.
+- **Tests without network.** Unit tests use fakes (see `tests/`). Calls to the real API or `agy` belong in manual checks, not in CI.
+
+## Where things live
+
+| Path | What |
+|---|---|
+| `src/gemini_pro_mcp/server.py` | Builds the server and the CLI (`serve`, `setup`, `doctor`, `flow-login`) |
+| `src/gemini_pro_mcp/agy.py` | `gemini_*` tools through the Antigravity CLI |
+| `src/gemini_pro_mcp/media.py` | Gemini API video and image tools |
+| `src/gemini_pro_mcp/jules.py` | `jules_*` tools (official API) |
+| `src/gemini_pro_mcp/google_web.py` | `gemini_app`, `google_ai_mode`, `google_page`, `google_act` |
+| `src/gemini_pro_mcp/notebook.py` | `notebook_*` tools |
+| `src/gemini_pro_mcp/flow/` | `flow_*` tools and the shared Chrome connection |
+| `src/gemini_pro_mcp/install.py` | `setup` and `doctor` |
+
+## Adding a tool
+
+1. Write it as an `async def` inside the `register()` function of the module it belongs to. The docstring becomes the tool description the model reads, so say what the tool does, what it costs and what it returns.
+2. Decorate it with `@mcp.tool(annotations=...)`. Tools that spend money or credits use the module's `paid` helper instead, which marks them and adds the confirmation sentence.
+3. Add its name to `BASE` or `FLOW` in `tests/test_server.py`, and test its logic with fakes in `tests/`.
+4. List it in the README's tool tables.
+
+## Good first issues
+
+Open tasks for newcomers are labelled [`good first issue`](https://github.com/Muzaqil555/gemini-pro-mcp/labels/good%20first%20issue): Lyria music, Flow images, Deep Research reports, testing on macOS and Linux, README translations and support for more Google AI sites. Comment on one to take it. Questions are welcome in [Discussions](https://github.com/Muzaqil555/gemini-pro-mcp/discussions).
+
+## Pull requests
+
+Keep them focused, add or update tests, and describe how you checked the change, for example "generated one 720p video" or "ran gemini_research".

gemini_pro_mcp-0.1.4/Dockerfile

@@ -0,0 +1,14 @@
+# Runs the MCP server over stdio, e.g. for MCP directories that start it and
+# list its tools. The subscription tools still need the Antigravity CLI and the
+# browser tools need a signed-in Chrome, so for real use install it locally
+# with `uvx ... gemini-pro-mcp setup` (see the README).
+FROM ghcr.io/astral-sh/uv:python3.12-bookworm-slim
+
+WORKDIR /app
+ENV UV_COMPILE_BYTECODE=1 UV_LINK_MODE=copy
+
+COPY pyproject.toml uv.lock README.md LICENSE ./
+COPY src ./src
+RUN uv sync --frozen --no-dev
+
+ENTRYPOINT ["uv", "run", "--frozen", "--no-dev", "gemini-pro-mcp"]

gemini_pro_mcp-0.1.4/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Muzaqil Hesenli
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.