devtime-ei 0.1.0__tar.gz → 0.1.2__tar.gz

{devtime_ei-0.1.0 → devtime_ei-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devtime-ei
-Version: 0.1.0
+Version: 0.1.2
 Summary: Local-first Engineering Intelligence for software repositories
 Author-email: Aviad Shakargi <aviad94@gmail.com>
 Maintainer-email: Aviad Shakargi <aviad94@gmail.com>
@@ -8,7 +8,7 @@ License: Apache-2.0
 Project-URL: Homepage, https://github.com/Shakargy/devtime
 Project-URL: Repository, https://github.com/Shakargy/devtime
 Project-URL: Issues, https://github.com/Shakargy/devtime/issues
-Project-URL: Release Notes, https://github.com/Shakargy/devtime/releases/tag/v0.1.0
+Project-URL: Release Notes, https://github.com/Shakargy/devtime/releases/tag/v0.1.2
 Project-URL: Demo, https://youtu.be/1Hiu3Y9J_SI
 Keywords: devtools,cli,static-analysis,repository-analysis,engineering-intelligence,local-first
 Classifier: Development Status :: 3 - Alpha
@@ -30,8 +30,11 @@ Requires-Dist: pydantic>=2.7
 Requires-Dist: sqlalchemy>=2.0
 Requires-Dist: pyyaml>=6.0
 Requires-Dist: pathspec>=0.12
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.2; extra == "mcp"
 Provides-Extra: dev
 Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: mcp>=1.2; extra == "dev"
 Dynamic: license-file
 
 # DevTime
@@ -46,16 +49,32 @@ risky changes.
 
 > No cloud. No telemetry. No code execution. No AI required.
 
-[![DevTime demo - Repository memory from evidence](assets/devtime-demo-thumbnail-v0.1.0.png)](https://youtu.be/1Hiu3Y9J_SI)
+![DevTime terminal demo - install, scan, and explain a repo from evidence](assets/devtime-terminal-demo.svg)
 
-Watch the 2-minute demo: DevTime scans a repo locally, explains concepts from
-evidence, surfaces uncertainty, catches a risky diff, and shows how a corroborated
-decision improves understanding.
+Prefer video? [Watch the 2-minute demo](https://youtu.be/1Hiu3Y9J_SI): DevTime scans
+a repo locally, explains concepts from evidence, surfaces uncertainty, catches a
+risky diff, and shows how a corroborated decision improves understanding.
 
 ---
 
 ## Try DevTime in 60 seconds
 
+```bash
+pipx install devtime-ei
+dtc demo init
+cd devtime-demo-saas
+dtc init
+dtc scan
+dtc concepts
+dtc explain "Billing Webhooks"
+```
+
+The PyPI distribution is `devtime-ei`. The Python package remains `devtime`, and the
+CLI command remains `dtc`. `dtc demo init` copies a small static example repo into
+`./devtime-demo-saas` so you can try DevTime without cloning this repository.
+
+### From source
+
 ```bash
 git clone https://github.com/Shakargy/devtime.git
 cd devtime
@@ -98,27 +117,36 @@ steps) is in **[DEMO_SCRIPT.md](DEMO_SCRIPT.md)**.
 
 ## Why this exists
 
-Git remembers code. It does not remember understanding. It does not tell you why a
-behavior exists, what evidence supports it, or what nobody has decided yet. As AI
-tools generate code faster than teams can review it, that missing understanding
-becomes the bottleneck.
+Git records what changed, but it does not preserve the reasoning behind those
+changes. When you return to a repository - or review one you did not write - you often
+have to reconstruct why a behavior exists, what evidence supports it, and what is
+still uncertain.
 
-DevTime builds evidence-backed repository memory: a local layer that says what a
-repository can prove, and - just as importantly - what it cannot prove yet.
+DevTime builds evidence-backed repository memory: a local layer that helps a
+codebase explain itself from code, tests, configs, routes, and recorded decisions.
+It shows what the repository can support with evidence - and, just as importantly,
+what it cannot support yet.
 
 ## Who it is for
 
-DevTime is for developers reviewing unfamiliar code, teams using AI coding tools, and
-maintainers who want repository understanding to be backed by evidence instead of
-generated summaries.
+DevTime is for people who need to understand a repository from evidence rather than
+memory.
+
+It is especially useful if you:
+
+- are onboarding to an unfamiliar codebase and need to understand how a feature is implemented;
+- are reviewing a pull request and want to see what evidence supports a behavior;
+- are returning to a project after weeks or months and cannot remember why something exists;
+- maintain a long-lived project where design decisions are easily lost;
+- want repository understanding to be backed by code and recorded decisions instead of generated summaries.
 
-It is useful when you want to ask:
+Questions DevTime helps answer include:
 
-- where is authentication actually implemented?
-- what files prove that billing webhooks exist?
-- what is still uncertain?
-- did this diff touch a risky concept?
-- is there a decision explaining this behavior?
+- Where is authentication actually implemented?
+- What files prove that Billing Webhooks exist?
+- What is still uncertain?
+- Did this diff touch a risky concept?
+- Is there a decision explaining this behavior?
 
 ## What DevTime does
 
@@ -178,14 +206,75 @@ Anything outside these six is out of scope for V0. See [LIMITATIONS.md](LIMITATI
 | `dtc decision add` | Add a local decision record that can reduce uncertainty. |
 
 (Also available: `dtc evidence`, `dtc debt`, `dtc status`, `dtc doctor --privacy`,
-`dtc export`, `dtc reset`.)
+`dtc export`, `dtc reset`, `dtc mcp start`.)
 
 Requires **Python >= 3.11** and git. See **[QUICKSTART.md](QUICKSTART.md)** for a
 step-by-step first run and troubleshooting.
 
+## Use with coding agents (MCP)
+
+Your coding agent starts every session amnesiac about your repository and then
+guesses, confidently. DevTime gives it memory it can trust: a local, read-only MCP
+server that answers only with claims the repository can prove, plus explicit
+uncertainty for what it cannot.
+
+Install with MCP support and scan your repo:
+
+```bash
+pipx install "devtime-ei[mcp]"
+cd your-repo
+dtc init
+dtc scan
+```
+
+Add DevTime to Claude Code:
+
+```bash
+claude mcp add devtime -- dtc mcp start
+```
+
+Or in any MCP client that reads `.mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "devtime": {
+      "command": "dtc",
+      "args": ["mcp", "start"]
+    }
+  }
+}
+```
+
+The agent gets three read-only tools: `list_concepts`, `explain_concept`, and
+`get_context_pack` (governed context with do-not-change-without-review paths, tests
+to run, and agent guidance). Local stdio only - no network listener, no write tools,
+no source code returned, only evidence file paths.
+
+DevTime is listed in the official MCP Registry as `io.github.shakargy/devtime`.
+
+<!-- mcp-name: io.github.shakargy/devtime -->
+
 ## Installation
 
-Recommended source install for now:
+Recommended: install from PyPI with [pipx](https://pipx.pypa.io/) so the `dtc`
+command is available on your PATH in an isolated environment:
+
+```bash
+pipx install devtime-ei
+```
+
+Or with pip:
+
+```bash
+pip install devtime-ei
+```
+
+The PyPI distribution is `devtime-ei`. The Python package remains `devtime`, and the
+CLI command remains `dtc`. After installing, run `dtc demo init` to create a local
+example repo to try it on.
+
+### From source
 
 ```bash
 git clone https://github.com/Shakargy/devtime.git
@@ -205,12 +294,6 @@ python -m venv .venv
 pip install -e ".[dev]"
 ```
 
-Planned PyPI install (after the package is published and verified):
-
-```bash
-pipx install devtime
-```
-
 ## Example output
 
 ```
@@ -274,7 +357,7 @@ intentionally not built yet - in **[LIMITATIONS.md](LIMITATIONS.md)**.
 ## Roadmap
 
 This is an early, local-first V0 focused on being trustworthy before being large.
-Not yet built (intentionally): git-history signals, wired MCP transport, an AI
+Not yet built (intentionally): git-history signals, write-enabled MCP tools, an AI
 provider, a UI, and any cloud/team/enterprise features. See **[ROADMAP.md](ROADMAP.md)**.
 
 ## Contributing

{devtime_ei-0.1.0 → devtime_ei-0.1.2}/README.md

@@ -10,16 +10,32 @@ risky changes.
 
 > No cloud. No telemetry. No code execution. No AI required.
 
-[![DevTime demo - Repository memory from evidence](assets/devtime-demo-thumbnail-v0.1.0.png)](https://youtu.be/1Hiu3Y9J_SI)
+![DevTime terminal demo - install, scan, and explain a repo from evidence](assets/devtime-terminal-demo.svg)
 
-Watch the 2-minute demo: DevTime scans a repo locally, explains concepts from
-evidence, surfaces uncertainty, catches a risky diff, and shows how a corroborated
-decision improves understanding.
+Prefer video? [Watch the 2-minute demo](https://youtu.be/1Hiu3Y9J_SI): DevTime scans
+a repo locally, explains concepts from evidence, surfaces uncertainty, catches a
+risky diff, and shows how a corroborated decision improves understanding.
 
 ---
 
 ## Try DevTime in 60 seconds
 
+```bash
+pipx install devtime-ei
+dtc demo init
+cd devtime-demo-saas
+dtc init
+dtc scan
+dtc concepts
+dtc explain "Billing Webhooks"
+```
+
+The PyPI distribution is `devtime-ei`. The Python package remains `devtime`, and the
+CLI command remains `dtc`. `dtc demo init` copies a small static example repo into
+`./devtime-demo-saas` so you can try DevTime without cloning this repository.
+
+### From source
+
 ```bash
 git clone https://github.com/Shakargy/devtime.git
 cd devtime
@@ -62,27 +78,36 @@ steps) is in **[DEMO_SCRIPT.md](DEMO_SCRIPT.md)**.
 
 ## Why this exists
 
-Git remembers code. It does not remember understanding. It does not tell you why a
-behavior exists, what evidence supports it, or what nobody has decided yet. As AI
-tools generate code faster than teams can review it, that missing understanding
-becomes the bottleneck.
+Git records what changed, but it does not preserve the reasoning behind those
+changes. When you return to a repository - or review one you did not write - you often
+have to reconstruct why a behavior exists, what evidence supports it, and what is
+still uncertain.
 
-DevTime builds evidence-backed repository memory: a local layer that says what a
-repository can prove, and - just as importantly - what it cannot prove yet.
+DevTime builds evidence-backed repository memory: a local layer that helps a
+codebase explain itself from code, tests, configs, routes, and recorded decisions.
+It shows what the repository can support with evidence - and, just as importantly,
+what it cannot support yet.
 
 ## Who it is for
 
-DevTime is for developers reviewing unfamiliar code, teams using AI coding tools, and
-maintainers who want repository understanding to be backed by evidence instead of
-generated summaries.
+DevTime is for people who need to understand a repository from evidence rather than
+memory.
+
+It is especially useful if you:
+
+- are onboarding to an unfamiliar codebase and need to understand how a feature is implemented;
+- are reviewing a pull request and want to see what evidence supports a behavior;
+- are returning to a project after weeks or months and cannot remember why something exists;
+- maintain a long-lived project where design decisions are easily lost;
+- want repository understanding to be backed by code and recorded decisions instead of generated summaries.
 
-It is useful when you want to ask:
+Questions DevTime helps answer include:
 
-- where is authentication actually implemented?
-- what files prove that billing webhooks exist?
-- what is still uncertain?
-- did this diff touch a risky concept?
-- is there a decision explaining this behavior?
+- Where is authentication actually implemented?
+- What files prove that Billing Webhooks exist?
+- What is still uncertain?
+- Did this diff touch a risky concept?
+- Is there a decision explaining this behavior?
 
 ## What DevTime does
 
@@ -142,14 +167,75 @@ Anything outside these six is out of scope for V0. See [LIMITATIONS.md](LIMITATI
 | `dtc decision add` | Add a local decision record that can reduce uncertainty. |
 
 (Also available: `dtc evidence`, `dtc debt`, `dtc status`, `dtc doctor --privacy`,
-`dtc export`, `dtc reset`.)
+`dtc export`, `dtc reset`, `dtc mcp start`.)
 
 Requires **Python >= 3.11** and git. See **[QUICKSTART.md](QUICKSTART.md)** for a
 step-by-step first run and troubleshooting.
 
+## Use with coding agents (MCP)
+
+Your coding agent starts every session amnesiac about your repository and then
+guesses, confidently. DevTime gives it memory it can trust: a local, read-only MCP
+server that answers only with claims the repository can prove, plus explicit
+uncertainty for what it cannot.
+
+Install with MCP support and scan your repo:
+
+```bash
+pipx install "devtime-ei[mcp]"
+cd your-repo
+dtc init
+dtc scan
+```
+
+Add DevTime to Claude Code:
+
+```bash
+claude mcp add devtime -- dtc mcp start
+```
+
+Or in any MCP client that reads `.mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "devtime": {
+      "command": "dtc",
+      "args": ["mcp", "start"]
+    }
+  }
+}
+```
+
+The agent gets three read-only tools: `list_concepts`, `explain_concept`, and
+`get_context_pack` (governed context with do-not-change-without-review paths, tests
+to run, and agent guidance). Local stdio only - no network listener, no write tools,
+no source code returned, only evidence file paths.
+
+DevTime is listed in the official MCP Registry as `io.github.shakargy/devtime`.
+
+<!-- mcp-name: io.github.shakargy/devtime -->
+
 ## Installation
 
-Recommended source install for now:
+Recommended: install from PyPI with [pipx](https://pipx.pypa.io/) so the `dtc`
+command is available on your PATH in an isolated environment:
+
+```bash
+pipx install devtime-ei
+```
+
+Or with pip:
+
+```bash
+pip install devtime-ei
+```
+
+The PyPI distribution is `devtime-ei`. The Python package remains `devtime`, and the
+CLI command remains `dtc`. After installing, run `dtc demo init` to create a local
+example repo to try it on.
+
+### From source
 
 ```bash
 git clone https://github.com/Shakargy/devtime.git
@@ -169,12 +255,6 @@ python -m venv .venv
 pip install -e ".[dev]"
 ```
 
-Planned PyPI install (after the package is published and verified):
-
-```bash
-pipx install devtime
-```
-
 ## Example output
 
 ```
@@ -238,7 +318,7 @@ intentionally not built yet - in **[LIMITATIONS.md](LIMITATIONS.md)**.
 ## Roadmap
 
 This is an early, local-first V0 focused on being trustworthy before being large.
-Not yet built (intentionally): git-history signals, wired MCP transport, an AI
+Not yet built (intentionally): git-history signals, write-enabled MCP tools, an AI
 provider, a UI, and any cloud/team/enterprise features. See **[ROADMAP.md](ROADMAP.md)**.
 
 ## Contributing

{devtime_ei-0.1.0 → devtime_ei-0.1.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "devtime-ei"
-version = "0.1.0"
+version = "0.1.2"
 description = "Local-first Engineering Intelligence for software repositories"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -37,15 +37,20 @@ dependencies = [
 ]
 
 [project.optional-dependencies]
+# Read-only MCP stdio server for coding agents (dtc mcp start).
+mcp = [
+    "mcp>=1.2",
+]
 dev = [
     "pytest>=8.0",
+    "mcp>=1.2",
 ]
 
 [project.urls]
 Homepage = "https://github.com/Shakargy/devtime"
 Repository = "https://github.com/Shakargy/devtime"
 Issues = "https://github.com/Shakargy/devtime/issues"
-"Release Notes" = "https://github.com/Shakargy/devtime/releases/tag/v0.1.0"
+"Release Notes" = "https://github.com/Shakargy/devtime/releases/tag/v0.1.2"
 Demo = "https://youtu.be/1Hiu3Y9J_SI"
 
 [project.scripts]
@@ -59,8 +64,15 @@ build-backend = "setuptools.build_meta"
 where = ["src"]
 
 # Non-Python runtime files that ship inside the package (read at runtime).
+# The demo-saas resource is copied out by `dtc demo init`; the leading-dot
+# .devtimeignore is listed explicitly because glob `*` does not match dotfiles.
 [tool.setuptools.package-data]
-devtime = ["db/*.sql", "assets/*"]
+devtime = [
+    "db/*.sql",
+    "assets/*",
+    "resources/demo-saas/**/*",
+    "resources/demo-saas/.devtimeignore",
+]
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]

{devtime_ei-0.1.0 → devtime_ei-0.1.2}/src/devtime/__init__.py

@@ -1,6 +1,6 @@
 """DevTime - local-first Engineering Intelligence for repository memory."""
 
-__version__ = "0.1.0"
+__version__ = "0.1.2"
 
 # Version metadata (Builder Edition, Chapter 20).
 EVIDENCE_MODEL = "2026.06.1"

{devtime_ei-0.1.0 → devtime_ei-0.1.2}/src/devtime/cli.py

@@ -24,9 +24,13 @@ console = Console()
 claim_app = typer.Typer(help="Inspect and govern claims.")
 decision_app = typer.Typer(help="Record human decisions.")
 mcp_app = typer.Typer(help="Local read-only MCP server.")
+demo_app = typer.Typer(
+    help="Create a local copy of the bundled demo repository.", no_args_is_help=True
+)
 app.add_typer(claim_app, name="claim")
 app.add_typer(decision_app, name="decision")
 app.add_typer(mcp_app, name="mcp")
+app.add_typer(demo_app, name="demo")
 
 
 # --------------------------------------------------------------------------- #
@@ -43,6 +47,37 @@ def init() -> None:
     console.print("AI disabled. Cloud disabled. Telemetry off. MCP read-only.")
 
 
+@demo_app.command("init")
+def demo_init(
+    force: bool = typer.Option(
+        False, "--force", help="Replace devtime-demo-saas if it already exists."
+    ),
+) -> None:
+    """Copy the bundled demo repository into ./devtime-demo-saas (static files only)."""
+    from devtime.demo import DEMO_DIR_NAME, DemoExistsError, create_demo
+
+    try:
+        create_demo(Path.cwd(), force=force)
+    except DemoExistsError as exc:
+        console.print(
+            f"[yellow]{DEMO_DIR_NAME}/ already exists[/yellow] at {exc.path}."
+        )
+        console.print(
+            "Use [bold]dtc demo init --force[/bold] to replace it, "
+            "or remove the directory first."
+        )
+        raise typer.Exit(code=1)
+
+    console.print(f"[green]Demo repository created[/green] at ./{DEMO_DIR_NAME}")
+    console.print("")
+    console.print("Next:")
+    console.print(f"  cd {DEMO_DIR_NAME}")
+    console.print("  dtc init")
+    console.print("  dtc scan")
+    console.print("  dtc concepts")
+    console.print('  dtc explain "Billing Webhooks"')
+
+
 @app.command()
 def status() -> None:
     """Show local storage, AI, cloud, telemetry, MCP, and scan status."""
@@ -306,20 +341,33 @@ def decision_add(
 
 @mcp_app.command("start")
 def mcp_start() -> None:
-    """Preview planned read-only MCP tools. Does NOT start a server in V0."""
-    from devtime.mcp.server import describe_server
+    """Start the local read-only MCP server over stdio (for coding agents)."""
+    # stdout belongs to the JSON-RPC stream: all diagnostics go to stderr.
+    err = Console(stderr=True)
+
+    if not paths.is_initialized():
+        err.print("[red]DevTime is not initialized here.[/red]")
+        err.print("Run [bold]dtc init[/bold] and [bold]dtc scan[/bold] in the repository first.")
+        raise typer.Exit(code=2)
+
+    from devtime.mcp.transport import McpDependencyMissing, run_stdio
 
-    console.print(describe_server())
-    # Honest exit: nothing was started, so a command named "start" returns nonzero.
-    raise typer.Exit(code=1)
+    err.print("DevTime MCP server: stdio, read-only, local only. Ctrl+C to stop.")
+    try:
+        run_stdio()
+    except McpDependencyMissing as exc:
+        # markup=False: the hint contains [mcp], which rich would eat as a tag.
+        err.print(str(exc), markup=False, style="red")
+        raise typer.Exit(code=1)
 
 
 @mcp_app.command("preview")
 def mcp_preview() -> None:
-    """Preview planned read-only MCP tools (transport not implemented in V0)."""
+    """Show implemented and planned read-only MCP tools."""
     from devtime.mcp.server import describe_server
 
-    console.print(describe_server())
+    # markup=False: the text contains [mcp], which rich would eat as a tag.
+    console.print(describe_server(), markup=False)
 
 
 @mcp_app.command("status")

devtime_ei-0.1.2/src/devtime/demo.py

@@ -0,0 +1,75 @@
+"""Bundled demo repository support for `dtc demo init`.
+
+This lets people who installed DevTime from PyPI (`pipx install devtime-ei`) try it
+without cloning the source repository. It copies a small, static example repo that
+ships inside the installed package into the current working directory.
+
+It only copies static files. It never executes code, never installs anything, never
+runs tests or migrations, and never touches the network. Nothing leaves the machine.
+"""
+
+from __future__ import annotations
+
+import shutil
+from importlib import resources
+from pathlib import Path
+
+# Directory name created in the current working directory.
+DEMO_DIR_NAME = "devtime-demo-saas"
+
+# The packaged demo lives at src/devtime/resources/demo-saas/ and ships in the wheel
+# via [tool.setuptools.package-data].
+_RESOURCE_SUBPATH = ("resources", "demo-saas")
+
+# Artifacts that must never end up in a copied demo, stripped defensively after copy.
+_FORBIDDEN_DIRS = {".devtime", ".git", "node_modules", "__pycache__", ".cache"}
+_FORBIDDEN_FILE_SUFFIXES = (".sqlite", ".sqlite3", ".db")
+
+
+class DemoExistsError(Exception):
+    """Raised when the demo directory already exists and force was not requested."""
+
+    def __init__(self, path: Path) -> None:
+        self.path = path
+        super().__init__(str(path))
+
+
+def packaged_demo_source() -> Path:
+    """Return a filesystem path to the demo directory bundled in the package."""
+    root = resources.files("devtime")
+    source = root.joinpath(*_RESOURCE_SUBPATH)
+    # In a normal wheel/editable install this is already a real path on disk.
+    return Path(str(source))
+
+
+def _strip_forbidden(dest: Path) -> None:
+    """Remove any artifacts that must never be part of a shared demo."""
+    for path in sorted(dest.rglob("*"), reverse=True):
+        if path.is_dir() and path.name in _FORBIDDEN_DIRS:
+            shutil.rmtree(path, ignore_errors=True)
+        elif path.is_file() and path.suffix.lower() in _FORBIDDEN_FILE_SUFFIXES:
+            path.unlink(missing_ok=True)
+
+
+def create_demo(dest_parent: Path, *, force: bool = False) -> Path:
+    """Copy the bundled demo into ``dest_parent/devtime-demo-saas``.
+
+    Writes only inside ``dest_parent``. Returns the created directory path.
+    Raises :class:`DemoExistsError` if the destination exists and ``force`` is False.
+    """
+    dest = dest_parent / DEMO_DIR_NAME
+    if dest.exists():
+        if not force:
+            raise DemoExistsError(dest)
+        shutil.rmtree(dest)
+
+    source = packaged_demo_source()
+    if not source.is_dir():
+        raise FileNotFoundError(f"Bundled demo not found at {source}")
+
+    # as_file guarantees a real filesystem path even if the package were zipped.
+    with resources.as_file(resources.files("devtime").joinpath(*_RESOURCE_SUBPATH)) as src_path:
+        shutil.copytree(src_path, dest)
+
+    _strip_forbidden(dest)
+    return dest

devtime_ei-0.1.2/src/devtime/mcp/server.py

@@ -0,0 +1,42 @@
+"""MCP server description (Builder Edition, Chapter 16).
+
+v0.1.2: the stdio transport is implemented for the read-only tool subset in
+devtime.mcp.transport. The remaining planned tools stay listed as planned so
+the preview output never overclaims.
+"""
+
+from __future__ import annotations
+
+import json
+
+from devtime.mcp import schemas
+from devtime.mcp.transport import IMPLEMENTED_TOOLS
+
+
+def describe_server() -> str:
+    """Honest preview: implemented tools are separated from planned ones."""
+    planned_read = [t for t in schemas.TOOLS["read"] if t not in IMPLEMENTED_TOOLS]
+    planned_context = [t for t in schemas.TOOLS["context"] if t not in IMPLEMENTED_TOOLS]
+    lines = [
+        "MCP transport: stdio, read-only, local only.",
+        'Requires the optional dependency: pip install "devtime-ei[mcp]"',
+        "Start with: dtc mcp start (stdout is the protocol stream).",
+        "",
+        "Implemented tools:",
+    ]
+    lines += [f"  - {t}" for t in IMPLEMENTED_TOOLS]
+    lines += ["Planned read tools (not implemented yet):"]
+    lines += [f"  - {t}" for t in planned_read]
+    lines += ["Planned context tools (not implemented yet):"]
+    lines += [f"  - {t}" for t in planned_context]
+    lines += ["Planned review tools (not implemented yet):"]
+    lines += [f"  - {t}" for t in schemas.TOOLS["review"]]
+    lines += [
+        "",
+        "Write tools are not exposed. No network listener. No source code is returned.",
+    ]
+    return "\n".join(lines)
+
+
+def describe_permissions() -> str:
+    return json.dumps(schemas.DEFAULT_PERMISSIONS, indent=2)