mcp-server-pixeltable-developerCAUTION
A local Model Context Protocol server for building, inspecting, and operating Pixeltable applications.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A local Model Context Protocol server for building, inspecting, and operating Pixeltable applications. Version 0.2 follows the application-first workflow in pixeltable-skill 2.12.0: generate one app.py, apply its schema, and serve its routes with the pxt CLI.
Compatibility
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`, then run the server from PyPI:
uvx mcp-server-pixeltable-developer --version
For reproducible development from a clone:
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:
docker build -t mcp-server-pixeltable-developer . docker run --rm -i \ -e PIXELTABLE_MCP_PROJECT_ROOT=/work/app -e PI
c14b371c48f3OBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-server-pixeltable-developer -- uvx mcp-server-pixeltable-developer==0.2.1
Exposed tools (8)
5 read · 3 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
pixeltable_describe | read | table_path = config.validate_catalog_path(path) |
pixeltable_schema_check | read | file_label = _project_label(config, schema_file) |
pixeltable_service_check | read | file_label = _project_label(config, app_file) |
pixeltable_service_list | read | arguments = [ |
pixeltable_service_stop | write | validated_names = [_validate_service_reference(name) for name in names] |
test_missing_capability | read | capabilities = ctx.session.client_capabilities |
test_trigger_prompt_change | write | server.add_prompt(Prompt.from_function(dynamic_prompt, name= |
test_trigger_tool_change | write | server.add_tool(dynamic_tool, name= |
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (8 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (6)
--url "http://127.0.0.1:${domain_port}/mcp" \--url "http://127.0.0.1:${fixture_port}/mcp" \self.origin = f"http://127.0.0.1:{self.port}"audio.wav
assert "eval(" not in safe_sourceassert "exec(" not in safe_sourceGates applied: no_behavioural_pass.
c14b371c48f3full audit observations/trust-audit/mcp-server/pixeltable__mcp-server-pixeltable-developer.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | c14b371c48f3 | CAUTION | B | 89 | first audit |
Questions
What is the mcp-server-pixeltable-developer MCP server?
A local Model Context Protocol server for building, inspecting, and operating Pixeltable applications.
What tools does mcp-server-pixeltable-developer expose?
8 in total: 5 read-only, 3 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is mcp-server-pixeltable-developer safe to connect to an agent?
With care. The audit graded it B (89/100) and found 6 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does mcp-server-pixeltable-developer need?
It reads EXAMPLE_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does mcp-server-pixeltable-developer run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on PyPI as mcp-server-pixeltable-developer.
How current is this page?
The grade is for one exact copy of the source (c14b371c48f3), read on 2026-10-10. The repository is watched and re-audited when it changes.