myopic 0.0.1__tar.gz

myopic-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,29 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+
+jobs:
+  test:
+    name: Python ${{ matrix.python-version }}
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: pip install -e .[dev]
+
+      - name: Run tests
+        run: pytest tests/ -v

myopic-0.0.1/.github/workflows/publish.yml

@@ -0,0 +1,105 @@
+name: Release (PyPI + GitHub Release + MCP Registry)
+
+# One tag push publishes everywhere, in the correct order:
+#   1. Guard — every version source must match the tag, or the release fails loudly.
+#   2. PyPI    — build + publish (OIDC Trusted Publishing, no token).
+#   3. GitHub  — create the Release with auto-generated notes.
+#   4. Wait    — until the new version is live on PyPI (the registry verifies
+#                ownership by reading the package's PyPI description).
+#   5. Registry — publish server.json via GitHub OIDC (no token).
+#
+# To cut a release: bump pyproject.toml, myopic/__init__.py, and BOTH version
+# fields in server.json to the same value, commit, then:
+#   git tag vX.Y.Z && git push origin vX.Y.Z
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  release:
+    name: Build and publish everywhere
+    runs-on: ubuntu-latest
+
+    permissions:
+      id-token: write   # OIDC — used by BOTH PyPI Trusted Publishing and the MCP Registry
+      contents: write   # required for `gh release create`
+
+    steps:
+      - uses: actions/checkout@v4
+
+      # 1. Guard: tag must equal every version source. Prevents the
+      #    "server.json left stale" desync from ever shipping silently.
+      - name: Verify version consistency
+        run: |
+          TAG="${GITHUB_REF#refs/tags/v}"
+          echo "Tag version: $TAG"
+
+          PYPROJECT=$(grep -m1 '^version' pyproject.toml | sed -E 's/.*"([^"]+)".*/\1/')
+          INIT=$(grep '__version__' myopic/__init__.py | sed -E 's/.*"([^"]+)".*/\1/')
+          SJ_TOP=$(python -c "import json;print(json.load(open('server.json'))['version'])")
+          SJ_PKG=$(python -c "import json;print(json.load(open('server.json'))['packages'][0]['version'])")
+
+          echo "pyproject.toml:      $PYPROJECT"
+          echo "__init__.py:         $INIT"
+          echo "server.json (top):   $SJ_TOP"
+          echo "server.json (pkg):   $SJ_PKG"
+
+          fail=0
+          for v in "$PYPROJECT" "$INIT" "$SJ_TOP" "$SJ_PKG"; do
+            if [ "$v" != "$TAG" ]; then fail=1; fi
+          done
+          if [ "$fail" -eq 1 ]; then
+            echo "::error::Version mismatch — every source must equal the tag ($TAG). Bump them and re-tag."
+            exit 1
+          fi
+          echo "All version sources match $TAG."
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Build distribution
+        run: pip install build && python -m build
+
+      # 2. PyPI — OIDC Trusted Publishing (configured once at
+      #    https://pypi.org/manage/account/publishing/). No token.
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+      # 3. GitHub Release with auto-generated notes from the commits.
+      - name: Create GitHub Release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: gh release create "${GITHUB_REF#refs/tags/}" --generate-notes --title "${GITHUB_REF#refs/tags/}"
+
+      # 4. Wait until the version is queryable on PyPI — the registry fetches the
+      #    package's PyPI description to verify the mcp-name ownership marker.
+      - name: Wait for PyPI to serve the new version
+        run: |
+          TAG="${GITHUB_REF#refs/tags/v}"
+          for i in $(seq 1 30); do
+            if curl -fsSL "https://pypi.org/pypi/myopic/$TAG/json" >/dev/null 2>&1; then
+              echo "myopic $TAG is live on PyPI."
+              exit 0
+            fi
+            echo "Attempt $i: not live yet, waiting 10s..."
+            sleep 10
+          done
+          echo "::error::myopic $TAG did not appear on PyPI within 5 minutes."
+          exit 1
+
+      # 5. Install the registry CLI and publish via GitHub OIDC.
+      #    The io.github.SurajKGoyal/* namespace is auto-authorized for OIDC
+      #    tokens from this repo — no allowlist step needed.
+      - name: Install mcp-publisher
+        run: |
+          curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
+
+      - name: Authenticate to MCP Registry (GitHub OIDC)
+        run: ./mcp-publisher login github-oidc
+
+      - name: Publish to MCP Registry
+        run: ./mcp-publisher publish

myopic-0.0.1/.gitignore

@@ -0,0 +1,24 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/
+
+# Virtual envs
+.venv/
+venv/
+env/
+
+# Secrets / local config
+.env
+*.env
+config.toml
+
+# Editors / OS
+.vscode/
+.idea/
+.DS_Store

myopic-0.0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Suraj Goyal
+
+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.

myopic-0.0.1/PKG-INFO

@@ -0,0 +1,182 @@
+Metadata-Version: 2.4
+Name: myopic
+Version: 0.0.1
+Summary: The code-review MCP that reviews your merge request against the whole codebase, not just the diff
+Project-URL: Homepage, https://github.com/SurajKGoyal/myopic
+Project-URL: Repository, https://github.com/SurajKGoyal/myopic
+Project-URL: Issues, https://github.com/SurajKGoyal/myopic/issues
+Author-email: Suraj Goyal <sgoyal275@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: ai-tools,claude,code-review,gitlab,llm,mcp,merge-request
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Requires-Dist: click>=8.0
+Requires-Dist: mcp[cli]>=1.0.0
+Requires-Dist: python-gitlab>=4.0
+Requires-Dist: rich>=13.0
+Requires-Dist: tree-sitter-go>=0.23.0
+Requires-Dist: tree-sitter-java>=0.23.0
+Requires-Dist: tree-sitter-javascript>=0.23.0
+Requires-Dist: tree-sitter-python>=0.23.0
+Requires-Dist: tree-sitter-rust>=0.23.0
+Requires-Dist: tree-sitter-typescript>=0.23.0
+Requires-Dist: tree-sitter>=0.24.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Provides-Extra: semantic
+Requires-Dist: httpx>=0.27; extra == 'semantic'
+Requires-Dist: lancedb>=0.15; extra == 'semantic'
+Description-Content-Type: text/markdown
+
+# myopic
+
+**The code-review MCP with the most ironic name in the registry.** It's anything
+but nearsighted — the goal is to review your merge request against the *whole*
+codebase, not just the diff in front of it.
+
+> ⚠️ **Alpha / building in public.** myopic is under active development and
+> currently supports **GitLab merge requests only** — GitHub pull requests are
+> on the roadmap (the platform layer is already abstracted for them). The
+> roadmap below is public on purpose: follow along, open issues, and pitch in.
+> What's checked off works today; the rest is coming. Don't depend on it in a
+> critical workflow yet.
+
+---
+
+## Why
+
+Most AI code review looks at the diff in isolation. But the bugs that matter
+live in what the diff *doesn't* show: the caller three files away that now
+breaks, the convention every sibling file follows that this one quietly drops,
+the helper that already exists so this new one is a duplicate, the file nobody
+imports. A reviewer that only reads the patch is **myopic**.
+
+myopic is an [MCP](https://modelcontextprotocol.io) server that feeds your AI
+client (Claude, Cursor, etc.) the structured context to review like someone who
+actually knows the codebase — starting with precise, line-numbered access to the
+merge request itself, and growing toward full codebase-aware review (see the
+roadmap).
+
+It pairs with [amnesic](https://github.com/SurajKGoyal/amnesic), my MCP server
+that gives AI persistent memory of SQL databases.
+
+---
+
+## Status & roadmap
+
+| Tool | What it does | Status |
+|------|--------------|--------|
+| `mr_review_status` | MR metadata + every discussion thread + resolved/unresolved state, in one call | ✅ alpha |
+| `mr_diff_lines` | MR diff as structured, line-numbered hunks — exact positions for inline comments | ✅ alpha |
+| `mr_diff_sections` | AST-grouped diff (by function/class) so large MRs don't blow the token budget | 🔜 planned |
+| `review_with_context` | RAG-augmented review: callers of changed symbols + conventions sibling files follow + duplication + unwired-file detection | 🔜 planned |
+| `mr_post_comments` | bulk-post inline review comments at exact diff positions | 🔜 planned |
+| GitHub pull requests | same tools, GitHub PRs (the platform layer is already abstracted for this) | 🔜 planned |
+
+Full details and design notes: [ROADMAP.md](./ROADMAP.md). Ideas and issues
+welcome — that's the point of building this in the open.
+
+---
+
+## Install
+
+```bash
+uvx myopic            # run directly (recommended)
+# or
+pip install myopic
+```
+
+## Setup
+
+myopic needs a GitLab URL and a personal access token with `api` (or `read_api`)
+scope.
+
+```bash
+myopic init           # writes a config template + prints next steps
+```
+
+Then put your token in `~/.config/myopic/.env`:
+
+```
+GITLAB_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx
+```
+
+Edit `~/.config/myopic/config.toml` if your GitLab is self-hosted (defaults to
+`https://gitlab.com`). Verify it:
+
+```bash
+myopic test           # ✓ Authenticated to https://gitlab.com as <you>
+```
+
+The token never lives in the TOML — it's referenced as `${GITLAB_TOKEN}` and
+read from the `.env` file (or your environment).
+
+## Add to your AI client
+
+**Claude Code** (`~/.claude/mcp.json` or project `.mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "myopic": {
+      "command": "uvx",
+      "args": ["myopic"]
+    }
+  }
+}
+```
+
+The same `command`/`args` work for Claude Desktop, Cursor, and other
+MCP-compatible clients — consult your client's MCP config docs for where the
+file lives.
+
+## Use
+
+Point your AI at a merge request:
+
+> "Review this MR: https://gitlab.com/group/project/-/merge_requests/42"
+
+Your client will call `mr_review_status` to orient, then `mr_diff_lines` to read
+exactly what changed with precise line numbers — and review from there.
+
+---
+
+## Configuration reference
+
+| Source | Key | Notes |
+|--------|-----|-------|
+| `config.toml` | `[gitlab].url` | GitLab base URL (default `https://gitlab.com`) |
+| `config.toml` | `[gitlab].token` | use `${GITLAB_TOKEN}` — don't hardcode |
+| `.env` (next to config) | `GITLAB_TOKEN` | the actual token value |
+| env var | `MYOPIC_GITLAB_URL` / `GITLAB_URL` | fallback if no TOML |
+| env var | `MYOPIC_GITLAB_TOKEN` / `GITLAB_TOKEN` | fallback if no TOML |
+| env var | `MYOPIC_CONFIG` | override the config file path |
+| env var | `MYOPIC_HOME` | override the config directory |
+
+## Security
+
+- **Read-oriented today.** The shipped tools only *read* MR data; nothing posts
+  or mutates. (Comment-posting on the roadmap will be explicit and opt-in.)
+- **Your token stays local.** It lives in your `.env` / environment and is sent
+  only to your configured GitLab instance — never to any third party.
+- Auth errors are scrubbed so your token never leaks into error messages.
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest                 # diff-parser unit tests, no network needed
+```
+
+## License
+
+MIT © Suraj Goyal
+
+<!-- MCP Registry ownership marker — do not remove. -->
+mcp-name: io.github.SurajKGoyal/myopic

myopic-0.0.1/README.md

@@ -0,0 +1,146 @@
+# myopic
+
+**The code-review MCP with the most ironic name in the registry.** It's anything
+but nearsighted — the goal is to review your merge request against the *whole*
+codebase, not just the diff in front of it.
+
+> ⚠️ **Alpha / building in public.** myopic is under active development and
+> currently supports **GitLab merge requests only** — GitHub pull requests are
+> on the roadmap (the platform layer is already abstracted for them). The
+> roadmap below is public on purpose: follow along, open issues, and pitch in.
+> What's checked off works today; the rest is coming. Don't depend on it in a
+> critical workflow yet.
+
+---
+
+## Why
+
+Most AI code review looks at the diff in isolation. But the bugs that matter
+live in what the diff *doesn't* show: the caller three files away that now
+breaks, the convention every sibling file follows that this one quietly drops,
+the helper that already exists so this new one is a duplicate, the file nobody
+imports. A reviewer that only reads the patch is **myopic**.
+
+myopic is an [MCP](https://modelcontextprotocol.io) server that feeds your AI
+client (Claude, Cursor, etc.) the structured context to review like someone who
+actually knows the codebase — starting with precise, line-numbered access to the
+merge request itself, and growing toward full codebase-aware review (see the
+roadmap).
+
+It pairs with [amnesic](https://github.com/SurajKGoyal/amnesic), my MCP server
+that gives AI persistent memory of SQL databases.
+
+---
+
+## Status & roadmap
+
+| Tool | What it does | Status |
+|------|--------------|--------|
+| `mr_review_status` | MR metadata + every discussion thread + resolved/unresolved state, in one call | ✅ alpha |
+| `mr_diff_lines` | MR diff as structured, line-numbered hunks — exact positions for inline comments | ✅ alpha |
+| `mr_diff_sections` | AST-grouped diff (by function/class) so large MRs don't blow the token budget | 🔜 planned |
+| `review_with_context` | RAG-augmented review: callers of changed symbols + conventions sibling files follow + duplication + unwired-file detection | 🔜 planned |
+| `mr_post_comments` | bulk-post inline review comments at exact diff positions | 🔜 planned |
+| GitHub pull requests | same tools, GitHub PRs (the platform layer is already abstracted for this) | 🔜 planned |
+
+Full details and design notes: [ROADMAP.md](./ROADMAP.md). Ideas and issues
+welcome — that's the point of building this in the open.
+
+---
+
+## Install
+
+```bash
+uvx myopic            # run directly (recommended)
+# or
+pip install myopic
+```
+
+## Setup
+
+myopic needs a GitLab URL and a personal access token with `api` (or `read_api`)
+scope.
+
+```bash
+myopic init           # writes a config template + prints next steps
+```
+
+Then put your token in `~/.config/myopic/.env`:
+
+```
+GITLAB_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx
+```
+
+Edit `~/.config/myopic/config.toml` if your GitLab is self-hosted (defaults to
+`https://gitlab.com`). Verify it:
+
+```bash
+myopic test           # ✓ Authenticated to https://gitlab.com as <you>
+```
+
+The token never lives in the TOML — it's referenced as `${GITLAB_TOKEN}` and
+read from the `.env` file (or your environment).
+
+## Add to your AI client
+
+**Claude Code** (`~/.claude/mcp.json` or project `.mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "myopic": {
+      "command": "uvx",
+      "args": ["myopic"]
+    }
+  }
+}
+```
+
+The same `command`/`args` work for Claude Desktop, Cursor, and other
+MCP-compatible clients — consult your client's MCP config docs for where the
+file lives.
+
+## Use
+
+Point your AI at a merge request:
+
+> "Review this MR: https://gitlab.com/group/project/-/merge_requests/42"
+
+Your client will call `mr_review_status` to orient, then `mr_diff_lines` to read
+exactly what changed with precise line numbers — and review from there.
+
+---
+
+## Configuration reference
+
+| Source | Key | Notes |
+|--------|-----|-------|
+| `config.toml` | `[gitlab].url` | GitLab base URL (default `https://gitlab.com`) |
+| `config.toml` | `[gitlab].token` | use `${GITLAB_TOKEN}` — don't hardcode |
+| `.env` (next to config) | `GITLAB_TOKEN` | the actual token value |
+| env var | `MYOPIC_GITLAB_URL` / `GITLAB_URL` | fallback if no TOML |
+| env var | `MYOPIC_GITLAB_TOKEN` / `GITLAB_TOKEN` | fallback if no TOML |
+| env var | `MYOPIC_CONFIG` | override the config file path |
+| env var | `MYOPIC_HOME` | override the config directory |
+
+## Security
+
+- **Read-oriented today.** The shipped tools only *read* MR data; nothing posts
+  or mutates. (Comment-posting on the roadmap will be explicit and opt-in.)
+- **Your token stays local.** It lives in your `.env` / environment and is sent
+  only to your configured GitLab instance — never to any third party.
+- Auth errors are scrubbed so your token never leaks into error messages.
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest                 # diff-parser unit tests, no network needed
+```
+
+## License
+
+MIT © Suraj Goyal
+
+<!-- MCP Registry ownership marker — do not remove. -->
+mcp-name: io.github.SurajKGoyal/myopic

myopic-0.0.1/ROADMAP.md

@@ -0,0 +1,83 @@
+# myopic roadmap
+
+myopic is built in the open and shipped in small increments. This file is the
+honest source of truth for what works, what's next, and why. If something here
+interests you, open an issue or a PR — design discussion is welcome.
+
+The north star: **review a change against the whole codebase, not just the
+diff.** Everything below ladders up to that.
+
+---
+
+## ✅ Shipped (alpha)
+
+### `mr_review_status(url)`
+One snapshot of where a review stands: MR metadata, every discussion thread,
+which are resolved vs open, general comments, and a lightweight file-change
+summary. Replaces 5-6 separate GitLab API calls.
+
+### `mr_diff_lines(url, files_filter?, lines_filter?)`
+The merge request diff as structured, line-numbered hunks — every line tagged
+add/del/context with exact old and new line numbers. This is the foundation for
+precise inline comments: `lines_filter` translates "comment on source line N"
+into the exact diff position the API needs. `files_filter` keeps large reviews
+under token limits.
+
+### Platform-abstraction seam
+All tools talk to a normalized `Review` interface, never to a platform SDK
+directly. GitLab is the first implementation; GitHub is a new implementation,
+not a rewrite (see below).
+
+---
+
+## 🔜 Next
+
+### `mr_diff_sections(url)` — AST-grouped diffs
+Group changed lines by the function/class they belong to (via tree-sitter) so a
+1,000-line MR can be reviewed structurally instead of overflowing the context
+window. All changed lines preserved; context optional.
+
+### `review_with_context(url, repo_path)` — the actual point
+This is myopic's reason to exist. For each changed symbol, surface:
+- **Callers** of modified public symbols (what might break).
+- **Conventions** sibling/similar files follow that this change drops
+  (missing imports, hooks, error handling).
+- **Intra-MR duplication** — near-identical new files copy-pasted within the MR.
+- **Unwired files** — new files nothing imports or references (dead on arrival).
+
+Pure structured context, no LLM judgment — the calling agent reviews; myopic
+makes sure it isn't reviewing blind. This depends on a codebase index; the
+indexing approach (and how to keep setup friction near zero) is the main open
+design question. **Ideas welcome.**
+
+### `mr_post_comments(url, comments[])` — explicit, opt-in writes
+Bulk-post inline review comments at exact diff positions (resolved via
+`mr_diff_lines`), rate-limited for self-hosted GitLab. Writes will always be
+explicit and clearly separated from the read-only tools.
+
+---
+
+## 🔭 Later
+
+### GitHub pull requests
+The platform layer is already abstracted (`myopic/platforms/base.py`). GitHub
+support is a `GitHubPlatform` + `GitHubReview` implementing the same interface —
+the tools don't change. This is why the project isn't named `gitlab-*`.
+
+### Other ideas on the table
+- CI/pipeline status + failed-job logs alongside the review.
+- Review-thread verification: did a later commit actually address each comment?
+- Configurable review "lenses" (security-only, performance-only, conventions-only).
+
+---
+
+## Design principles
+
+1. **Tools return data, not opinions.** myopic gathers context; the agent reviews.
+2. **Read and write are separate and obvious.** No tool silently mutates.
+3. **Setup friction approaches zero.** If a feature needs heavy local infra, that
+   friction is itself a design problem to solve, not a given.
+4. **Platform-neutral core.** Diffs and reviews are abstracted; GitLab is just the
+   first backend.
+
+Have a better idea for any of these? Open an issue.

myopic-0.0.1/myopic/__init__.py

@@ -0,0 +1,9 @@
+"""
+myopic — the code-review MCP server with the most ironic name in the registry.
+
+It's anything but nearsighted. It reviews your merge request against the *whole*
+codebase — callers, conventions, duplication, dead code — not just the diff in
+front of it.
+"""
+
+__version__ = "0.0.1"