benspdf-mcp 0.1.0__tar.gz

benspdf_mcp-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

benspdf_mcp-0.1.0/MANIFEST.in

@@ -0,0 +1,11 @@
+# setuptools already picks up tests/test_*.py by itself, but not conftest.py,
+# which every test needs: the autouse isolated_workspace fixture lives there and
+# points the artifact workspace at a temp directory. Without it the tests in the
+# sdist collect and then write to the real ~/.benstools/work. Graft the whole
+# directory so the sdist is either coherent or obviously not.
+graft tests
+
+# Build noise that has no business in a release artifact.
+global-exclude *.py[cod]
+global-exclude .DS_Store
+prune **/__pycache__

benspdf_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,201 @@
+Metadata-Version: 2.4
+Name: benspdf-mcp
+Version: 0.1.0
+Summary: Local PDF tools for AI agents, exposed over the Model Context Protocol
+Author-email: Benjamin Bergner <bergner.benjamin@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/benbergner/BensPDF
+Project-URL: Repository, https://github.com/benbergner/BensPDF
+Project-URL: Issues, https://github.com/benbergner/BensPDF/issues
+Keywords: mcp,pdf,llm,agents,model-context-protocol
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Text Processing
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pypdf>=4.0.0
+Requires-Dist: pypdfium2>=4.30.0
+Requires-Dist: Pillow>=10.0.0
+Requires-Dist: mcp>=2.0.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"
+Requires-Dist: black>=23.0.0; extra == "dev"
+Requires-Dist: mypy>=1.0.0; extra == "dev"
+Provides-Extra: ollama
+Requires-Dist: ollama>=0.1.0; extra == "ollama"
+Dynamic: license-file
+
+# BensPDF
+
+Ben's PDF tools for AI agents, exposed over the [Model Context Protocol](https://modelcontextprotocol.io) (MCP).
+
+Your PDFs are read on your own machine and never uploaded. Works with Claude
+Desktop, VS Code, Kiro, Cursor, the ChatGPT desktop app, and any other MCP
+client, or fully offline with a local Ollama model.
+
+## Tools
+
+| Tool | What it does |
+| --- | --- |
+| `pdf_page_count` | Counts the pages in a PDF |
+| `pdf_metadata` | Reads document properties: title, author, dates, producer |
+| `pdf_check_text` | Says whether a PDF is readable text or a scan that needs OCR |
+| `pdf_page_layout` | Page sizes, orientation, rotation and page boxes |
+| `pdf_check_access` | Encryption, and what the file permits: printing, copying, editing |
+| `pdf_render_pages` | Renders pages to images, so a page can be looked at |
+| `create_test_pdf_file` | Generates a throwaway PDF, handy for trying things out |
+| `export` | Saves results to a real location on disk |
+| `list_artifacts` | Lists recent temporary results |
+| `discard` | Deletes temporary results now |
+
+## Where results go
+
+When a tool makes a new PDF, it goes into a scratch folder instead of your own
+folders, and you get back a short id like `art_a1b2c3d4.pdf`. Tools accept those
+ids anywhere they accept a file path, so several steps can be chained together.
+
+Results carry the artifact's `path` as well as its id, so you can open a rendered
+page or an intermediate file straight away without exporting it first.
+
+`export` is the only tool that writes into your folders, so nothing shows up
+until you ask for it. Each time the server starts it clears out scratch files
+older than 7 days. Set `BENSTOOLS_WORKSPACE` to put the scratch folder somewhere
+other than `~/.benstools/work`.
+
+## Setup
+
+Install [uv](https://docs.astral.sh/uv/getting-started/installation/)
+once, then point your client at `uvx benspdf-mcp` and uv fetches the package,
+plus a suitable Python, on first run.
+
+```bash
+# macOS and Linux
+curl -LsSf https://astral.sh/uv/install.sh | sh
+
+# Windows
+powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
+```
+
+On macOS, `brew install uv` works too.
+
+Add the server to your client with one of the configs below, then restart the
+server from your client's UI. Once connected, just ask in plain language:
+
+> How many pages are in ~/Downloads/report.pdf?
+
+### Claude Desktop
+
+Edit `claude_desktop_config.json`, which lives at
+`~/Library/Application Support/Claude/` on macOS and `%APPDATA%\Claude\` on
+Windows. You can also open it from **Settings → Developer → Edit Config**.
+
+```json
+{
+  "mcpServers": {
+    "benspdf": {
+      "command": "uvx",
+      "args": ["benspdf-mcp"]
+    }
+  }
+}
+```
+
+### VS Code
+
+`.vscode/mcp.json` in your workspace, or the same file in your user profile.
+Note VS Code uses `servers` rather than `mcpServers`, and wants an explicit
+`type`.
+
+```json
+{
+  "servers": {
+    "benspdf": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["benspdf-mcp"]
+    }
+  }
+}
+```
+
+### Kiro
+
+`.kiro/settings/mcp.json` in your workspace, or `~/.kiro/settings/mcp.json` to
+enable it everywhere. `autoApprove` skips the confirmation prompt for tools you
+trust.
+
+```json
+{
+  "mcpServers": {
+    "benspdf": {
+      "command": "uvx",
+      "args": ["benspdf-mcp"],
+      "autoApprove": ["pdf_page_count"]
+    }
+  }
+}
+```
+
+### Cursor, Continue.dev, and most other clients
+
+Same shape as the Claude Desktop config above, in whatever file the client uses.
+
+### ChatGPT desktop app, Codex CLI, Codex IDE extension
+
+All three are Codex clients and share one config file, `~/.codex/config.toml`,
+so adding the server once covers all of them.
+
+```toml
+[mcp_servers.benspdf]
+command = "uvx"
+args = ["benspdf-mcp"]
+```
+
+## Fully offline with Ollama
+
+The clients above keep your PDFs local, but they answer using a hosted model.
+Pair the tools with a local model instead and nothing leaves your machine.
+
+You'll need [Ollama](https://ollama.com) with a model pulled, plus this package:
+
+```bash
+pip install benspdf-mcp ollama
+ollama pull llama3.1
+```
+
+Then run the bundled CLI:
+
+```bash
+benspdf-cli                        # uses the first model you have
+benspdf-cli --model llama3.1       # or pick one
+BENSPDF_MODEL=llama3.1 benspdf-cli # or set it once
+```
+
+`python -m benspdf.cli` does the same thing, handy from a source checkout.
+
+```
+You: how many pages in ~/Downloads/report.pdf?
+[Using tool: pdf_page_count]
+[Result: 12 pages in report.pdf]
+Assistant: The PDF has 12 pages.
+```
+
+## Reference
+
+Each tool's own description tells your client what it does and when to use it, so
+in normal use there is nothing to look up. If you want the detail — every field a
+tool returns, and the reasoning behind the answers it gives — see the
+[tool reference](https://github.com/benbergner/BensPDF/blob/main/docs/tools.md).
+
+To work on the code, see
+[CONTRIBUTING.md](https://github.com/benbergner/BensPDF/blob/main/CONTRIBUTING.md).
+
+## License
+
+Apache 2.0

benspdf_mcp-0.1.0/README.md

@@ -0,0 +1,168 @@
+# BensPDF
+
+Ben's PDF tools for AI agents, exposed over the [Model Context Protocol](https://modelcontextprotocol.io) (MCP).
+
+Your PDFs are read on your own machine and never uploaded. Works with Claude
+Desktop, VS Code, Kiro, Cursor, the ChatGPT desktop app, and any other MCP
+client, or fully offline with a local Ollama model.
+
+## Tools
+
+| Tool | What it does |
+| --- | --- |
+| `pdf_page_count` | Counts the pages in a PDF |
+| `pdf_metadata` | Reads document properties: title, author, dates, producer |
+| `pdf_check_text` | Says whether a PDF is readable text or a scan that needs OCR |
+| `pdf_page_layout` | Page sizes, orientation, rotation and page boxes |
+| `pdf_check_access` | Encryption, and what the file permits: printing, copying, editing |
+| `pdf_render_pages` | Renders pages to images, so a page can be looked at |
+| `create_test_pdf_file` | Generates a throwaway PDF, handy for trying things out |
+| `export` | Saves results to a real location on disk |
+| `list_artifacts` | Lists recent temporary results |
+| `discard` | Deletes temporary results now |
+
+## Where results go
+
+When a tool makes a new PDF, it goes into a scratch folder instead of your own
+folders, and you get back a short id like `art_a1b2c3d4.pdf`. Tools accept those
+ids anywhere they accept a file path, so several steps can be chained together.
+
+Results carry the artifact's `path` as well as its id, so you can open a rendered
+page or an intermediate file straight away without exporting it first.
+
+`export` is the only tool that writes into your folders, so nothing shows up
+until you ask for it. Each time the server starts it clears out scratch files
+older than 7 days. Set `BENSTOOLS_WORKSPACE` to put the scratch folder somewhere
+other than `~/.benstools/work`.
+
+## Setup
+
+Install [uv](https://docs.astral.sh/uv/getting-started/installation/)
+once, then point your client at `uvx benspdf-mcp` and uv fetches the package,
+plus a suitable Python, on first run.
+
+```bash
+# macOS and Linux
+curl -LsSf https://astral.sh/uv/install.sh | sh
+
+# Windows
+powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
+```
+
+On macOS, `brew install uv` works too.
+
+Add the server to your client with one of the configs below, then restart the
+server from your client's UI. Once connected, just ask in plain language:
+
+> How many pages are in ~/Downloads/report.pdf?
+
+### Claude Desktop
+
+Edit `claude_desktop_config.json`, which lives at
+`~/Library/Application Support/Claude/` on macOS and `%APPDATA%\Claude\` on
+Windows. You can also open it from **Settings → Developer → Edit Config**.
+
+```json
+{
+  "mcpServers": {
+    "benspdf": {
+      "command": "uvx",
+      "args": ["benspdf-mcp"]
+    }
+  }
+}
+```
+
+### VS Code
+
+`.vscode/mcp.json` in your workspace, or the same file in your user profile.
+Note VS Code uses `servers` rather than `mcpServers`, and wants an explicit
+`type`.
+
+```json
+{
+  "servers": {
+    "benspdf": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["benspdf-mcp"]
+    }
+  }
+}
+```
+
+### Kiro
+
+`.kiro/settings/mcp.json` in your workspace, or `~/.kiro/settings/mcp.json` to
+enable it everywhere. `autoApprove` skips the confirmation prompt for tools you
+trust.
+
+```json
+{
+  "mcpServers": {
+    "benspdf": {
+      "command": "uvx",
+      "args": ["benspdf-mcp"],
+      "autoApprove": ["pdf_page_count"]
+    }
+  }
+}
+```
+
+### Cursor, Continue.dev, and most other clients
+
+Same shape as the Claude Desktop config above, in whatever file the client uses.
+
+### ChatGPT desktop app, Codex CLI, Codex IDE extension
+
+All three are Codex clients and share one config file, `~/.codex/config.toml`,
+so adding the server once covers all of them.
+
+```toml
+[mcp_servers.benspdf]
+command = "uvx"
+args = ["benspdf-mcp"]
+```
+
+## Fully offline with Ollama
+
+The clients above keep your PDFs local, but they answer using a hosted model.
+Pair the tools with a local model instead and nothing leaves your machine.
+
+You'll need [Ollama](https://ollama.com) with a model pulled, plus this package:
+
+```bash
+pip install benspdf-mcp ollama
+ollama pull llama3.1
+```
+
+Then run the bundled CLI:
+
+```bash
+benspdf-cli                        # uses the first model you have
+benspdf-cli --model llama3.1       # or pick one
+BENSPDF_MODEL=llama3.1 benspdf-cli # or set it once
+```
+
+`python -m benspdf.cli` does the same thing, handy from a source checkout.
+
+```
+You: how many pages in ~/Downloads/report.pdf?
+[Using tool: pdf_page_count]
+[Result: 12 pages in report.pdf]
+Assistant: The PDF has 12 pages.
+```
+
+## Reference
+
+Each tool's own description tells your client what it does and when to use it, so
+in normal use there is nothing to look up. If you want the detail — every field a
+tool returns, and the reasoning behind the answers it gives — see the
+[tool reference](https://github.com/benbergner/BensPDF/blob/main/docs/tools.md).
+
+To work on the code, see
+[CONTRIBUTING.md](https://github.com/benbergner/BensPDF/blob/main/CONTRIBUTING.md).
+
+## License
+
+Apache 2.0

benspdf_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,75 @@
+[build-system]
+# 77 is the floor for PEP 639: `license` as an SPDX expression plus
+# `license-files`, which is what PyPI reads now.
+requires = ["setuptools>=77.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "benspdf-mcp"
+version = "0.1.0"
+description = "Local PDF tools for AI agents, exposed over the Model Context Protocol"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [
+    {name = "Benjamin Bergner", email = "bergner.benjamin@gmail.com"}
+]
+keywords = ["mcp", "pdf", "llm", "agents", "model-context-protocol"]
+# These become the sidebar links on the PyPI page, which is where someone who
+# found the package by search goes next.
+urls.Homepage = "https://github.com/benbergner/BensPDF"
+urls.Repository = "https://github.com/benbergner/BensPDF"
+urls.Issues = "https://github.com/benbergner/BensPDF/issues"
+# No license classifier: PEP 639 replaced it with the `license` field above, and
+# setuptools rejects declaring both.
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Text Processing",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+]
+dependencies = [
+    "pypdf>=4.0.0",
+    "pypdfium2>=4.30.0",
+    "Pillow>=10.0.0",
+    "mcp>=2.0.0",
+]
+
+[project.scripts]
+benspdf-mcp = "benspdf.mcp_server:main"
+benspdf-cli = "benspdf.cli:main"
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=7.0.0",
+    "pytest-asyncio>=0.21.0",
+    "black>=23.0.0",
+    "mypy>=1.0.0",
+]
+ollama = ["ollama>=0.1.0"]
+
+# Two top-level packages: benspdf (the PDF verbs) and benscore (the shared
+# artifact layer they sit on). benscore carries no domain in its name or its
+# config surface, so a future domain package can share one workspace with these
+# verbs, and so moving it into its own distribution later changes nothing for
+# anything that imports it.
+[tool.setuptools.packages.find]
+where = ["src"]
+
+# pypdfium2 is a ctypes binding and ships no py.typed marker, so mypy cannot see
+# into it. Nothing to fix on our side; the calls we make are covered by tests.
+[[tool.mypy.overrides]]
+module = ["pypdfium2.*", "pypdfium2"]
+ignore_missing_imports = true
+
+# ollama is an optional extra, so the common case is that it is not installed -
+# which is the case cli.py already handles, by guarding the import and telling
+# the user how to get it. Without this, type checking an install that does not
+# have the extra fails on an import that is meant to be absent.
+[[tool.mypy.overrides]]
+module = ["ollama.*", "ollama"]
+ignore_missing_imports = true

benspdf_mcp-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+