sg-mcp-server 0.1.0__tar.gz

sg_mcp_server-0.1.0/.gitignore

@@ -0,0 +1,46 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+dist/
+.eggs/
+*.egg-info/
+*.egg
+
+# Virtual environments
+.venv/
+venv/
+ENV/
+
+# PyInstaller
+*.manifest
+*.spec
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage*
+.pytest_cache/
+.cache/
+
+# Type checker / linter caches
+.pyright/
+.mypy_cache/
+.ruff_cache/
+pyrightconfig.json
+
+# Editors
+.vscode/
+.idea/
+
+# OS
+.DS_Store
+Thumbs.db

sg_mcp_server-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 the sg-mcp-server authors
+
+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.

sg_mcp_server-0.1.0/PKG-INFO

@@ -0,0 +1,174 @@
+Metadata-Version: 2.5
+Name: sg-mcp-server
+Version: 0.1.0
+Summary: Read-only MCP server for Autodesk Flow Production Tracking
+Project-URL: Documentation, https://github.com/dactylo/sg-mcp-server/tree/main/docs
+Project-URL: Homepage, https://github.com/dactylo/sg-mcp-server
+Project-URL: Issues, https://github.com/dactylo/sg-mcp-server/issues
+Project-URL: Repository, https://github.com/dactylo/sg-mcp-server
+License-Expression: MIT
+License-File: LICENSE
+Keywords: flow-production-tracking,mcp,server,shotgrid,shotgun
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: anyio>=4.9
+Requires-Dist: jsonschema>=4.20
+Requires-Dist: mcp<3,>=2
+Requires-Dist: tzdata
+Provides-Extra: official
+Requires-Dist: shotgun-api3>=3.10.2; extra == 'official'
+Description-Content-Type: text/markdown
+
+# sg-mcp-server
+
+sg-mcp-server lets an AI assistant answer questions about your Autodesk Flow Production Tracking
+site. Connect it to an MCP (Model Context Protocol) client, ask in plain language, and the
+assistant looks up your site's live schema and records instead of guessing at entity types, field
+names, or status values.
+
+The server gives the client three read-only tools over MCP stdio: `sg_schema` explores entity types
+and fields, `sg_query` runs bounded queries, and `sg_get` opens one record with its web link. Every
+query is checked against your site's schema first: a misspelled field name returns a list of valid
+alternatives and is never silently replaced.
+
+This documentation uses SG for Flow Production Tracking, formerly named Shotgun and ShotGrid.
+
+## Security model
+
+sg-mcp-server is read-only: it has no tools that create, change, or delete records. Every request
+runs as one SG script (`ApiUser`) and sees what that script's permissions allow. The server does
+not act as the person asking the question, so anyone who can use the MCP client can read anything
+the script can read. Give the script access only to the data you intend to expose, and keep its key
+in your client's private configuration.
+
+The server appends every tool call to a local security audit, `~/.sg-mcp-server/audit.jsonl` by
+default. Each entry records the script name, tool, outcome, duration, and returned record IDs, with
+a hash of the request instead of its contents. If an audit write fails, the server warns on
+standard error and still answers, so that call is missing from the audit.
+
+An assistant can still misread a result or answer from incomplete data. In the
+[interface study](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/benchmarks.md), no tested model answered every task correctly, so check
+important answers against the records the tools return.
+
+## Installation
+
+You need:
+
+- Python 3.11 or newer and [uv](https://docs.astral.sh/uv/).
+- An MCP client that can start a local stdio server.
+- An SG site reachable from this machine, with a script name and API key that can read the data you
+  want to ask about.
+
+From a checkout of this repository, install the command with the official SG client:
+
+```sh
+uv tool install '.[official]'
+```
+
+The `official` extra installs `shotgun-api3`, the Autodesk Python API the server uses to reach your
+site. The base package does not include an SG client; without one, the server stops at startup with
+an error that names the `official` extra.
+
+After updating the checkout, update the installed command:
+
+```sh
+uv tool install --reinstall '.[official]'
+```
+
+`make install` and `make reinstall` run the same commands. Run `sg-mcp-server --version` to check
+the installed version. If your MCP client cannot find `sg-mcp-server`, give it the full path in the
+directory that `uv tool dir --bin` prints.
+
+## Quick start
+
+### Add the server to your MCP client
+
+Add a stdio server to your client's MCP configuration. This example uses the common `mcpServers`
+JSON shape; place it where your client expects MCP servers:
+
+```json
+{
+  "mcpServers": {
+    "sg": {
+      "command": "sg-mcp-server",
+      "env": {
+        "SG_MCP_SITE_URL": "https://yoursite.shotgunstudio.com",
+        "SG_MCP_SCRIPT_NAME": "your-script-name",
+        "SG_MCP_API_KEY": "your-script-key"
+      }
+    }
+  }
+}
+```
+
+Replace the three values with your site's address, script name, and API key. `SG_MCP_SITE_URL` must
+be the bare HTTPS site address, with no path, query, or fragment. Restart or reconnect the client
+so that it starts the server; the server runs until the client disconnects.
+
+The server checks its settings when it starts and stops with a one-line `error:` message if one is
+missing or invalid; [Troubleshooting](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/usage.md#troubleshooting) lists the causes. It does not
+contact your site until the first tool call, so a wrong key or an unreachable site appears as an
+error on your first question, not as a startup failure.
+
+### Ask your first question
+
+Ask the assistant:
+
+```text
+Which projects can this script see?
+```
+
+The assistant typically calls `sg_schema` to confirm the Project entity, then `sg_query` to list
+Projects, and answers with project names from your site. A list of names means the server is
+working. The exact answer depends on your site's records and the script's permissions.
+
+Next, ask "What fields are available on Shot?" to explore your site's schema before asking about
+site-specific fields. [Using the server](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/usage.md) has more example questions, direct
+tool-call arguments, and every setting.
+
+## What the tools do
+
+| Tool        | Use it for                                                                                    |
+| ----------- | --------------------------------------------------------------------------------------------- |
+| `sg_schema` | List entity types, describe one entity's fields, or search field names and labels.            |
+| `sg_query`  | Find records with validated filters, sorting, and a row limit, or request one native summary. |
+| `sg_get`    | Fetch one record by entity type and numeric ID, including its web URL.                        |
+
+A query returns at most 50 records unless it asks for a different limit, and never more than 200;
+you can change both limits. When more records match, the result says so and suggests narrowing the
+filters or requesting a summary, so the assistant does not mistake one page for every match.
+
+## Documentation
+
+| If you want to...                                                  | Read                                             |
+| ------------------------------------------------------------------ | ------------------------------------------------ |
+| Find example questions and tool-call arguments                     | [Using the server](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/usage.md)                |
+| Change the time zone, limits, timeout, audit path, or schema cache | [Settings](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/usage.md#settings)               |
+| Fix a request that fails or a server that will not start           | [Troubleshooting](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/usage.md#troubleshooting) |
+| Find out where a slow request spends its time                      | [Latency diagnostics](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/diagnostics.md)       |
+| Understand the three-tool design and model reliability             | [Interface study](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/benchmarks.md)            |
+| See changes by version                                             | [Changelog](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/CHANGELOG.md)                        |
+
+## Development
+
+See the [development guide](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/docs/development.md) for the required tools, CI, and dependency locks.
+With those tools installed, run:
+
+```sh
+make setup
+make check
+```
+
+The checks never contact a live SG site.
+
+## License
+
+sg-mcp-server is available under the [MIT License](https://github.com/dactylo/sg-mcp-server/blob/v0.1.0/LICENSE). It is an independent project and is
+not affiliated with or endorsed by Autodesk. Flow Production Tracking is a product of Autodesk,
+Inc.

sg_mcp_server-0.1.0/README.md

@@ -0,0 +1,147 @@
+# sg-mcp-server
+
+sg-mcp-server lets an AI assistant answer questions about your Autodesk Flow Production Tracking
+site. Connect it to an MCP (Model Context Protocol) client, ask in plain language, and the
+assistant looks up your site's live schema and records instead of guessing at entity types, field
+names, or status values.
+
+The server gives the client three read-only tools over MCP stdio: `sg_schema` explores entity types
+and fields, `sg_query` runs bounded queries, and `sg_get` opens one record with its web link. Every
+query is checked against your site's schema first: a misspelled field name returns a list of valid
+alternatives and is never silently replaced.
+
+This documentation uses SG for Flow Production Tracking, formerly named Shotgun and ShotGrid.
+
+## Security model
+
+sg-mcp-server is read-only: it has no tools that create, change, or delete records. Every request
+runs as one SG script (`ApiUser`) and sees what that script's permissions allow. The server does
+not act as the person asking the question, so anyone who can use the MCP client can read anything
+the script can read. Give the script access only to the data you intend to expose, and keep its key
+in your client's private configuration.
+
+The server appends every tool call to a local security audit, `~/.sg-mcp-server/audit.jsonl` by
+default. Each entry records the script name, tool, outcome, duration, and returned record IDs, with
+a hash of the request instead of its contents. If an audit write fails, the server warns on
+standard error and still answers, so that call is missing from the audit.
+
+An assistant can still misread a result or answer from incomplete data. In the
+[interface study](docs/benchmarks.md), no tested model answered every task correctly, so check
+important answers against the records the tools return.
+
+## Installation
+
+You need:
+
+- Python 3.11 or newer and [uv](https://docs.astral.sh/uv/).
+- An MCP client that can start a local stdio server.
+- An SG site reachable from this machine, with a script name and API key that can read the data you
+  want to ask about.
+
+From a checkout of this repository, install the command with the official SG client:
+
+```sh
+uv tool install '.[official]'
+```
+
+The `official` extra installs `shotgun-api3`, the Autodesk Python API the server uses to reach your
+site. The base package does not include an SG client; without one, the server stops at startup with
+an error that names the `official` extra.
+
+After updating the checkout, update the installed command:
+
+```sh
+uv tool install --reinstall '.[official]'
+```
+
+`make install` and `make reinstall` run the same commands. Run `sg-mcp-server --version` to check
+the installed version. If your MCP client cannot find `sg-mcp-server`, give it the full path in the
+directory that `uv tool dir --bin` prints.
+
+## Quick start
+
+### Add the server to your MCP client
+
+Add a stdio server to your client's MCP configuration. This example uses the common `mcpServers`
+JSON shape; place it where your client expects MCP servers:
+
+```json
+{
+  "mcpServers": {
+    "sg": {
+      "command": "sg-mcp-server",
+      "env": {
+        "SG_MCP_SITE_URL": "https://yoursite.shotgunstudio.com",
+        "SG_MCP_SCRIPT_NAME": "your-script-name",
+        "SG_MCP_API_KEY": "your-script-key"
+      }
+    }
+  }
+}
+```
+
+Replace the three values with your site's address, script name, and API key. `SG_MCP_SITE_URL` must
+be the bare HTTPS site address, with no path, query, or fragment. Restart or reconnect the client
+so that it starts the server; the server runs until the client disconnects.
+
+The server checks its settings when it starts and stops with a one-line `error:` message if one is
+missing or invalid; [Troubleshooting](docs/usage.md#troubleshooting) lists the causes. It does not
+contact your site until the first tool call, so a wrong key or an unreachable site appears as an
+error on your first question, not as a startup failure.
+
+### Ask your first question
+
+Ask the assistant:
+
+```text
+Which projects can this script see?
+```
+
+The assistant typically calls `sg_schema` to confirm the Project entity, then `sg_query` to list
+Projects, and answers with project names from your site. A list of names means the server is
+working. The exact answer depends on your site's records and the script's permissions.
+
+Next, ask "What fields are available on Shot?" to explore your site's schema before asking about
+site-specific fields. [Using the server](docs/usage.md) has more example questions, direct
+tool-call arguments, and every setting.
+
+## What the tools do
+
+| Tool        | Use it for                                                                                    |
+| ----------- | --------------------------------------------------------------------------------------------- |
+| `sg_schema` | List entity types, describe one entity's fields, or search field names and labels.            |
+| `sg_query`  | Find records with validated filters, sorting, and a row limit, or request one native summary. |
+| `sg_get`    | Fetch one record by entity type and numeric ID, including its web URL.                        |
+
+A query returns at most 50 records unless it asks for a different limit, and never more than 200;
+you can change both limits. When more records match, the result says so and suggests narrowing the
+filters or requesting a summary, so the assistant does not mistake one page for every match.
+
+## Documentation
+
+| If you want to...                                                  | Read                                             |
+| ------------------------------------------------------------------ | ------------------------------------------------ |
+| Find example questions and tool-call arguments                     | [Using the server](docs/usage.md)                |
+| Change the time zone, limits, timeout, audit path, or schema cache | [Settings](docs/usage.md#settings)               |
+| Fix a request that fails or a server that will not start           | [Troubleshooting](docs/usage.md#troubleshooting) |
+| Find out where a slow request spends its time                      | [Latency diagnostics](docs/diagnostics.md)       |
+| Understand the three-tool design and model reliability             | [Interface study](docs/benchmarks.md)            |
+| See changes by version                                             | [Changelog](CHANGELOG.md)                        |
+
+## Development
+
+See the [development guide](docs/development.md) for the required tools, CI, and dependency locks.
+With those tools installed, run:
+
+```sh
+make setup
+make check
+```
+
+The checks never contact a live SG site.
+
+## License
+
+sg-mcp-server is available under the [MIT License](LICENSE). It is an independent project and is
+not affiliated with or endorsed by Autodesk. Flow Production Tracking is a product of Autodesk,
+Inc.

sg_mcp_server-0.1.0/pyproject.toml

@@ -0,0 +1,189 @@
+# ==========================================================
+# Build System
+# ==========================================================
+[build-system]
+build-backend = "hatchling.build"
+requires = [ "editables~=0.3", "hatch-fancy-pypi-readme>=25.1", "hatchling>=1.27" ]
+
+# ==========================================================
+# Project Metadata
+# ==========================================================
+[project]
+name = "sg-mcp-server"
+version = "0.1.0"
+description = "Read-only MCP server for Autodesk Flow Production Tracking"
+keywords = [ "flow-production-tracking", "mcp", "server", "shotgrid", "shotgun" ]
+license = "MIT"
+license-files = [ "LICENSE" ]
+requires-python = ">=3.11"
+classifiers = [
+  "Programming Language :: Python :: 3 :: Only",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Programming Language :: Python :: 3.14",
+  "Programming Language :: Python :: 3.15",
+  "Typing :: Typed",
+]
+dynamic = [ "readme" ]
+dependencies = [
+  "anyio>=4.9",
+  "jsonschema>=4.20",
+  "mcp>=2,<3",
+  "tzdata",
+]
+optional-dependencies.official = [
+  "shotgun-api3>=3.10.2",
+]
+urls.Documentation = "https://github.com/dactylo/sg-mcp-server/tree/main/docs"
+urls.Homepage = "https://github.com/dactylo/sg-mcp-server"
+urls.Issues = "https://github.com/dactylo/sg-mcp-server/issues"
+urls.Repository = "https://github.com/dactylo/sg-mcp-server"
+scripts.sg-mcp-server = "sg_mcp_server:main"
+
+[dependency-groups]
+dev = [
+  "mdformat",
+  "mdformat-config",
+  "mdformat-frontmatter",
+  "mdformat-gfm",
+  "mdformat-pyproject",
+  "mdformat-ruff",
+  "mdformat-shfmt",
+  "pyproject-fmt",
+  "pyright",
+  "ruff",
+  { include-group = "test" },
+]
+test = [
+  "pytest",
+  "pytest-xdist>=3.2",
+]
+ci-build = [
+  "maturin>=1.10,<2",
+]
+
+[tool.hatch]
+metadata.hooks.fancy-pypi-readme.content-type = "text/markdown"
+metadata.hooks.fancy-pypi-readme.fragments = [ { path = "README.md" } ]
+build.targets.wheel.packages = [ "src/sg_mcp_server" ]
+build.targets.sdist.include = [ "/README.md", "/src" ]
+
+# Keep checkout links relative; package links target this release.
+[[tool.hatch.metadata.hooks.fancy-pypi-readme.substitutions]]
+pattern = '(!\[[^\]\n]*\]\()(?![A-Za-z][A-Za-z0-9+.-]*:|[/#])(?:\./)?([^\s)]+)(\))'
+replacement = '\1https://raw.githubusercontent.com/dactylo/sg-mcp-server/v$HFPR_VERSION/\2\3'
+
+[[tool.hatch.metadata.hooks.fancy-pypi-readme.substitutions]]
+pattern = '(?<!!)(\[[^\]\n]+\]\()(?![A-Za-z][A-Za-z0-9+.-]*:|[/#])(?:\./)?([^\s)]+)(\))'
+replacement = '\1https://github.com/dactylo/sg-mcp-server/blob/v$HFPR_VERSION/\2\3'
+
+[tool.uv]
+# CI supplies the native Taplo CLI; its Python package lacks Linux/Windows ARM wheels.
+exclude-dependencies = [
+  { package = { name = "mdformat-config", version = "0.2.1" }, dependencies = [ "taplo" ] },
+]
+
+# ==========================================================
+# Ruff Configuration
+# ==========================================================
+[tool.ruff]
+target-version = "py311"
+line-length = 99
+format.quote-style = "single"
+format.exclude = [ "*.md" ]
+lint.select = [ "ALL" ]
+lint.ignore = [
+  "COM812", # Conflicts with the Ruff formatter
+  "CPY001", # Copyright notices are not required
+  "EM101",  # Exception must not use string literal
+  "EM102",  # Exception must not use f-string literal
+  "FBT001", # Boolean positional arg in function definition
+  "FBT002", # Boolean default value in function definition
+  "Q000",   # Conflicts with the Ruff formatter
+  "Q003",   # Conflicts with the Ruff formatter
+  "T201",   # print() found
+  "TRY003", # Avoid specifying long messages outside exception class
+]
+# Exact-file exceptions for same-file private collaboration, intentional output, and tests.
+lint.per-file-ignores."experiments/arms/_arm_b.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/arms/_arm_d.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/arms/_arm_e.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/bakeoff/dataset/seed.py" = [ "T201" ]
+lint.per-file-ignores."experiments/bakeoff/driver.py" = [ "T201" ]
+lint.per-file-ignores."experiments/bakeoff/fixtures/augment_schema.py" = [ "T201" ]
+lint.per-file-ignores."experiments/bakeoff/harness/_questions.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/bakeoff/harness/_schema_tools.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/bakeoff/harness/runner.py" = [ "SLF001", "T201" ]
+lint.per-file-ignores."experiments/model_benchmark/_artifacts.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_budget.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_claude.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_cli.py" = [ "T201" ]
+lint.per-file-ignores."experiments/model_benchmark/_codex.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_interface_aggregation.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_interface_gate.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_interface_replay.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_live.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_realism.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_report.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_runner.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/model_benchmark/_subprocess.py" = [ "SLF001" ]
+lint.per-file-ignores."experiments/tests/**/*.py" = [
+  "D",       # No docstrings required in tests
+  "PLR2004", # Allow magic values in tests
+  "S101",    # Allow asserts in tests
+  "S603",    # Allow subprocess calls in tests
+  "SLF001",  # Tests intentionally inspect and patch private state
+]
+# Fake-host CLI responses intentionally use stdout.
+lint.per-file-ignores."experiments/tests/model_benchmark/fake_claude.py" = [ "T201" ]
+lint.per-file-ignores."experiments/tests/model_benchmark/fake_codex.py" = [ "T201" ]
+lint.per-file-ignores."scripts/diagnose_live_latency.py" = [ "T201" ]
+lint.per-file-ignores."scripts/smoke_test_live.py" = [ "SLF001", "T201" ]
+lint.per-file-ignores."src/sg_mcp_server/_audit.py" = [ "T201" ]
+lint.per-file-ignores."src/sg_mcp_server/_diagnostics.py" = [ "T201" ]
+lint.per-file-ignores."src/sg_mcp_server/_engine/_validation.py" = [ "SLF001" ]
+lint.per-file-ignores."src/sg_mcp_server/_rendering.py" = [ "SLF001" ]
+lint.per-file-ignores."tests/**/*.py" = [
+  "D",       # No docstrings required in tests
+  "PLR2004", # Allow magic values in tests
+  "S101",    # Allow asserts in tests
+  "S603",    # Allow subprocess calls in tests
+  "S607",    # Allow partial executable paths in tests
+  "SLF001",  # Tests intentionally inspect and patch private state
+]
+lint.pydocstyle.convention = "google"
+
+[tool.pyproject-fmt]
+max_supported_python = "3.15"
+
+# ==========================================================
+# Pyright Configuration
+# ==========================================================
+[tool.pyright]
+pythonVersion = "3.11"  # Keep in sync with tool.ruff.target-version
+typeCheckingMode = "strict"
+extraPaths = [ ".", "src" ]
+executionEnvironments = [
+  { root = "tests/scripts", reportPrivateUsage = "none" },
+  { root = "tests", reportPrivateUsage = "none" },
+  { root = "experiments/tests", reportPrivateUsage = "none" },
+  { root = "." },
+]
+
+# ==========================================================
+# Pytest Configuration
+# ==========================================================
+[tool.pytest]
+ini_options.testpaths = [ "tests" ]
+ini_options.pythonpath = [ "src", "tests" ]
+ini_options.addopts = [ "-q", "--strict-markers", "--tb=short" ]
+ini_options.markers = [ "slow: marks tests as slow (deselect with '-m \"not slow\"')" ]
+ini_options.faulthandler_timeout = 300
+
+# ==========================================================
+# Mdformat Configuration (Requires mdformat-pyproject)
+# ==========================================================
+[tool.mdformat]
+wrap = 99  # Keep in sync with tool.ruff.line-length
+number = true

sg_mcp_server-0.1.0/src/sg_mcp_server/__init__.py

@@ -0,0 +1,19 @@
+"""Provide the read-only MCP server for Flow Production Tracking.
+
+Run `sg-mcp-server`, run `python -m sg_mcp_server`, or call `main()` to serve
+the solo-mode tool surface over stdio in the foreground. `main()` parses
+`sys.argv` unless given an argument list, accepts no arguments other than
+`--help` and `--version`, and returns the process exit status. `--help` and
+invalid arguments end in `SystemExit` from argument parsing; `--version`
+returns 0 after printing the version.
+
+Set `SG_MCP_SITE_URL`, `SG_MCP_SCRIPT_NAME`, and `SG_MCP_API_KEY` for the site
+connection. Optional `SG_MCP_TIMEZONE`, `SG_MCP_AUDIT_PATH`,
+`SG_MCP_DEFAULT_LIMIT`, `SG_MCP_HARD_LIMIT`, `SG_MCP_SCHEMA_TTL_SECONDS`,
+`SG_MCP_TIMEOUT_SECONDS`, and `SG_MCP_DIAGNOSTICS_PATH` settings control
+rendering, logging, query limits, the SG request timeout, and schema caching.
+"""
+
+from sg_mcp_server._cli import main
+
+__all__ = ['main']

sg_mcp_server-0.1.0/src/sg_mcp_server/__main__.py

@@ -0,0 +1,13 @@
+"""Serve the read-only solo-mode MCP tools over stdio.
+
+Run `python -m sg_mcp_server` with `SG_MCP_SITE_URL`, `SG_MCP_SCRIPT_NAME`, and
+`SG_MCP_API_KEY` set. The command uses the same optional environment settings
+as `sg-mcp-server` and runs the server in the foreground.
+"""
+
+import sys
+
+from sg_mcp_server._cli import main
+
+if __name__ == '__main__':
+    sys.exit(main())