harborrag-mcp-server 2.0.0a1__tar.gz

harborrag_mcp_server-2.0.0a1/.gitignore

@@ -0,0 +1,252 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+harborrag_control.db
+harborrag_control.db-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# HarborRAG local runtime state and ingested object data
+/.harborrag/
+/.local/
+# ...and the same, wherever a package nests its own local runtime state.
+**/.local/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer,
+#   you could uncomment the following to ignore the entire vscode folder
+.vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+.claude/**
+.agents/
+
+examples/
+
+# OS / editor noise
+.DS_Store
+.~lock.*#
+
+# Generated API contract artifact (exported by make openapi)
+openapi.json
+clients/typescript/src/schema.d.ts
+clients/typescript/dist/
+clients/typescript/node_modules/
+
+# Internal architecture working notes (kept out of the repo per team decision)
+docs/developers/architecture/http_backend/
+
+# Docling image output (config/parsers.yaml pdf-docling.image_output_dir)
+/data/docling-images/
+
+# Local macOS-compatible copy of dev.sh (bash 3.2 / BSD sed tweaks)
+scripts/deployment/dev-mac.sh

harborrag_mcp_server-2.0.0a1/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.

harborrag_mcp_server-2.0.0a1/PKG-INFO

@@ -0,0 +1,180 @@
+Metadata-Version: 2.5
+Name: harborrag-mcp-server
+Version: 2.0.0a1
+Summary: MCP facade and audited tools for HarborRAG.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: harborrag-core==2.0.0a1
+Requires-Dist: harborrag-runtime==2.0.0a1
+Requires-Dist: jsonschema<5,>=4.26
+Requires-Dist: pydantic<3,>=2.12
+Requires-Dist: pyyaml<7,>=6.0.2
+Provides-Extra: mcp
+Requires-Dist: fastmcp<4,>=3.4; extra == 'mcp'
+Description-Content-Type: text/markdown
+
+# harborrag-mcp-server
+
+Owns the FastMCP transport, pre-execution policy, and durable audit boundary.
+
+## Folder ownership
+
+```text
+__main__.py                 stdio / HTTP launcher and flag parsing
+tools/base.py               McpToolSpec and the BaseMcpTool contract
+tools/retrieval_inputs.py   shared tenant and retrieval argument schemas
+tools/vector_search.py      vector_search
+tools/graph_search.py       graph_triplet_search, graph_path_search, graph_subgraph_search
+server/base.py              server protocol
+server/server.py            tool registry, policy enforcement, dispatch
+server/http.py              loopback Streamable HTTP transport and status UI
+server/http_auth.py         owner-only bearer and tenant authorization
+server/static/status.html   status page and Tool Playground
+configuration/              config/mcp.yaml loading, validation, env overrides
+policy.py                   compiled safety ceilings
+audit.py                    JSONL audit writer
+defaults/mcp.yaml           packaged fallback configuration
+```
+
+## Team deliverables
+
+- The shipped transport exposes four retrieval tools: `vector_search`,
+  `graph_triplet_search`, `graph_path_search`, and `graph_subgraph_search`.
+  Chat and agent are not MCP tools; they are served only through the HarborRAG
+  REST API's `/v1/chat/completions` and `/v1/agent/completions` endpoints.
+- Every attempt and outcome is durably audited with a principal identifier and
+  arguments digest; raw arguments and tokens are never recorded.
+- Declared input schemas plus argument, result-count, and serialized-output
+  budgets are enforced.
+- Ingestion-capability tools fail closed until explicitly enabled.
+- Transport creation fails closed without authentication unless the caller
+  explicitly selects local unauthenticated stdio.
+- Service-level tools must never expose raw database/provider access or place
+  retrieved document text in descriptions.
+
+Install dependencies before running the launcher. The stdio and HTTP transports
+both configure the durable conversation memory, which runs control-plane
+database migrations via Alembic/asyncpg on startup; the retrieval tools call
+embedding providers through LiteLLM, read/write documents through the S3/MinIO
+object store, and query the Qdrant and FalkorDB backends. The `mcp` extra
+alone is not enough:
+
+```bash
+uv sync --package harborrag-mcp-server --extra mcp \
+    --package harborrag-adapters --extra control-plane --extra postgres \
+    --extra llm --extra s3 --extra qdrant --extra falkordb
+```
+
+Run the standard stdio transport:
+
+```bash
+scripts/deployment/mcp.sh
+```
+
+Build the equivalent non-root container and verify its advertised registry:
+
+```bash
+docker build -f deploy/docker/Dockerfile.mcp -t harborrag-mcp .
+docker run --rm harborrag-mcp --check
+```
+
+For a real stdio MCP session, run the image with an attached stdin, the
+database/model environment files, and connectivity to the configured data
+services. The image entrypoint is `python -m harborrag_mcp_server`, so MCP
+arguments such as `--check` or `--transport http` are forwarded directly.
+
+The launcher loads the protected database, model, API, and MCP environment files,
+constructs the shared `HarborRAG` runtime, and communicates over stdin/stdout.
+It is a child process launched by an MCP client, not an interactive terminal or
+HTTP service. Run `scripts/deployment/mcp.sh --check` yourself to perform a real
+MCP handshake and print the four advertised tool names without connecting to
+providers.
+
+Run an authenticated local Streamable HTTP endpoint and status page:
+
+```bash
+scripts/deployment/dev.sh bootstrap
+scripts/deployment/mcp.sh --http
+```
+
+The browser status page is `http://127.0.0.1:8010/`, health is available at
+`http://127.0.0.1:8010/healthz`, and MCP clients connect to
+`http://127.0.0.1:8010/mcp` with the token in an `Authorization: Bearer`
+header. Override the loopback host, port, or path with `--host`, `--port`, and
+`--path`; this local static-token mode intentionally rejects non-loopback
+hosts. The bootstrap command generates the token in the Git-ignored
+`env/.env.mcp` file with mode `0600`; override that path with `MCP_ENV_FILE`.
+
+## Tool Playground
+
+Open the browser page, enter the bearer token, provide a tenant ID, and select
+**Load tools**. The page builds an argument form from the effective JSON schema
+and executes the selected tool with **Run tool**. Tenant-specific enablement,
+defaults and limits are applied before execution, and each attempt is audited.
+
+Chat and agent are not part of this catalog; use the HarborRAG REST API's
+`/v1/chat/completions` and `/v1/agent/completions` endpoints instead.
+
+The owner-only browser API is:
+
+- `GET /api/tools?tenant_id=<tenant>` for the effective catalog;
+- `POST /api/tools/call` with `{"name": "...", "arguments": {...}}` to run a tool.
+
+The API is a local administrative convenience, not a second unprotected tool
+transport. It requires the same owner bearer token as configuration editing.
+
+## Tool configuration
+
+The versioned configuration lives at `config/mcp.yaml` by default. Set
+`HARBORRAG_MCP_CONFIG_PATH` or pass `--config` after `--http` to select another
+file. The configuration controls:
+
+- global policy budgets;
+- globally enabled tools;
+- optional argument defaults and numeric upper limits;
+- per-tenant enabled state, defaults, and limits.
+
+Required fields and `tenant_id` can never receive defaults, unknown tools and
+fields are rejected, and configured limits cannot exceed each tool's compiled
+safety ceiling. Tenant IDs are canonicalized before policy lookup and execution,
+and configuration tenant keys may not contain surrounding whitespace. These environment variables override the file without being
+persisted back into it:
+
+- `HARBORRAG_MCP_MAX_RESULTS`
+- `HARBORRAG_MCP_MAX_ARGUMENT_BYTES`
+- `HARBORRAG_MCP_MAX_OUTPUT_BYTES`
+- `HARBORRAG_MCP_DISABLED_TOOLS` (comma-separated tool names)
+
+In HTTP mode, enter the bearer token in the status page and use **Load**,
+**Save**, or **Reload YAML**. The owner-only API is `GET/PUT /api/config` and
+`POST /api/config/reload`. Saves use revision checks and atomic replacement;
+audit records contain only revision hashes, never configuration values.
+
+Defaults, limits, budgets, and tenant overrides are enforced immediately.
+Changes to global advertised tool schemas or enabled tools set
+`restart_required=true`; restart the MCP process so connected clients receive
+the new advertised catalog.
+
+Network transports must be constructed with a FastMCP authentication provider.
+MCP tool calls require an authenticated token carrying `role=owner` and an
+explicit `tenants` claim containing the requested tenant. Global owners must
+carry the deliberate wildcard claim `tenants=["*"]`.
+The explicit local override is for stdio only and opens no listener.
+
+
+## Package tests
+
+Tests for this package live in:
+
+```text
+packages/harborrag-mcp-server/tests/
+```
+
+Run from the repository root:
+
+```bash
+pytest packages/harborrag-mcp-server/tests
+```
+
+Keep new tests in this folder when adding or changing behavior owned by this package.