R, Python 및 SQL의 데이터로 작업하는 에이전트를 위한 대화형 워크 벤치.

한 번 로드 데이터, 질문을 탐구, refine 플로우, 도움말을 읽고, 그리고 개체와 디버그 코드 메모리에서 여전히. 하나의 언어를 사용하거나 같은 과정에서 결합, 중간 파일없이.

Code는 기본적으로 OS-level sandbox에서 실행됩니다. 콘솔은 환경 및 패키지를 자동으로 준비합니다. 콘솔 구성 파일이 필요하지 않습니다. Codex 및 Claude Code와 같은 MCP 호환 클라이언트와 함께 작동하며 특정 모델 공급자에 의존하지 않습니다.

개발 미리보기: 인터페이스를 변경할 수 있습니다. macOS, Linux 및 Windows x64는 지원됩니다.

퀵스타트

uv를 설치하고 콘솔을 설치하십시오:

플랫폼 prerequisites, 선택적인 R 임명 및 클라이언트 설치를 시작하십시오. 소스에서 빌드는 개발 버전을 다룹니다.

클라이언트와 콘솔 등록:

콘솔을 전 세계적으로 등록하고, 클라이언트가 uvx mcp-console serve]을 실행하고, 콘솔을 로드합니다. --directory . 을 추가하여 현재 디렉토리에 등록하십시오. --dry-run] 을 사용하여 설정 또는 --no-auto-load] 을 미리 설정하여 클라이언트의 기본 도구 발견을 유지합니다.

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 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, then install Console:

uv tool install mcp-console

Get started covers platform prerequisites, optional R installation, and client setup. Build from source covers the development version.

Register Console with your client:

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 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:

Use Console to generate a small dataset, fit a model, and plot the result. Keep the data and model for follow-up.

Where Console fits

• Unattended analysis: run long analyses with limits on filesystem writes and network access.
• Model evaluations: evaluate how an agent explores data, checks its work, and responds to results.
• Conversational analysis: discuss questions and results while the agent works in its own session.
• Large datasets: keep data and intermediate results in memory for follow-up questions.
• Debugging and package development: pause execution and inspect live objects where a failure occurs.

Limits and trust boundaries

The default sandbox permits host-file reads, restricts direct networking, and permits regular-file writes only in private temporary storage. Readable secrets are not protected. Project configuration is trusted input and may widen permissions.

Dependency preparation has its own permissions.