Skip to main content

tripl-mcp

Standalone MCP 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:

{
  "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:

{
  "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)

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

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.

Metadata

Release files for tripl-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tripl-mcp 0.1.0
File Size Uploaded
tripl_mcp-0.1.0.tar.gz 76.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for tripl-mcp 0.1.0
File Interpreter ABI Platform
tripl_mcp-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 99.8 kB

Release files / tripl_mcp-0.1.0.tar.gz

Download URL tripl_mcp-0.1.0.tar.gz
Size 76.2 kB
Tags Source
SHA-256 checksum
How to use checksums
ba34e02213252e3d63f802b37a540104608709a4a159bd3ea0165c2748cf783c
BLAKE2b-256 checksum
How to use checksums
0c5ff186b2f7c63e532ba7ec71958442fead68c57c51d427dbeda86de21bdb2b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.

Transparency log

Release files / tripl_mcp-0.1.0-py3-none-any.whl

Download URL tripl_mcp-0.1.0-py3-none-any.whl
Size 23.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
305c6bd1ec0731566a8723c00524560bf0cbabe44da3119da51fb1a3c049109e
BLAKE2b-256 checksum
How to use checksums
c36954704a9950c9f5417d63fb804149084e1a45609b3e170b01f362ec72b567
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.2

2 release files

0.2.0

2 release files

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page