Point your assistant at this server
This is the whole product. Once an assistant is connected it can run Python — properly, in a sandbox — and you
talk to it in ordinary sentences. There is no interface to learn and no environment to install.
The endpoint
https://crucible.konsole.one/mcp
copy
It speaks MCP over streamable HTTP, and authorises with OAuth 2.1 — most clients will walk you through signing in
the first time. If yours wants a key instead, mint one on your account page .
Claude Code
claude mcp add --transport http crucible https://crucible.konsole.one/mcp
copy
Anything that takes a config file
{
"mcpServers" : {
"crucible" : {
"type" : "http" ,
"url" : "https://crucible.konsole.one/mcp" ,
"headers" : { "Authorization" : "Bearer crk_your_key" }
}
}
}
Leave the header out if your client does OAuth — it will get its own token.
Then just ask
Arithmetic you would not trust it to do in its head
“What’s the compound interest on 40,000 at 6.5% over 12 years, monthly?”
“Is 2ⁿ − 1 prime for every n under 200? Which ones?”
“Work out the payment schedule and give me it as a CSV.”
Data you hand it
“Here’s the export — which region grew fastest, and plot it.”
“Find the duplicate rows in this and tell me what they have in common.”
“Reconcile these two files and give me what’s only in one of them.”
Work that comes back
“Save that as a program called weekly-recon, taking a month.”
“Run weekly-recon for August.”
“It worked last week — run the revision from before Tuesday.”
Worth knowing
An assistant sees exactly what you see — its key carries your role
The last expression is the answer, so it needs no print
A run has no network . Send the data with the call
Nothing survives between runs — ask for a session if it should
A missing package is a runtime to rebuild, and the reply says which call does it
Ask it to meta.whoami if an answer looks thinner than expected
If it does not connect
401 with a WWW-Authenticate header — that is normal. Your client should follow it to the OAuth flow. If it cannot, use a key.
“This server has no accounts yet” — nobody has set it up. Open /setup .
Your key stopped working — it was revoked, it expired, or you have been marked as having left. Check your account page .
Everything returns nothing — you are probably signed in as someone whose role only sees themselves. Run meta.whoami.
Every run is refused — this deployment has no container engine reachable. /sandbox says what it found and what to do about it.
Is it up at all? — /health answers without any credential.