gitpr-cli 0.0.26__tar.gz → 0.0.28__tar.gz

{gitpr_cli-0.0.26/gitpr_cli.egg-info → gitpr_cli-0.0.28}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gitpr-cli
-Version: 0.0.26
+Version: 0.0.28
 Summary: Automação de PRs, Commits e Code Review com IA (Gemini e DeepSeek)
 Author-email: Natan Fiuza <contato@natanfiuza.dev.br>
 Requires-Python: >=3.10
@@ -14,12 +14,20 @@ Requires-Dist: cryptography
 Requires-Dist: pyyaml
 Requires-Dist: textual
 Requires-Dist: requests
+Requires-Dist: mcp>=1.0.0
 Dynamic: license-file
 
+
 # **GitPR CLI 🚀**
 
+<p align="center">
+  <img src="https://raw.githubusercontent.com/natanfiuza/gitpr/main/docs/logo.png" alt="GitPR Logo" width="150">
+</p>
+
 GitPR CLI is a command-line automation tool that uses **Google Gemini** and **DeepSeek** artificial intelligence to analyze your code changes (git diff) or entire files. The tool automatically generates commit messages in the *Conventional Commits* standard, detailed Pull Request descriptions, and deep Code Reviews aimed at reducing technical debt.
 
+🌐 **Website:** [gitpr.natanfiuza.dev.br](https://gitpr.natanfiuza.dev.br/) · 📂 **Repository:** [github.com/natanfiuza/gitpr](https://github.com/natanfiuza/gitpr)
+
 ## **🛠️ Technologies and Libraries Used**
 
 This project was developed in Python and uses the following main libraries:
@@ -33,6 +41,7 @@ This project was developed in Python and uses the following main libraries:
 * [**PyYAML**](https://pyyaml.org/): Used to read and process the custom static analysis rules from the `.gitpr.linter.yml` file.
 * [**Textual**](https://textual.textualize.io/): Powerful library for creating Terminal Graphical Interfaces (TUI), used in the interactive issue generation and editing panel.
 * [**Requests**](https://pypi.org/project/requests/): Elegant and robust library for HTTP requests, used to communicate with the GitHub REST API.
+* [**MCP**](https://pypi.org/project/mcp/): Official Python SDK for the Model Context Protocol, enabling GitPR to integrate directly with AI-powered editors and IDEs.
 
 ----
 
@@ -130,6 +139,8 @@ You can pass the following *flags* for specific actions:
 * `--lang <code>`: Forces the interface language for this execution (e.g.: `en_us`, `pt_br`). Overrides `GITPR_LANG` in `.env` without persisting the change.
 * `-ch` or `--chat`: Opens the **Interactive Pair Programming Chat** — a TUI terminal where the AI sees your current diff and maintains a contextual conversation. Features memory per branch, slash commands (`/explain`, `/tests`, `/optimize`, `/clear`), auto-patching (F5), diff refresh (F2), and session export (F6).
 * `-l` or `--linter`: Runs **only the local static linter** (no AI calls). Ideal for use in CI/CD pipelines to block non-compliant code.
+* `--mcp`: Starts GitPR as an **MCP server** (Model Context Protocol) on stdio transport. Enables integration with VS Code, Cursor, Claude Desktop, and other MCP-compatible editors — exposing all GitPR AI capabilities as tools directly inside your IDE. Also available as the standalone `gitpr-mcp` command.
+* `--install`: **Interactive Setup Wizard.** Runs a guided 4-step setup: downloads skill templates, installs Git hooks, configures MCP for detected editors, and checks/requests your AI provider API key. Each step asks for confirmation before proceeding.
 * `-ih` or `--installhooks`: Automatically installs **local Git Hooks** (`pre-commit` and `prepare-commit-msg`) in your repository.
 * `-s` or `--skill`: Creates the AI context template files (`.gitpr.commit.md`, `.gitpr.pr.md`, `.gitpr.review.md`, `.gitpr.filereview.md`, `.gitpr.issue.md`, `.gitpr.blame.md`) and the Linter (`.gitpr.linter.yml`) at the project root.
 * `-is` or `--issue`: Automatically generates a draft of a **standardized Issue** and opens an interactive interface (TUI) for editing or direct submission via REST API. This feature has **3 context engines** depending on the command combination:
@@ -140,6 +151,14 @@ You can pass the following *flags* for specific actions:
 * `-u` or `--update`: Checks and installs the latest version of GitPR (Auto-Updater).
 
 > **⚙️ Technical Note (--hook):** GitPR has a hidden flag `--hook <file>` that is triggered exclusively by the Git Hooks system in the background. It allows the AI to inject the suggested message directly into Git's temporary file, without cluttering your terminal.
+>
+> **⚙️ Technical Note (--pre-save):** GitPR has a hidden debug flag `--pre-save` that can be combined with any AI command (e.g.: `gitpr -c --pre-save`). Before each AI call, it saves the full payload that will be sent to the model (system instruction + prompt + character counters) to a `_{action}-{datetime}.json` file in the current folder, and then proceeds normally. Useful for inspecting very large prompts. Note: when the response comes from the local cache, no call is made and no file is generated.
+
+### 📦 Huge Diffs (Map-Reduce)
+
+When your diff is too large for a single AI call (over ~90k estimated tokens), GitPR automatically splits it into batches by file, asks the AI for a technical summary of each part (Map), and unifies everything into the final commit message, review, or PR description (Reduce). No flags needed — it activates on demand and shows the progress in the console.
+
+📚 Full documentation: [docs/map-reduce-diff.md](https://github.com/natanfiuza/gitpr/blob/main/docs/map-reduce-diff.md)
 
 ## 🛡️ Local Linter (Static Analysis)
 
@@ -194,7 +213,64 @@ GitPR automatically detects your system language and displays messages in your n
 
 To force a specific language, set `GITPR_LANG=pt_br` or `GITPR_LANG=en` in `~/.gitpr/.env`.
 
-> 📖 **Full developer guide:** [docs/i18n_explanation.md](docs/i18n_explanation.md) — architecture, usage patterns, circular import precautions, and how to add new languages.
+> 📖 **Full developer guide:** [docs/i18n_explanation.md](https://github.com/natanfiuza/gitpr/blob/main/docs/i18n_explanation.md) — architecture, usage patterns, circular import precautions, and how to add new languages.
+
+## 🔌 MCP Integration (Model Context Protocol)
+
+GitPR can run as an **MCP server**, exposing its AI-powered capabilities as tools that your editor's AI assistant can invoke directly — no terminal needed. This enables a fully integrated workflow where you can generate commit messages, review code, run linters, trace code origins, and create issues without leaving your IDE.
+
+### Supported Editors
+
+| Editor | Config File |
+| ------ | ----------- |
+| **VS Code** | `.vscode/mcp.json` |
+| **Cursor** | `.cursor/mcp.json` |
+| **Claude Code** | `.mcp.json` |
+| **Claude Desktop** | `claude_desktop_config.json` |
+| **Zed** | `settings.json` |
+
+### Quick Setup
+
+Use the built-in installer to configure your editor automatically:
+
+```bash
+gitpr-mcp --install vscode    # Creates .vscode/mcp.json
+gitpr-mcp --install cursor      # Creates .cursor/mcp.json
+gitpr-mcp --install claude-code # Creates .mcp.json
+gitpr-mcp --install claude      # Updates Claude Desktop config
+gitpr-mcp --install zed         # Updates Zed settings
+gitpr-mcp --install auto      # Auto-detect and install for all found
+```
+
+The installer creates the config directory if needed, merges with any existing
+config (never overwrites other servers), and is safe to run multiple times.
+
+> Manual setup is also supported — see [docs/mcp-integration.md](https://github.com/natanfiuza/gitpr/blob/main/docs/mcp-integration.md)
+> for the JSON config format for each editor.
+
+Once configured, use natural language in your editor's AI chat:
+
+   * *"Review my current changes"* → calls `review_code`
+   * *"Generate a commit message"* → calls `generate_commit_message`
+   * *"Create a PR description"* → calls `generate_pr_description`
+   * *"Run the linter on my diff"* → calls `run_linter`
+
+### Available MCP Tools
+
+| Tool | Description |
+| ---- | ----------- |
+| `get_git_context` | Current branch, repository name, and remote URL |
+| `analyze_diff` | Git diff of uncommitted changes |
+| `get_full_diff` | Full diff against origin/main |
+| `generate_commit_message` | AI-generated Conventional Commits message |
+| `review_code` | AI code review of local changes |
+| `full_review` | AI code review of all changes since origin/main |
+| `generate_pr_description` | Complete PR description (title + body) |
+| `run_linter` | Static linter against `.gitpr.linter.yml` |
+| `analyze_blame` | Git blame + AI classification |
+| `generate_issue` | Structured issue from diff, history, or blame |
+
+📖 **Full documentation:** [docs/mcp-integration.md](https://github.com/natanfiuza/gitpr/blob/main/docs/mcp-integration.md) — available in 5 languages (EN, PT-BR, PT-PT, ES, FR).
 
 ## 📚 Technical Documentation and Advanced Guides
 
@@ -225,10 +301,12 @@ If you want to implement GitPR as an automated quality barrier in your team, che
 
 ### Configuration & Infrastructure
 
+* [**Install Wizard**](https://github.com/natanfiuza/gitpr/blob/main/docs/install-wizard.md) — Step-by-step guided setup for configuring GitPR in a new project.
 * [**AI Providers**](https://github.com/natanfiuza/gitpr/blob/main/docs/providers-ia.md) — Configuration and selection between Google Gemini, DeepSeek, and Ollama.
 * [**Auto-Updater**](https://github.com/natanfiuza/gitpr/blob/main/docs/auto-update.md) — How GitPR's automatic update (hot-swap) works.
 * [**GitHub Token (PAT) Integration and Security**](https://github.com/natanfiuza/gitpr/blob/main/docs/github-pat-integration.md) — Understand how GitPR creates issues directly in the repository with authentication.
 * [**Internationalization (i18n)**](https://github.com/natanfiuza/gitpr/blob/main/docs/i18n_explanation.md) — Architecture, usage patterns, and how to add new languages.
+* [**MCP Integration**](https://github.com/natanfiuza/gitpr/blob/main/docs/mcp-integration.md) — Connect GitPR to VS Code, Cursor, and Claude Desktop via Model Context Protocol.
 
 ## ⚡ Local Cache System (Quota Savings)