Persistent R, Python, and SQL sessions for MCP clients
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-console","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Console An interactive workbench for agents working with data in R, Python, and SQL. Load data once, explore questions, refine plots, read help, and debug code with objects and models still in memory. Use one language or combine them in the same process, without intermediate files. Code runs in an [OS-level sandbox](docs/SANDBOX.md) by default. Console prepares environments and packages automatically; no Console configuration file is required. It works with MCP-compatible clients such as Codex and Claude Code and does not depend on a particular model provider. **Development preview:** interfaces may change. macOS, Linux, and Windows x64 are supported. ## Quickstart Install [uv](https://docs.astral.sh/uv/getting-started/installation/), then install Console: ```sh uv tool install mcp-console ``` [Get started](docs/getting-started.qmd) covers platform prerequisites, optional R installation, and client setup. [Build from source](docs/BUILD_FROM_SOURCE.md) covers the development version. Register Console with your client: ```sh mcp-console configure-client codex # Or: mcp-console configure-client claude ``` This registers Console globally, configures the client to launch `uvx mcp-console serve`, and loads Console tools up front. Add `--directory .` to register it for the current directory instead. Use `--dry-run` to preview the settings or `--no-auto-load` to keep the client's default tool discovery. You can also start with `uvx mcp-console configure-client codex claude` to configure both clients without first installing Console. Use `--pin-version VERSION` to select the Console version resolved by uvx, or `--no-uvx` to configure an absolute executable path. `--pin-version current` pins the version running setup. See [client setup](docs/getting-started.qmd#connect-your-client) for project/global scope and other clients. Run the client and Console on the same host, with the client's shell and filesystem tools using the same workspace. Ask your agent: >…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.