mcp-on-demand-tools 0.1.0__tar.gz

mcp_on_demand_tools-0.1.0/.github/workflows/publish-to-test-pypi.yml

@@ -0,0 +1,68 @@
+name: Publish Python 🐍 distribution 📦 to PyPI and TestPyPI
+
+
+on:
+  push: {}
+  workflow_dispatch: {}
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@v6
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+      - name: Build sdist and wheel
+        run: uv build
+      - name: Verify artifacts
+        run: 'test -n "$(ls -A dist)"'
+      - uses: actions/upload-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+  publish-testpypi:
+    name: Publish to TestPyPI on main pushes
+    if: github.ref == 'refs/heads/main' && github.event_name == 'push'
+    needs: [build]
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+      - uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+      - uses: astral-sh/setup-uv@v6
+      - name: Publish to TestPyPI (OIDC)
+        run: uv publish --publish-url https://test.pypi.org/legacy/ dist/*
+
+  publish-pypi:
+    name: Publish to PyPI on tags
+    if: startsWith(github.ref, 'refs/tags/')
+    needs: [build]
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+    environment:
+      name: pypi
+      url: https://pypi.org/p/mcp-on-demand-tools
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+      - uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+      - uses: astral-sh/setup-uv@v6
+      - name: Publish to PyPI (OIDC)
+        run: uv publish dist/*
+

mcp_on_demand_tools-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+# System files
+.DS_Store

mcp_on_demand_tools-0.1.0/.python-version

@@ -0,0 +1 @@
+3.12

mcp_on_demand_tools-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.

mcp_on_demand_tools-0.1.0/PKG-INFO

@@ -0,0 +1,303 @@
+Metadata-Version: 2.4
+Name: mcp-on-demand-tools
+Version: 0.1.0
+Summary: An MCP server for dynamic tool registration and AI-powered simulation via Goose recipes
+Author-email: Aaron Goldsmith <aargoldsmith@gmail.com>
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: mcp>=1.17.0
+Description-Content-Type: text/markdown
+
+# mcp-on-demand-tools
+
+A Model Context Protocol (MCP) server that enables dynamic tool registration and execution powered by AI agents. Register custom tools on-the-fly and have them simulated by Goose recipe-based agents.
+
+## Overview
+
+This MCP server allows you to dynamically register new tools at runtime without server restarts. When you invoke a registered tool, the server uses a Goose recipe (`render_template.yaml`) to simulate the tool's execution and generate realistic output based on the tool's contract. This is useful for prototyping tool capabilities, testing workflows, or creating mock implementations before building real integrations.
+
+## Components
+
+### Resources
+
+The server provides resources for monitoring registered tools:
+
+- **Tool definition resources** (`tool://internal/{tool-name}`)
+  - Returns the complete tool schema including name, description, parameters, expected output, and side effects
+  - Includes call count statistics for monitoring usage
+
+- **Stats resource** (`stats://internal/summary`)
+  - Shows aggregate statistics: total tools registered, total calls made
+  - Lists top 10 tools by call count
+
+### Prompts
+
+- **plan-with-tools**: A planning prompt that helps orchestrate tool usage
+  - Arguments: `goal` (required), `notes` (optional)
+  - Lists all currently registered tools and suggests registering new ones if needed
+
+### Tools
+
+#### Core Tool
+
+- **register-tool**: Dynamically register a new on-demand tool
+  - Required parameters:
+    - `name`: Tool identifier (string)
+    - `description`: What the tool does (string)
+    - `paramSchema`: JSON object defining tool parameters. Each parameter should have `description` and `type` properties. Can be provided as an object or JSON string.
+    - `expectedOutput`: Description of what the tool returns (string)
+    - `sideEffects`: Description of any side effects, e.g., "Makes API call to weather service" or "None - simulated data generation" (string)
+
+#### Dynamic Tools
+
+Once registered, tools become immediately available for invocation. Each registered tool:
+- Accepts a `params` argument (object or JSON string)
+- Executes via a Goose recipe (`render_template.yaml`) which uses an AI model to generate realistic output
+- Returns simulated output matching the expected output contract
+- The server automatically notifies connected MCP clients when new tools are registered or when tool usage statistics change
+
+## How It Works
+
+1. **Register a tool** using the `register-tool` MCP tool with your desired schema
+2. **Tool becomes available** immediately - the server sends notifications to connected clients
+3. **Invoke the tool** with specific parameter values
+4. **Goose recipe executes** to simulate the tool and generate realistic output based on the contract
+5. **View statistics** via resources to monitor tool usage and call history
+
+### Architecture
+
+```
+┌─────────────────┐
+│  MCP Client     │
+│  (Claude, etc)  │
+└────────┬────────┘
+         │
+         │ register-tool
+         ▼
+┌─────────────────────────┐
+│  MCP Server             │
+│  (mcp-on-demand-tools)  │
+│                         │
+│  • Stores tool metadata │
+│  • Tracks call history  │
+│  • Provides resources   │
+└────────┬────────────────┘
+         │
+         │ invoke: tool-name(params)
+         ▼
+┌─────────────────────────┐
+│  Goose Recipe Runner    │
+│  (render_template.yaml) │
+│                         │
+│  Simulates tool based   │
+│  on contract & params   │
+└─────────────────────────┘
+```
+
+### Example Workflow
+
+```json
+// Step 1: Register a weather forecast tool
+{
+  "name": "get-weather-forecast",
+  "description": "Fetches weather forecast for a given location",
+  "paramSchema": {
+    "location": {
+      "description": "City name or coordinates",
+      "type": "string"
+    },
+    "days": {
+      "description": "Number of days to forecast (1-7)",
+      "type": "integer"
+    }
+  },
+  "expectedOutput": "Weather forecast data including temperature, conditions, and precipitation",
+  "sideEffects": "None - simulated data generation"
+}
+
+// Step 2: Tool is now available in MCP
+// Step 3: Invoke it
+{
+  "params": {
+    "location": "San Francisco",
+    "days": 3
+  }
+}
+// Step 4: Goose generates realistic weather data matching the contract
+```
+
+## Installation
+
+### Prerequisites
+
+**Required:**
+- Python 3.12 or higher
+- **[Goose](https://github.com/block/goose)** - Must be installed and available in your PATH
+- `uv` package manager (recommended) or `pip`
+
+**Important**: This server requires Goose to function. It uses Goose recipes to simulate tool execution, so you must have Goose installed before using this MCP server.
+
+**Compatibility Note**: This server works best with MCP clients that support dynamic tool list updates (like Claude Desktop). Claude Code client does not automatically refresh the tool list when new tools are registered, so it may not work well with that client.
+
+### Installing for Claude Desktop
+
+Add the server configuration to your Claude Desktop config file:
+
+**MacOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`  
+**Windows**: `%APPDATA%/Claude/claude_desktop_config.json`
+
+#### Option 1: Use Published Package (Recommended)
+
+```json
+{
+  "mcpServers": {
+    "mcp-on-demand-tools": {
+      "command": "uvx",
+      "args": ["mcp-on-demand-tools"]
+    }
+  }
+}
+```
+
+#### Option 2: Development Setup
+
+Clone the repository and use local installation:
+
+```json
+{
+  "mcpServers": {
+    "mcp-on-demand-tools": {
+      "command": "uv",
+      "args": [
+        "--directory",
+        "/absolute/path/to/mcp-on-demand-tools",
+        "run",
+        "mcp-on-demand-tools"
+      ]
+    }
+  }
+}
+```
+
+### Installing for Other MCP Clients
+
+For other MCP-compatible clients, configure them to run:
+
+```bash
+uvx mcp-on-demand-tools
+```
+
+Or for development:
+
+```bash
+uv --directory /path/to/mcp-on-demand-tools run mcp-on-demand-tools
+```
+
+## Development
+
+### Setup
+
+1. Clone the repository:
+```bash
+git clone https://github.com/yourusername/mcp-on-demand-tools.git
+cd mcp-on-demand-tools
+```
+
+2. Install dependencies:
+```bash
+uv sync
+```
+
+3. Run locally:
+```bash
+uv run mcp-on-demand-tools
+```
+
+### Building and Publishing
+
+To prepare the package for distribution:
+
+1. Build package distributions:
+```bash
+uv build
+```
+
+This creates source and wheel distributions in the `dist/` directory.
+
+2. Publish to PyPI:
+```bash
+uv publish
+```
+
+**Note**: Publishing requires PyPI credentials via environment variables or command flags:
+- Token: `--token` or `UV_PUBLISH_TOKEN`
+- Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`
+
+### Automated Publishing
+
+The project includes a GitHub Actions workflow that automatically:
+- Builds the package on every push
+- Publishes to TestPyPI on pushes to `main` branch
+- Publishes to PyPI when you create a git tag (e.g., `v0.1.0`)
+
+To publish a new version:
+```bash
+git tag v0.1.1
+git push origin v0.1.1
+```
+
+### Debugging
+
+Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, use the [MCP Inspector](https://github.com/modelcontextprotocol/inspector):
+
+```bash
+npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-on-demand-tools run mcp-on-demand-tools
+```
+
+Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
+
+### Project Structure
+
+```
+mcp-on-demand-tools/
+├── src/
+│   └── mcp_on_demand_tools/
+│       ├── __init__.py           # Package entry point
+│       ├── server.py             # Main MCP server implementation
+│       └── recipes/
+│           └── render_template.yaml  # Goose recipe for tool simulation
+├── pyproject.toml                # Project metadata and dependencies
+├── uv.lock                       # Locked dependencies
+└── README.md                     # This file
+```
+
+## How Tool Execution Works
+
+When you invoke a registered tool:
+
+1. The MCP server receives the tool call with parameters
+2. It constructs a context string with:
+   - Tool name and description
+   - Expected output contract
+   - Side effects declaration
+   - Input parameters (as JSON)
+3. The server executes `goose run --recipe render_template.yaml` with these parameters
+4. Goose's AI agent reads the contract and generates realistic output that matches the expected format
+5. The output is extracted and returned to the MCP client
+
+## Use Cases
+
+This server is ideal for:
+- **Rapid prototyping**: Test tool concepts without implementing full functionality
+- **API design exploration**: Experiment with tool interfaces before committing to implementation
+- **Workflow testing**: Validate complex workflows with realistic mock data
+- **Demonstration and documentation**: Show how tools would work without building them
+- **Placeholder tools**: Create temporary tool implementations during development
+
+## License
+
+See [LICENSE](LICENSE) file for details.
+
+## Contributing
+
+Contributions are welcome! Please feel free to submit a Pull Request.