klavis
[DEPRECATED] Legacy Klavis AI MCP integrations. See klavis.ai for RL environments and training data.
Runssource: GitHubhomepagePythonApache-2.0archived upstreamcommit 45c9f7da83d1
Python, Apache-2.0 licensed. The project labels itself: agents, ai, ai agents, api, deprecated, developer tools, discord and function calling.
klavis runs. An Argusic agent installed it in 1 minute and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The strata-mcp package installs, CLI commands work (strata --help, strata list, strata add), all 60 runnable tests pass, and the server starts on port 18080 with SSE and StreamableHTTP transports, connecting to configured MCP servers.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- AttributeError: 'Server' object has no attribute 'list_tools' in server.py (mcp v2.3 removed decorator pattern)5 minutes
- test_server_integration.py hung across tests and KeyError not caught2 minutes
- ImportError: cannot import name 'streamablehttp_client' from mcp.client.streamable_http1 minute
- AssertionError in test_mcp_client_manager_sync.py::test_sync_with_http_server1 minute
- AttributeError: 'Tool' object has no attribute 'inputSchema' (mcp v2 uses input_schema)0.5 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pytest -v -m 'not integration' --ignore=test_mcp_client.py --ignore=test_mcp_client_manager.py returned 60 passed, 1 deselected; strata run --port 18080 started uvicorn on 0.0.0.0:18080 with SSE 200 and StreamableHTTP transports
- Model tokens used
- 142,946
- Exact commit tested
- 45c9f7da83d1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Error 5**: Assertion failures and hang in `test_server_integration.py` — the `create_test_mcp_ser…
**Remaining (not fixed)**: `test_mcp_client.py` requires `GITHUB_PAT` env var; `test_mcp_client_man…
**Install**: `pip install -e ".[dev]"` — succeeded.
**Tests**: `pytest -v -m "not integration" --ignore=test_mcp_client.py --ignore=test_mcp_client_man…
**Server launch**: `strata run --port 18080` — prints banner, starts uvicorn on `0.0.0.0:18080`, SS…
exec
/bin/sh -lc "ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"install_mi…
exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:: not found
2026-11-07T05:30:55.362672Z ERROR codex_core::session: failed to record rollout items: thread 01a1b…
tokens used
142,946Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 1 minute, faster than the median of the 40 comparable projects Argusic has measured.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 41 agents projects Argusic has installed and timed, klavis was the 3rd fastest to reach a running state, and 29 of 41 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.33 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.15 |
Topics (from GitHub)
agentsaiai-agentsapideprecateddeveloper-toolsdiscordfunction-callingintegrationllmmcpmcp-clientmcp-serveroauth2open-source
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/klavis)Questions
- Does klavis run?
- Yes. klavis runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test klavis?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 45c9f7da83d1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test klavis?
- The run that produced this verdict cost $0.33: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does klavis take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does klavis need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing klavis?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does klavis compare with the alternatives?
- Of the 41 agents projects Argusic has installed and timed, klavis was the 3rd fastest to reach a running state, and 29 of 41 reached one at all.
- Where is the evidence for klavis?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.