mcp-toolsets-runtime 0.1.3__tar.gz

mcp_toolsets_runtime-0.1.3/.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Default owners for everything in the repo.
+* @ciaransweet

mcp_toolsets_runtime-0.1.3/.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+  - package-ecosystem: "uv"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "npm"
+    directory: "/js/mcp-view"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

mcp_toolsets_runtime-0.1.3/.github/workflows/ci.yml

@@ -0,0 +1,54 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  python:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+      - uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        with:
+          python-version: ${{ matrix.python-version }}
+      # Include [agent] so mcp_agent is imported/typechecked/tested too.
+      - run: uv sync --frozen --all-extras
+      - run: ./scripts/lint
+      - run: ./scripts/test
+
+  js:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
+        with:
+          node-version: "22"
+      - run: ./scripts/build-js
+
+  pr-title:
+    # The "changelog entry or fail" gate: the PR title must be a valid
+    # conventional commit, which (via squash-by-title) becomes the commit
+    # release-please turns into a CHANGELOG line.
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/action-semantic-pull-request@48f256284bd46cdaab1048c3721360e808335d50 # v6.1.1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          types: |
+            feat
+            fix
+            perf
+            refactor
+            docs
+            test
+            build
+            ci
+            chore

mcp_toolsets_runtime-0.1.3/.github/workflows/publish.yaml

@@ -0,0 +1,55 @@
+name: publish
+
+# Fires on the release release-please cuts (it uses an App token, so the event
+# is not suppressed — see release-please.yml).
+#
+# Both registries' trusted publishers are registered against this workflow's
+# *filename* and environment: `publish.yaml` / `release`. Renaming either breaks
+# publishing with an OIDC claim mismatch; change it on PyPI and npm first.
+#
+# `release` restricts deployments by ref. This workflow is triggered by a
+# release, so the ref is a *tag* — the environment needs a matching tag policy
+# (`mcp-toolsets-runtime-v*`), not just a branch one, or both jobs are blocked
+# before they start.
+on:
+  release:
+    types: [published]
+
+jobs:
+  pypi:
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      id-token: write # OIDC trusted publishing — no long-lived token
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          ref: ${{ github.event.release.tag_name }}
+      - uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+      - run: uv build
+      - uses: pypa/gh-action-pypi-publish@ba38be9e461d3875417946c167d0b5f3d385a247 # v1.14.1
+
+  npm:
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      contents: read
+      id-token: write # OIDC trusted publishing — no long-lived token
+    defaults:
+      run:
+        working-directory: js/mcp-view
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          ref: ${{ github.event.release.tag_name }}
+      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
+        with:
+          node-version: "22"
+          registry-url: "https://registry.npmjs.org"
+          scope: "@developmentseed"
+      # Node 22 ships npm 10; trusted publishing needs >= 11.5.1.
+      - run: npm install -g npm@latest
+        working-directory: .
+      - run: npm ci
+      - run: npm run build
+      - run: npm publish

mcp_toolsets_runtime-0.1.3/.github/workflows/release-please.yml

@@ -0,0 +1,29 @@
+name: release-please
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      # Runs as a GitHub App rather than GITHUB_TOKEN so the release it creates
+      # can trigger `publish.yaml` — GitHub suppresses workflow events for
+      # anything GITHUB_TOKEN does, to stop CI recursing.
+      - uses: actions/create-github-app-token@1b10c78c7865c340bc4f6099eb2f838309f1e8c3 # v3.1.1
+        id: app-token
+        with:
+          app-id: ${{ vars.DS_RELEASE_BOT_CLIENT_ID }}
+          private-key: ${{ secrets.DS_RELEASE_BOT_PRIVATE_KEY }}
+
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+      - uses: googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7 # v5.0.0
+        id: release
+        with:
+          token: ${{ steps.app-token.outputs.token }}
+          # config + manifest are read from the repo root

mcp_toolsets_runtime-0.1.3/.gitignore

@@ -0,0 +1,225 @@
+# 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
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-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
+
+# 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/
+
+# 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
+
+# Node / JS bridge
+node_modules/
+js/**/dist/
+
+# Chainlit runtime scaffolding
+.chainlit/

mcp_toolsets_runtime-0.1.3/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.1.3"
+}

mcp_toolsets_runtime-0.1.3/CHANGELOG.md

@@ -0,0 +1,24 @@
+# Changelog
+
+## [0.1.3](https://github.com/developmentseed/mcp-toolsets-runtime/compare/mcp-toolsets-runtime-v0.1.2...mcp-toolsets-runtime-v0.1.3) (2026-07-30)
+
+
+### Features
+
+* **publish:** release via App token, publish to PyPI and public npm ([#14](https://github.com/developmentseed/mcp-toolsets-runtime/issues/14)) ([b1da2e0](https://github.com/developmentseed/mcp-toolsets-runtime/commit/b1da2e0439d4525274b7d83a379e74a4078198d8))
+
+## [0.1.2](https://github.com/developmentseed/mcp-toolsets-runtime/compare/mcp-toolsets-runtime-v0.1.1...mcp-toolsets-runtime-v0.1.2) (2026-07-28)
+
+
+### Bug Fixes
+
+* **release:** publish the npm bridge inline and lock versions in step ([#12](https://github.com/developmentseed/mcp-toolsets-runtime/issues/12)) ([ee28bc2](https://github.com/developmentseed/mcp-toolsets-runtime/commit/ee28bc208b4f8af0022a4796dad08d7da54570bb))
+
+## [0.1.1](https://github.com/developmentseed/mcp-toolsets-runtime/compare/mcp-toolsets-runtime-v0.1.0...mcp-toolsets-runtime-v0.1.1) (2026-07-28)
+
+
+### Features
+
+* extract shared runtime into an installable package ([#1](https://github.com/developmentseed/mcp-toolsets-runtime/issues/1)) ([ca9ec3d](https://github.com/developmentseed/mcp-toolsets-runtime/commit/ca9ec3d37893b54dfd53409d4e4c13c7fef1b762))
+
+## Changelog

mcp_toolsets_runtime-0.1.3/CONTRIBUTING.md

@@ -0,0 +1,66 @@
+# Contributing
+
+## Your PR title is the changelog
+
+This repo releases with [release-please](https://github.com/googleapis/release-please):
+it reads the commits on `main`, groups them into `CHANGELOG.md`, and bumps the
+version. Because `main` uses **squash-merge with the PR title as the commit
+subject**, your **PR title** is the line that lands in the changelog.
+
+So every PR title must be a valid [Conventional Commit](https://www.conventionalcommits.org/):
+
+```
+<type>(<optional scope>): <description>
+```
+
+CI (`pr-title`) fails the PR if the title isn't one of these types:
+
+| Type | Use for | Version effect (pre-1.0) |
+| --- | --- | --- |
+| `feat` | a new capability | minor |
+| `fix` | a bug fix | patch |
+| `perf` | a performance improvement | patch |
+| `refactor` | internal change, no behaviour change | patch |
+| `docs` | docs only | none |
+| `test` | tests only | none |
+| `build` | build system / deps | none |
+| `ci` | CI config | none |
+| `chore` | anything else | none |
+
+A **breaking change** — an incompatible change to the plugin contract
+(`TOOLS` / `VIEWS` / `CREDENTIAL_HEADERS`), `ToolResult`, the `ui/*` wire
+protocol, or a public signature — gets a `!`:
+
+```
+feat!: require ToolResult from every tool
+```
+
+Examples:
+
+```
+feat(runtime): stamp view _meta on tools that declare VIEWS
+fix(agent): only inject declared credential headers
+chore(deps): bump mcp to 1.29
+```
+
+## The release flow
+
+1. Merge PRs with conventional titles.
+2. release-please keeps a rolling **release PR** that bumps `pyproject.toml` and
+   `js/mcp-view/package.json` (kept equal by the linked-versions plugin) and
+   updates `CHANGELOG.md`. **This PR is editable** — curate the changelog prose
+   before merging if a release warrants it.
+3. Merging the release PR tags `vX.Y.Z`, cuts a GitHub Release, and publishes
+   the JS package.
+
+## Local checks
+
+```bash
+uv sync --all-extras
+./scripts/lint
+./scripts/test
+./scripts/build-js
+```
+
+Lint/type rules live entirely in `pyproject.toml` — the scripts pass no rule
+flags, so your editor, `./scripts/format`, and CI all agree.

mcp_toolsets_runtime-0.1.3/LICENSE

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

mcp_toolsets_runtime-0.1.3/PKG-INFO

@@ -0,0 +1,117 @@
+Metadata-Version: 2.4
+Name: mcp-toolsets-runtime
+Version: 0.1.3
+Summary: Shared runtime for MCP Toolsets: discover LangChain tools, serve them as MCP, plus a CLI and an example chat agent.
+License: MIT License
+        
+        Copyright (c) 2026 Development Seed
+        
+        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.
+License-File: LICENSE
+Requires-Python: <3.14,>=3.12
+Requires-Dist: fastapi<1.0.0,>=0.140.11
+Requires-Dist: langchain-core<2.0.0,>=1.4.6
+Requires-Dist: langchain-mcp-adapters<0.4.0,>=0.3.0
+Requires-Dist: mcp<2.0.0,>=1.27.2
+Requires-Dist: pydantic-settings<3.0.0,>=2.12.0
+Requires-Dist: rich<16.0.0,>=15.0.0
+Requires-Dist: typer<0.28.0,>=0.27.0
+Requires-Dist: typing-extensions>=4.10.0
+Provides-Extra: agent
+Requires-Dist: chainlit<3.0.0,>=2.11.1; extra == 'agent'
+Requires-Dist: httpx<1.0.0,>=0.28.1; extra == 'agent'
+Requires-Dist: langchain<2.0.0,>=1.3.7; extra == 'agent'
+Description-Content-Type: text/markdown
+
+# mcp-toolsets-runtime
+
+The shared runtime for [MCP Toolsets](https://github.com/developmentseed/mcp-toolsets).
+Both `developmentseed/mcp-toolsets` and downstream repos generated from it
+(e.g. `ecmwf/dss-agentic-ai-services`) install this package instead of each
+carrying their own copy of the runtime.
+
+## What's in here
+
+One Python distribution (`mcp-toolsets-runtime`) exposing three top-level
+modules, plus the view-side JS bridge:
+
+| Module | What it is |
+| --- | --- |
+| `mcp_runtime` | Discovers a toolset's LangChain tools (`TOOLS`) and serves them as an MCP server; serves UI views (`VIEWS`) as `ui://` resources; derives server `instructions` from `CREDENTIAL_HEADERS`. Entry points: `mcp-serve`, `mcp-index`. |
+| `mcp_cli` | Typer CLI to list and call tools on a running MCP service. Entry point: `mcp-cli`. |
+| `mcp_toolset` | Scaffolds a new toolset in a consumer repo (`mcp-toolset new [--with-ui] <name>`), wired to this package + the npm view bridge. |
+| `mcp_agent` | Example Chainlit chat agent that discovers MCP servers behind an index URL and drives their tools. Ships the Chainlit host element `elements/McpView.jsx`. Entry points: `mcp-agent`, `mcp-agent-web`. Requires the `[agent]` extra. |
+| `@developmentseed/mcp-view` (`js/mcp-view`) | The view-side `ui/*` postMessage bridge a toolset UI imports (`onData` / `sendMessage`). Published to npm separately. |
+
+### The toolset plugin contract
+
+`mcp_runtime` discovers a toolset purely by convention — a `<toolset>.tools`
+module exporting:
+
+- `TOOLS` — a non-empty list of LangChain tools that return a `ToolResult`.
+- `VIEWS` *(optional)* — `{tool_name: view_id}`, with a built bundle at
+  `<package>/views/<view_id>.html`.
+- `CREDENTIAL_HEADERS` *(optional)* — header names the tools read off the
+  transport; used to derive the model-facing auth hint.
+
+Treat these, `ToolResult`, and the `ui/*` wire protocol as **public API**.
+
+## Install
+
+```bash
+# base: runtime + cli (lean, for tool-serving images)
+pip install "mcp-toolsets-runtime @ git+https://github.com/developmentseed/mcp-toolsets-runtime.git@v0.1.0"
+
+# with the Chainlit web agent
+pip install "mcp-toolsets-runtime[agent] @ git+https://github.com/developmentseed/mcp-toolsets-runtime.git@v0.1.0"
+```
+
+With uv, as a consumer:
+
+```toml
+dependencies = ["mcp-toolsets-runtime[agent]"]
+
+[tool.uv.sources]
+mcp-toolsets-runtime = { git = "https://github.com/developmentseed/mcp-toolsets-runtime.git", tag = "v0.1.0" }
+```
+
+Imports are unchanged from the old workspace packages: `from mcp_runtime.server
+import build_server`, etc. Bump the runtime by changing the `tag` and running
+`uv lock`.
+
+**Consuming this package** — the plugin contract, serving toolsets, wiring up UI
+views (including `mcp-agent install-elements` and the npm bridge), and migrating
+off the in-repo workspace: see **[docs/CONSUMING.md](./docs/CONSUMING.md)**.
+
+## Develop
+
+```bash
+uv sync --all-extras   # install with [agent] + dev tools
+./scripts/lint         # ruff check + ruff format --check + mypy (config in pyproject)
+./scripts/test         # pytest
+./scripts/build-js     # typecheck + build + vitest for js/mcp-view (needs node)
+```
+
+## Releases
+
+Versioning and `CHANGELOG.md` are managed by
+[release-please](https://github.com/googleapis/release-please) from Conventional
+Commits. See [CONTRIBUTING.md](./CONTRIBUTING.md) — in short, **your PR title is
+the changelog entry**, and CI fails a PR whose title isn't a valid conventional
+commit. The Python package and the JS bridge share one version (linked).