sift-cli 1.0.1__tar.gz → 1.0.2__tar.gz

{sift_cli-1.0.1 → sift_cli-1.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sift-cli
-Version: 1.0.1
+Version: 1.0.2
 Summary: Runs your command, then gives the model only the lines that matter.
 Project-URL: Homepage, https://github.com/slymnysr/sift
 Author: slmnys
@@ -182,6 +182,7 @@ sift outline PATH         what a file declares, without its bodies
 sift digest PATH...       what is in files somebody else produced
 sift peek HANDLE|PATH [FIRST] [LAST]
 sift hook                 answer one shell-command event on stdin
+sift mcp                  speak the protocol on stdin, for a client
 sift tools                which dense tools this machine has
 sift tool NAME [ARGS...]  run one of them, distilled
 sift memory [TERM]        what has been run here before, and how it went
@@ -260,7 +261,10 @@ Without a key the server starts and every tool that would need a model declines
 with an explanation, so the agent falls back to its own shell rather than being
 handed a worse answer it cannot tell apart from a good one.
 
-Any client that speaks stdio will do — the command is `sift-mcp`. It offers
+Any client that speaks stdio will do. The command is `sift-mcp`, and `sift mcp`
+starts the same server — one word for a client that would rather run the package
+by its own name (`uvx --from "sift-cli[mcp]" sift-cli mcp`, which is what the MCP
+registry entry says). It offers
 `run`, `follow`, `outline`, `digest`, `digest_many`, `tool` and `peek`. `list`
 and `stats` are deliberately not offered: they would hand a model every command lately run on this machine,
 including the ones it never asked about, and the person at a terminal already

{sift_cli-1.0.1 → sift_cli-1.0.2}/README.md

@@ -162,6 +162,7 @@ sift outline PATH         what a file declares, without its bodies
 sift digest PATH...       what is in files somebody else produced
 sift peek HANDLE|PATH [FIRST] [LAST]
 sift hook                 answer one shell-command event on stdin
+sift mcp                  speak the protocol on stdin, for a client
 sift tools                which dense tools this machine has
 sift tool NAME [ARGS...]  run one of them, distilled
 sift memory [TERM]        what has been run here before, and how it went
@@ -240,7 +241,10 @@ Without a key the server starts and every tool that would need a model declines
 with an explanation, so the agent falls back to its own shell rather than being
 handed a worse answer it cannot tell apart from a good one.
 
-Any client that speaks stdio will do — the command is `sift-mcp`. It offers
+Any client that speaks stdio will do. The command is `sift-mcp`, and `sift mcp`
+starts the same server — one word for a client that would rather run the package
+by its own name (`uvx --from "sift-cli[mcp]" sift-cli mcp`, which is what the MCP
+registry entry says). It offers
 `run`, `follow`, `outline`, `digest`, `digest_many`, `tool` and `peek`. `list`
 and `stats` are deliberately not offered: they would hand a model every command lately run on this machine,
 including the ones it never asked about, and the person at a terminal already

{sift_cli-1.0.1 → sift_cli-1.0.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "sift-cli"
-version = "1.0.1"
+version = "1.0.2"
 description = "Runs your command, then gives the model only the lines that matter."
 readme = "README.md"
 requires-python = ">=3.12"
@@ -30,6 +30,9 @@ mcp = ["mcp>=2"]
 [project.scripts]
 sift = "sift.cli:main"
 sift-mcp = "sift.server:main"
+# The package name, spelled as a command, because that is the only name a
+# registry entry can carry: `uvx <package>` is how a client starts one.
+sift-cli = "sift.cli:main"
 
 [project.urls]
 Homepage = "https://github.com/slymnysr/sift"

{sift_cli-1.0.1 → sift_cli-1.0.2}/src/sift/__init__.py

@@ -15,4 +15,4 @@ reply that makes no sense -- each of these falls back to rules that need none of
 them. A tool that drops output to save context has cost more than it saved.
 """
 
-__version__ = "1.0.1"
+__version__ = "1.0.2"

{sift_cli-1.0.1 → sift_cli-1.0.2}/src/sift/cli.py

@@ -73,6 +73,7 @@ USAGE = """sift -- run a command, keep every byte, show the lines that matter
   sift hook                           answer one shell-command event on stdin
   sift hook --install [--yes]         route the client's own shell here too
   sift hook --uninstall               and take it back out
+  sift mcp                            speak the protocol on stdin, for a client
   sift tools                          which dense tools this machine has
   sift tool NAME [ARGS...]            run one of them, distilled
   sift memory [TERM] [--here]
@@ -161,6 +162,8 @@ def main(argv: list[str] | None = None) -> int:
         return _list(rest)
     if word == "hook":
         return _hook(rest)
+    if word == "mcp":
+        return _mcp(rest)
     if word == "tools":
         return _tools()
     if word == "tool":
@@ -573,6 +576,29 @@ def _hook(args: list[str]) -> int:
     return 0
 
 
+def _mcp(args: list[str]) -> int:
+    """Speak the protocol on stdin -- the same server `sift-mcp` starts.
+
+    Two names for one server looks like waste until you try to write down how a
+    stranger's client should start it. What a registry entry can name is the
+    package, and the package is `sift-cli`; what `uvx` runs is a command of that
+    same name. So `uvx --from "sift-cli[mcp]" sift-cli mcp` is a line anyone can
+    build from the entry alone, and it needs this word to exist.
+
+    The import is here rather than at the top because the whole point of the
+    extra is that the command line works without it. Somebody who never
+    installed `mcp` gets the sentence `sift.server` raises, not a traceback.
+    """
+    if args:
+        print(f"sift: mcp takes no arguments\n\n{USAGE}", file=sys.stderr)
+        return 2
+
+    from sift.server import main as serve
+
+    serve()
+    return 0
+
+
 def _tools() -> int:
     """What each of them replaces, and whether this machine has it.
 

{sift_cli-1.0.1 → sift_cli-1.0.2}/test/mutations.py

@@ -1255,6 +1255,13 @@ MUTATIONS = [
         "    if not wanted():\n        return PASS",
         "    if False:\n        return PASS",
     ),
+    # -- T1/T2: the word a registry entry can spell ----------------------------
+    Mutation(
+        "cli.py",
+        "the server can be started by the package's own name",
+        '    if word == "mcp":\n        return _mcp(rest)\n',
+        "",
+    ),
 ]
 
 

{sift_cli-1.0.1 → sift_cli-1.0.2}/test/test_package.py

@@ -23,6 +23,24 @@ def test_the_published_version_is_the_one_the_package_reports():
     assert veri["project"]["version"] == sift.__version__
 
 
+def test_a_command_is_named_after_the_package_itself():
+    """`uvx sift-cli` has to start something.
+
+    What an MCP registry entry can name is the package, and what `uvx` runs is a
+    command of that same name -- so a client building a command from the entry
+    alone types `sift-cli`, and until this existed it got "an executable named
+    `sift-cli` is not provided by package `sift-cli`". The names differ because
+    `sift` was taken on PyPI, which is nobody's fault and still the user's
+    problem.
+    """
+    veri = tomllib.loads((KOK / "pyproject.toml").read_text(encoding="utf-8"))
+    scripts = veri["project"]["scripts"]
+    ad = veri["project"]["name"]
+
+    assert ad in scripts, f"{ad} adinda bir komut yok; uvx {ad} calismaz"
+    assert scripts[ad] == scripts["sift"], "paketin adi komut satirini baslatmali"
+
+
 def test_notes_and_tests_live_in_their_own_folders():
     """The layout the project promised: notes in notlar/, tests in test/.
 

{sift_cli-1.0.1 → sift_cli-1.0.2}/test/test_server.py

@@ -268,6 +268,49 @@ def test_and_the_test_above_would_have_noticed():
     assert "`sift`) is already installed" in finished.stderr
 
 
+# -- the word a registry entry can spell -------------------------------------
+
+
+def test_the_subcommand_starts_the_same_server(monkeypatch):
+    """`sift mcp` and `sift-mcp` are one server under two names.
+
+    The second name exists because an MCP registry entry can only name the
+    package, and a client turns that name into `uvx --from "sift-cli[mcp]"
+    sift-cli mcp`. A word that a stranger's client types has to reach the same
+    place the documented command does, or the entry is worse than no entry.
+    """
+    from sift import cli
+
+    started = []
+    monkeypatch.setattr(s, "main", lambda: started.append(True))
+
+    assert cli.main(["mcp"]) == 0
+    assert started == [True], "alt komut sunucuyu baslatmadi"
+
+
+def test_the_subcommand_takes_nothing_and_says_so(capsys):
+    """Silence would be worse: a flag that was ignored looks like a flag that worked."""
+    from sift import cli
+
+    assert cli.main(["mcp", "--port", "8080"]) == 2
+    assert "mcp takes no arguments" in capsys.readouterr().err
+
+
+def test_the_subcommand_says_the_same_sentence_when_the_extra_is_missing():
+    """The registry command minus the extra is an ordinary thing to type.
+
+    `uvx sift-cli mcp` -- without `--from "sift-cli[mcp]"` -- installs the
+    command line and nothing else, and this is the path a client takes when it
+    drops the runtime arguments. What comes back has to be the sentence, not a
+    stack: the import lives inside the subcommand for exactly this reason.
+    """
+    finished = _without_mcp("import sift.cli\nsift.cli.main(['mcp'])\n")
+
+    assert finished.returncode != 0
+    assert 'uv tool install "sift-cli[mcp]"' in finished.stderr
+    assert "Traceback" not in finished.stderr
+
+
 # -- over the real transport -------------------------------------------------
 
 SCRIPT = shutil.which("sift-mcp")