tripl-mcp 0.1.0__tar.gz

tripl_mcp-0.1.0/.gitignore

@@ -0,0 +1,7 @@
+.venv/
+__pycache__/
+*.pyc
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+dist/

tripl_mcp-0.1.0/Dockerfile

@@ -0,0 +1,18 @@
+FROM python:3.13-slim
+
+COPY --from=ghcr.io/astral-sh/uv:latest /uv /usr/local/bin/uv
+
+WORKDIR /app
+ENV UV_COMPILE_BYTECODE=1 UV_LINK_MODE=copy
+
+COPY pyproject.toml uv.lock README.md ./
+COPY src ./src
+RUN uv sync --frozen --no-dev
+
+ENV PATH="/app/.venv/bin:$PATH"
+
+# stdio by default; compose sidecars override the command with flags only
+# (the ENTRYPOINT below already provides the `tripl-mcp` executable):
+#   command: ["--transport", "streamable-http", "--host", "0.0.0.0", "--port", "8765"]
+EXPOSE 8765
+ENTRYPOINT ["tripl-mcp"]

tripl_mcp-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 2026 Vladislav Denisov
+
+   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.

tripl_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,113 @@
+Metadata-Version: 2.4
+Name: tripl-mcp
+Version: 0.1.0
+Summary: Standalone MCP server exposing a curated agent toolset over the tripl REST API
+Project-URL: Homepage, https://vladenisov.github.io/tripl/
+Project-URL: Documentation, https://vladenisov.github.io/tripl/docs/integrate/mcp-server
+Project-URL: Repository, https://github.com/vladenisov/tripl
+Project-URL: Issues, https://github.com/vladenisov/tripl/issues
+Author: Vladislav Denisov
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: analytics,mcp,model-context-protocol,tracking-plan,tripl
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: mcp<2,>=1.9.0
+Description-Content-Type: text/markdown
+
+# tripl-mcp
+
+Standalone [MCP](https://modelcontextprotocol.io) server exposing a curated,
+agent-safe toolset over a **running tripl instance**. It is a pure HTTP client
+of the tripl REST API (`/api/v1`) — it imports no backend code and is not
+mounted into the FastAPI app.
+
+- 17 curated tools (14 read, 3 write): plan search, event read/write, event
+  types & fields, variables, branches & diffs, scans, monitors, reconciliation,
+  projects.
+- Read tools carry `readOnlyHint`; write tools require a `tk_w_` API key.
+- Plan-mutating tools **require `branch_id`** so an agent never edits the live
+  main plan by accident. Operators can override with `TRIPL_MCP_ALLOW_MAIN=1`.
+- Branch merge/revert/transition, SSE streams, and photo upload are
+  intentionally not exposed in v1.
+
+## stdio (Claude Code / Claude Desktop)
+
+> **Not on PyPI.** There is no `tripl-mcp` package on the index yet, so a bare
+> `uvx tripl-mcp` will not resolve. Install from git or from a checkout.
+
+From git — no clone needed:
+
+```json
+{
+  "mcpServers": {
+    "tripl": {
+      "command": "uvx",
+      "args": [
+        "--from",
+        "git+https://github.com/vladenisov/tripl.git#subdirectory=mcp-server",
+        "tripl-mcp"
+      ],
+      "env": {
+        "TRIPL_BASE_URL": "https://tripl.example.com",
+        "TRIPL_API_KEY": "tk_r_..."
+      }
+    }
+  }
+}
+```
+
+From a local checkout:
+
+```json
+{
+  "command": "uv",
+  "args": ["run", "--project", "/path/to/tripl/mcp-server", "tripl-mcp"]
+}
+```
+
+Create API keys in the tripl app under **Account → API keys**. Use a
+project-scoped `tk_r_` key for read-only agents; reserve `tk_w_` keys for
+agents explicitly allowed to edit the plan.
+
+## streamable-http (shared server)
+
+```bash
+TRIPL_BASE_URL=https://tripl.example.com tripl-mcp --transport streamable-http --port 8765
+```
+
+In this mode the server holds **no credentials**. Every incoming MCP request
+must carry `Authorization: Bearer tk_...`; the header is forwarded verbatim to
+the tripl API and never stored. Requests without it get a clear tool error.
+
+## Environment
+
+| Variable | Meaning |
+|----------|---------|
+| `TRIPL_BASE_URL` | Base URL of the tripl instance (required) |
+| `TRIPL_API_KEY` | API key for stdio mode (required for stdio) |
+| `TRIPL_MCP_ALLOW_MAIN` | Set to `1` to allow plan writes without `branch_id` (edits main) |
+
+## Development
+
+```bash
+cd mcp-server
+uv sync
+uv run pytest -q
+uv run ruff check .
+```
+
+## Docs
+
+Full agent workflow guidance lives in the website docs:
+`website/docs/integrate/agent-api-guide.md` and
+`website/docs/use-cases/llm-agent.md`.

tripl_mcp-0.1.0/README.md

@@ -0,0 +1,87 @@
+# tripl-mcp
+
+Standalone [MCP](https://modelcontextprotocol.io) server exposing a curated,
+agent-safe toolset over a **running tripl instance**. It is a pure HTTP client
+of the tripl REST API (`/api/v1`) — it imports no backend code and is not
+mounted into the FastAPI app.
+
+- 17 curated tools (14 read, 3 write): plan search, event read/write, event
+  types & fields, variables, branches & diffs, scans, monitors, reconciliation,
+  projects.
+- Read tools carry `readOnlyHint`; write tools require a `tk_w_` API key.
+- Plan-mutating tools **require `branch_id`** so an agent never edits the live
+  main plan by accident. Operators can override with `TRIPL_MCP_ALLOW_MAIN=1`.
+- Branch merge/revert/transition, SSE streams, and photo upload are
+  intentionally not exposed in v1.
+
+## stdio (Claude Code / Claude Desktop)
+
+> **Not on PyPI.** There is no `tripl-mcp` package on the index yet, so a bare
+> `uvx tripl-mcp` will not resolve. Install from git or from a checkout.
+
+From git — no clone needed:
+
+```json
+{
+  "mcpServers": {
+    "tripl": {
+      "command": "uvx",
+      "args": [
+        "--from",
+        "git+https://github.com/vladenisov/tripl.git#subdirectory=mcp-server",
+        "tripl-mcp"
+      ],
+      "env": {
+        "TRIPL_BASE_URL": "https://tripl.example.com",
+        "TRIPL_API_KEY": "tk_r_..."
+      }
+    }
+  }
+}
+```
+
+From a local checkout:
+
+```json
+{
+  "command": "uv",
+  "args": ["run", "--project", "/path/to/tripl/mcp-server", "tripl-mcp"]
+}
+```
+
+Create API keys in the tripl app under **Account → API keys**. Use a
+project-scoped `tk_r_` key for read-only agents; reserve `tk_w_` keys for
+agents explicitly allowed to edit the plan.
+
+## streamable-http (shared server)
+
+```bash
+TRIPL_BASE_URL=https://tripl.example.com tripl-mcp --transport streamable-http --port 8765
+```
+
+In this mode the server holds **no credentials**. Every incoming MCP request
+must carry `Authorization: Bearer tk_...`; the header is forwarded verbatim to
+the tripl API and never stored. Requests without it get a clear tool error.
+
+## Environment
+
+| Variable | Meaning |
+|----------|---------|
+| `TRIPL_BASE_URL` | Base URL of the tripl instance (required) |
+| `TRIPL_API_KEY` | API key for stdio mode (required for stdio) |
+| `TRIPL_MCP_ALLOW_MAIN` | Set to `1` to allow plan writes without `branch_id` (edits main) |
+
+## Development
+
+```bash
+cd mcp-server
+uv sync
+uv run pytest -q
+uv run ruff check .
+```
+
+## Docs
+
+Full agent workflow guidance lives in the website docs:
+`website/docs/integrate/agent-api-guide.md` and
+`website/docs/use-cases/llm-agent.md`.

tripl_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,82 @@
+[project]
+name = "tripl-mcp"
+version = "0.1.0"
+description = "Standalone MCP server exposing a curated agent toolset over the tripl REST API"
+readme = "README.md"
+requires-python = ">=3.12"
+# Apache-2.0 while the SERVICE is AGPL-3.0-or-later, and that split is
+# deliberate: this package is a standalone httpx client of the REST API — it
+# imports nothing from `tripl` — so a permissive licence lets anyone embed it in
+# their own agent without the service's copyleft reaching into their codebase.
+# Apache rather than MIT for the express patent grant.
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Vladislav Denisov" }]
+keywords = ["mcp", "model-context-protocol", "analytics", "tracking-plan", "tripl"]
+# Trove classifiers are what PyPI's sidebar and search filters read. No
+# "Private :: Do Not Upload" here on purpose — this package IS meant to be
+# installed by users (uvx tripl-mcp), unlike the service itself, which ships as
+# a container image.
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: Apache Software License",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Software Development :: Libraries",
+    "Typing :: Typed",
+]
+dependencies = [
+    # Upper bound is load-bearing, not caution: this package imports
+    # ``mcp.server.fastmcp``, which mcp 2.0 removed when it reorganised the
+    # server API (2.0 ships mcp.server.mcpserver instead). uv.lock pins 1.28.1
+    # so the repo and CI never see it, but a lockfile is not published — an
+    # installer resolving ">=1.9.0" alone gets 2.0 and the console script dies
+    # on import with ModuleNotFoundError. Caught by installing the built wheel
+    # into a clean venv before the first PyPI upload.
+    "mcp>=1.9.0,<2",
+    "httpx>=0.27.0",
+]
+
+[project.urls]
+Homepage = "https://vladenisov.github.io/tripl/"
+Documentation = "https://vladenisov.github.io/tripl/docs/integrate/mcp-server"
+Repository = "https://github.com/vladenisov/tripl"
+Issues = "https://github.com/vladenisov/tripl/issues"
+
+[project.scripts]
+tripl-mcp = "tripl_mcp.server:main"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.0",
+    "pytest-asyncio>=0.26",
+    "respx>=0.22",
+    "ruff>=0.4",
+    "mypy>=1.10",
+]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/tripl_mcp"]
+
+[tool.pytest.ini_options]
+asyncio_mode = "auto"
+testpaths = ["tests"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py312"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B", "SIM"]
+
+[tool.mypy]
+python_version = "3.12"
+strict = true
+ignore_missing_imports = true

tripl_mcp-0.1.0/src/tripl_mcp/__init__.py

@@ -0,0 +1,3 @@
+"""tripl-mcp — standalone MCP server that proxies a curated tripl REST toolset."""
+
+__version__ = "0.1.0"