mcp-server-pixeltable-developer 0.2.1__tar.gz

mcp_server_pixeltable_developer-0.2.1/.gitignore

@@ -0,0 +1,92 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+*.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
+.hypothesis/
+.pytest_cache/
+
+# Virtual environments
+.env
+.venv
+.venv-*/
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# IDEs
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+
+# Pixeltable specific
+.pixeltable/
+
+# MCP server specific
+*.log
+
+# uv
+.python-version
+
+# Testing logs
+pixeltable_testing_logs/
+conformance-results/
+evals/results/*/sources/
+evals/results/*/*/workspace/
+evals/results/*/*/prompt.txt
+evals/results/*/*/transcript.jsonl
+evals/results/*/*/stderr.txt
+evals/results/*/*/final.txt
+evals/results/*/*/verifier.json
+
+# Sample data
+sample_data/

mcp_server_pixeltable_developer-0.2.1/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_server_pixeltable_developer-0.2.1/PKG-INFO

@@ -0,0 +1,303 @@
+Metadata-Version: 2.5
+Name: mcp-server-pixeltable-developer
+Version: 0.2.1
+Summary: A local developer MCP server for Pixeltable applications
+Project-URL: Homepage, https://github.com/pixeltable/mcp-server-pixeltable-developer
+Project-URL: Bug Tracker, https://github.com/pixeltable/mcp-server-pixeltable-developer/issues
+Author: Pixeltable
+License: Apache-2.0
+License-File: LICENSE
+Keywords: ai,data,machine-learning,mcp,multimodal,pixeltable
+Classifier: Development Status :: 4 - Beta
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Python: >=3.11
+Requires-Dist: mcp<3,>=2.2
+Requires-Dist: packaging>=24
+Requires-Dist: pixeltable[serve]<0.8,>=0.7.10
+Requires-Dist: pydantic<3,>=2.11
+Provides-Extra: canvas
+Requires-Dist: fastapi>=0.115.0; extra == 'canvas'
+Requires-Dist: uvicorn>=0.32.0; extra == 'canvas'
+Provides-Extra: test
+Requires-Dist: build>=1.2; extra == 'test'
+Requires-Dist: mcp[cli]<3,>=2.2; extra == 'test'
+Requires-Dist: pyright>=1.1.405; extra == 'test'
+Requires-Dist: pytest-asyncio>=0.24; extra == 'test'
+Requires-Dist: pytest>=8.0; extra == 'test'
+Requires-Dist: ruff>=0.12; extra == 'test'
+Description-Content-Type: text/markdown
+
+# Pixeltable Developer MCP Server
+
+<!-- mcp-name: io.github.pixeltable/mcp-server-pixeltable-developer -->
+
+A local Model Context Protocol server for building, inspecting, and operating
+[Pixeltable](https://pixeltable.com/) applications. Version 0.2 follows the
+application-first workflow in [pixeltable-skill 2.12.0](https://github.com/pixeltable/pixeltable-skill/blob/67f5a4222ce325420c461606c099e9ee0f9c9c02/skills/pixeltable-skill/SKILL.md): generate one `app.py`, apply its schema, and serve its routes with the `pxt` CLI.
+
+## Compatibility
+
+| Component | Supported line |
+|---|---|
+| Python | 3.11 or newer |
+| Pixeltable | `>=0.7.10,<0.8` with the `serve` extra |
+| MCP Python SDK | `>=2.2,<3` |
+| Pixeltable skill | 2.12.0 |
+| Production transport | local `stdio` |
+
+The server is a **beta developer tool**. It runs with the permissions of the
+process that launched it and can mutate the selected Pixeltable catalog. Point
+`PIXELTABLE_MCP_PROJECT_ROOT` at the application directory and `PIXELTABLE_HOME`
+at the intended catalog before startup. Both locations are fixed for the life of
+the process. Use a separate catalog for evaluation and automated tests.
+
+## Install and connect
+
+Install [`uv`](https://docs.astral.sh/uv/getting-started/installation/), then run the server from PyPI:
+
+```bash
+uvx mcp-server-pixeltable-developer --version
+```
+
+For reproducible development from a clone:
+
+```bash
+git clone https://github.com/pixeltable/mcp-server-pixeltable-developer.git
+cd mcp-server-pixeltable-developer
+uv sync --frozen --extra test
+```
+
+The repository also builds a container image that runs the same `stdio` server.
+Mount your application directory and point both variables at the mounts; the
+catalog is lost with the container unless you mount one too. On macOS, the host
+paths must be shared with your container engine, or the mount lands inside its VM:
+
+```bash
+docker build -t mcp-server-pixeltable-developer .
+docker run --rm -i \
+  -e PIXELTABLE_MCP_PROJECT_ROOT=/work/app -e PIXELTABLE_HOME=/work/catalog \
+  -v /absolute/path/to/pixeltable-app:/work/app \
+  -v /absolute/path/to/.pixeltable:/work/catalog \
+  mcp-server-pixeltable-developer
+```
+
+Configure a client to launch the server over `stdio`. Replace the application
+project and catalog paths with absolute paths:
+
+```json
+{
+  "mcpServers": {
+    "pixeltable": {
+      "command": "uvx",
+      "args": ["mcp-server-pixeltable-developer"],
+      "env": {
+        "PIXELTABLE_MCP_PROJECT_ROOT": "/absolute/path/to/pixeltable-app",
+        "PIXELTABLE_HOME": "/absolute/path/to/.pixeltable"
+      }
+    }
+  }
+}
+```
+
+Claude Code:
+
+```bash
+claude mcp add pixeltable -e PIXELTABLE_MCP_PROJECT_ROOT=/absolute/path/to/pixeltable-app -e PIXELTABLE_HOME=/absolute/path/to/.pixeltable -- uvx mcp-server-pixeltable-developer
+```
+
+To run a clone instead, use `"command": "uv"` with
+`"args": ["run", "--directory", "/absolute/path/to/mcp-server-pixeltable-developer", "mcp-server-pixeltable-developer"]`.
+
+Restart the client after changing its MCP configuration. Keep one server
+process per catalog when performing schema or service mutations.
+
+The `pxt` CLI talks to one local daemon per port (22089 by default), and a
+`pxt` command from a different project root restarts that daemon. If you run
+`pxt` for another project while the server is working, its calls can fail with
+`RemoteDisconnected`. Give the server its own port by adding
+`"PXT_PORT": "22090"` (any free port) to `env`.
+
+## Default interface
+
+Version 0.2 exposes a focused interface instead of mirroring the whole
+Pixeltable Python API.
+
+### Tools
+
+| Area | Tools |
+|---|---|
+| Inspect | `pixeltable_list_catalog`, `pixeltable_describe`, `pixeltable_rows`, `pixeltable_get_row`, `pixeltable_errors` |
+| Data | `pixeltable_insert_rows`, `pixeltable_recompute` |
+| App scaffold | `pixeltable_scaffold_app` |
+| Schema lifecycle | `pixeltable_schema_check`, `pixeltable_schema_diff`, `pixeltable_schema_update`, `pixeltable_schema_prune` |
+| Service lifecycle | `pixeltable_service_check`, `pixeltable_service_diff`, `pixeltable_service_update`, `pixeltable_service_list`, `pixeltable_service_stop`, `pixeltable_service_prune` |
+
+Read tools declare read-only MCP annotations. Mutation tools declare their
+write and destructive behavior. Arguments and results use typed schemas, and
+recoverable failures are returned as MCP tool errors so clients can retry with
+corrected input.
+
+### Resources
+
+| URI | Purpose |
+|---|---|
+| `pixeltable://status` | Server, dependency, transport, catalog, and unsafe-mode status |
+| `pixeltable://catalog` | Current catalog inventory |
+| `pixeltable://guidance/app` | Pixeltable 0.7 application workflow |
+| `pixeltable://guidance/cloud` | Cloud preparation guidance; it does not deploy resources |
+
+### Prompts
+
+- `pixeltable_build_app`
+- `pixeltable_build_rag`
+- `pixeltable_build_agent`
+- `pixeltable_debug_computation`
+
+The prompts are short task guides aligned with pixeltable-skill 2.12.0. The
+skill remains the detailed source for provider output shapes, multimodal views,
+indexes, tool calling, serving, debugging, and Cloud workflows.
+
+## Unsafe mode
+
+Host-code execution, package installation, and browser display are disabled by
+default. A trusted local user can opt in before starting the server:
+
+```bash
+export PIXELTABLE_MCP_ENABLE_UNSAFE=1
+```
+
+This adds:
+
+- `pixeltable_unsafe_execute_python`
+- `pixeltable_unsafe_install_package`
+- `pixeltable_unsafe_display`
+
+These tools are available only on `stdio`. They can execute arbitrary Python,
+change the server environment, read files available to the server process, and
+render untrusted content. Enable them only for a trusted, local MCP client and
+a disposable development environment. Do not expose unsafe mode through an
+HTTP transport.
+
+The repository may use an in-process or HTTP harness in tests. HTTP is not a
+supported production transport for version 0.2. A future HTTP release must add
+authorization, concurrency and request limits, origin and host validation,
+per-principal isolation, and an explicit threat model before it is supported.
+
+## Recommended Pixeltable workflow
+
+Start an application with the current Pixeltable CLI:
+
+```bash
+pip install 'pixeltable[serve]>=0.7.10,<0.8'
+pxt init
+pxt service example --out app.py
+pxt schema check app.py
+pxt schema diff app.py my_app
+pxt schema update app.py my_app
+pxt service check app.py
+pxt service update app.py my_app
+pxt service list
+```
+
+`my_app` is a catalog directory. It is not a filesystem directory. Edit
+`app.py` and apply the schema again when the model changes. Apply the service
+again after route changes. Use `pxt service list` to discover the assigned URL.
+
+The application file should declare `TableModel` classes and, when HTTP routes
+are needed, a `FastAPIRouter`. Stored columns use annotations. Computed columns
+use assignments. Types are non-nullable by default; write `T | None` for an
+optional column. Do not use `pxt.Required`.
+
+Schema updates intentionally require a review step. `schema_check` validates
+the file, `schema_diff` previews catalog changes, and `schema_update` applies
+them. Prune operations are separate because they can remove catalog objects.
+To change a computed-column expression, edit it and apply the schema again:
+the update keeps existing values, so run `pxt recompute my_app/docs COLUMN -f`
+to refresh them. Changing a column's type is unsupported in place; rename a
+computed column instead.
+
+For Cloud, prepare the same `app.py`, sign in with `pxt login` (or set
+`PIXELTABLE_API_KEY`), declare the target `pxt://org:db` in `pixeltable.toml`,
+and review `pixeltable://guidance/cloud`. The MCP server does not create paid
+resources or deploy to Cloud automatically.
+
+## Develop and verify
+
+Use a disposable catalog:
+
+```bash
+export PIXELTABLE_MCP_PROJECT_ROOT="$PWD"
+export PIXELTABLE_HOME="$(mktemp -d)/catalog"
+uv sync --frozen --extra test
+uv run pytest -q
+PIXELTABLE_DISABLE_STDOUT=1 uv run pytest --run-slow -q
+uv run python list_tools.py
+./scripts/run-conformance.sh
+./scripts/build-mcpb.sh
+```
+
+`build-mcpb.sh` writes the desktop-extension bundle to `dist/` from tracked files
+only. Pushing a `v*` tag publishes to PyPI through trusted publishing once the test,
+quality, bounds, conformance, and evaluation-artifact jobs pass; register this
+repository, workflow `ci.yml`, and environment `pypi` as a trusted publisher on
+PyPI one time before the first tag.
+
+Run the MCP Inspector only as a local test harness:
+
+```bash
+uv run mcp dev src/mcp_server_pixeltable_developer/server.py:mcp
+```
+
+Before release, also run the latest-dependency compatibility job, the MCP
+in-memory contract tests, the subprocess `stdio` smoke test, lint, type checks,
+and package build verification described in the review report.
+
+## Privacy Policy
+
+The server runs entirely on the machine that starts it. It collects no telemetry
+and no analytics, and it sends nothing to Pixeltable or to any third party.
+
+**What it handles.** The Pixeltable catalog at `PIXELTABLE_HOME` and the
+application files under `PIXELTABLE_MCP_PROJECT_ROOT`, both chosen by you. Tool
+results are returned to the MCP client that launched the server, which is how
+your assistant reads them. Nothing else receives them.
+
+**Storage and retention.** The server stores nothing of its own. Catalog data
+stays in `PIXELTABLE_HOME` on your disk, under your control, and is removed when
+you remove it.
+
+**Secrets.** Command output is passed through a redactor that masks common
+credential forms, including URL passwords and API tokens, before it reaches the
+client.
+
+**Third parties.** If your application declares computed columns that call model
+providers, Pixeltable makes those calls with the credentials you configured. That
+traffic is your application's, not this server's.
+
+**Unsafe mode.** With `PIXELTABLE_MCP_ENABLE_UNSAFE=1`, the added tools execute
+arbitrary Python, install packages, and read files available to the server
+process. Enable it only on a trusted local machine.
+
+**Contact.** Report privacy questions through
+[GitHub issues](https://github.com/pixeltable/mcp-server-pixeltable-developer/issues).
+
+## Documentation
+
+- [0.1.0 evidence review](docs/review-0.1.0.md)
+- [0.2.0 implementation review](docs/review-0.2.0.md)
+- [Migration from 0.1 to 0.2](docs/migration-0.1-to-0.2.md)
+- [Agent evaluation protocol](evals/README.md)
+- [Pixeltable documentation](https://docs.pixeltable.com/)
+- [Pixeltable get started](https://www.pixeltable.com/get-started.md)
+- [Pixeltable LLM reference](https://www.pixeltable.com/llms.txt)
+- [MCP Python SDK 2 documentation](https://py.sdk.modelcontextprotocol.io/v2/)
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).