arcade-mcp
MCP Server Framework and Tool Development library for building custom capabilities into agents.
Runssource: GitHubhomepagePythonMITcommit af2501e56400
Python, MIT licensed. The project labels itself: ai, arcade, arcade ai, claude, claude code, claude mcp, mcp and mcp framework.
arcade-mcp runs. An Argusic agent installed it in 22 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Arcade MCP installs from source via make install, its full pytest suite passes (4140 passed, 1 skipped), the scaffolded MCP server starts over HTTP and stdio and answers real tools/call requests (greet returned 'Hello, world!' over HTTP and 'Hello, stdio-user!' over stdio;
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 100 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.
- arcade show --local finds no tools for the quick-start src-layout scaffold (DISCOVERY_PATTERNS only match top-level *.py and tools/ dirs)6 minutes
- arcade whoami exits 1 with 'Not logged in' when no Arcade login config exists (tests/install/test_install.py step 6)5 minutes
- uv binary not installed (make install/health checks require it)4 minutes
- Install time
- 22 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- uv run --extra all --extra dev pytest -W ignore -q libs/tests returned '4140 passed, 1 skipped' exit 0; tests/install/test_install.py 'Total: 7/7 tests passed' with mock login config; tests/integration/no_auth_cli_smoke.py 'All MCP protocol smoke checks PASSED' exit 0; curl POST localhost:8000/mcp/v1 tools/call ArcadeTestServer_Greet returned 'Hello, world!'; stdio piped client returned 'Hello, stdio-user!' and 'The last 4 characters of the secret are: ime!'; uv run arcade --version returned 'Arcade CLI (version 1.16.1)'; libs/tests/cli/test_dashboard.py '15 passed'
- Model tokens used
- 1,035,872
- Exact commit tested
- af2501e56400
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `uv` missing → installed via official installer (no root) → resolved.
- `arcade new`/server run emit an update notice ("Update available: 1.16.1 → 1.16.2") — cosmetic, n…
- `tests/install/test_install.py`: `whoami` step exits 1 with "Not logged in to Arcade CLI" when no…
- Noted (unfixed, out of scope): `arcade show --local` discovers no tools from the quick-start's sr…
**Verification**
- `make test`-equivalent run: `uv run --extra all --extra dev pytest libs/tests` → `4140 passed, 1 …
- Install script with mock login config: `Total: 7/7 tests passed` (exit 0).
- `uv run python tests/integration/no_auth_cli_smoke.py`: "All MCP protocol smoke checks PASSED." (…
- HTTP MCP `tools/call` on `ArcadeTestServer_Greet` returned `"Hello, world!"`; stdio returned `"He…
- `libs/tests/cli/test_dashboard.py`: `15 passed`.
**Final state**
- Everything now works: install via `make install`, full test suite `4140 passed, 1 skipped`, the g…Replay 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.
- Recovered from all 3 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 MIT, as reported by its host.
What did not, or is not known
- Took 22 minutes to install, slower than the median of the 233 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 234 ai projects Argusic has installed and timed, arcade-mcp was the 206th fastest to reach a running state, and 162 of 234 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.
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
Topics (from GitHub)
aiarcadearcade-aiclaudeclaude-codeclaude-mcpmcpmcp-frameworkmcp-gatewaymcp-runtimemcp-servermcp-serversmcp-toolsmcpservermodel-context-protocolmodel-context-protocol-sdkpython
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/arcade-mcp)Questions
- Does arcade-mcp run?
- Yes. arcade-mcp runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test arcade-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit af2501e56400. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test arcade-mcp?
- The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does arcade-mcp take to install?
- 22 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does arcade-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing arcade-mcp?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does arcade-mcp compare with the alternatives?
- Of the 234 ai projects Argusic has installed and timed, arcade-mcp was the 206th fastest to reach a running state, and 162 of 234 reached one at all.
- Where is the evidence for arcade-mcp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.