Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@boinc-central-mcp check my latest BOINC Central batch status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server (stdio) that lets agents see batch status and fetch batch output on BOINC Central without a browser. It works with BUDA (Docker) batches and other remote-submission apps, and with any BOINC project that runs the standard job-submission code.
The server only calls the API BOINC already has, so the server side needs no changes:
What | BOINC endpoint | Auth |
batches, jobs, abort, retire |
|
|
batch output tar |
| web cookie |
Tool | What it returns |
| Your batches, newest first. |
| State, fraction done, job counts ( |
| One row per job: id, name, status, canonical instance, CPU time. Failed jobs also carry exit codes and error flags. |
| A job's instances and their states. With |
| Writes |
| Destructive. Aborts the batch. You must pass |
| Destructive. The server deletes the batch's collected output at once. You must pass |
The read-only tools carry readOnlyHint, and the two destructive ones carry
destructiveHint.
The RPC API does not give per-job sent or received times, so these figures come from what the API does give:
batch_turnaround_s is the finish time minus the submit time. For a running batch,
it is the time elapsed so far.
median_turnaround_s is the batch field the web page labels "Median turnaround
time" (expire_time). BUDA leaves it unset, so for BUDA batches it is usually
null.
runtime_sample gives median run times of completed jobs.
median_job_turnaround_s is the median of received time minus sent time over the
canonical instances. It appears only when the server reports those times, which
needs the proposed BOINC change on the
remote-batch-output-auth
branch.
Related MCP server: mcp-slurm
Get your account key, the authenticator. Log in to BOINC Central and open Your account → Account keys (https://boinc.berkeley.edu/central/weak_auth.php). Copy the value shown under "Your account key is:". Do not copy the weak account key below it, because the RPC API does not accept the weak key.
Put the key in the key file and lock it down.
mkdir -p ~/.config/boinc-central
( umask 077; pbpaste > ~/.config/boinc-central/authenticator ) # or use an editor
chmod 600 ~/.config/boinc-central/authenticatorThe server refuses to read the file if group or others can read it.
BOINC_CENTRAL_AUTH_FILE=/path/to/file points the server at another file. Only a
path is accepted: the key itself is never taken from a tool argument or an
environment variable value. The server also removes the key from any error text
before an agent can see it.
Register the server with Claude Code.
claude mcp add boinc-central -s user -- \
uvx --from git+https://github.com/ispacex/boinc-central-mcp boinc-central-mcpTo run from a local checkout instead:
claude mcp add boinc-central -s user -- \
uv run --directory ~/work/math/boinc-central-mcp boinc-central-mcpBOINC_CENTRAL_URL (default https://boinc.berkeley.edu/central/) points the
server at another BOINC project.
Your account needs remote-submission access (a user_submit record), which every
account that can submit BUDA jobs has.
uv run pytestThe tests use recorded-format XML fixtures (tests/fixtures/) and an
httpx.MockTransport, so they need neither network access nor a key. They pass with
mcp 1.x (FastMCP) and 2.x (MCPServer, the renamed FastMCP).
There is no RPC for submitting BUDA batches. buda_submit.php is a web form that
authenticates by cookie. It submits in two steps:
Upload the batch .zip to your sandbox (sandbox.php, action=upload_file,
multipart).
Request buda_submit.php?action=submit&app=…&batch_file=…&max_runtime_days=…&exp_runtime_days=…&cmdline=….
This runs create_work with BUDA's sub_appname and templates.
The generic submit_batch RPC does not set those up. A submit_buda_batch tool could
drive the two web steps with the same auth cookie. A cleaner route is a
submit_buda_batch RPC upstream in BOINC.
MIT, see LICENSE.
This server cannot be deployed
Remote MCP for Android CLI agent build gate, structured receipts, audit logs, and reviewer-ready evi
Manage brainCloud apps, cloud code, hooks and servers; API lookups to help generate client code.
Dispatch and track Alchemist Cloud tickets, watch deploys, read logs, and query your project DB.
Inspect Depot builds, CI runs, job logs and Actions runners; retry or cancel CI runs.
