Public clients and versions

Point an MCP client that supports HTTP servers at https://adaptorch.com/mcp. It takes JSON-RPC over HTTPS POST; SSE GET is not supported. Create an API key on the connect page and keep it in your client's secret settings, not in a prompt or a URL.

Client-specific setup for Claude Code, Codex CLI and Cursor is in the connection documentation. Use this path first when your client supports it.

For clients that only run local stdio MCP servers. adaptorch-mcp 0.6.x is a remote client with no engine dependency: it forwards MCP calls to https://adaptorch.com/v1/mcp. It needs Python 3.11 or 3.12.

uvx --from adaptorch-mcp==0.6.1 adaptorch-mcp-client --transport stdio

Versions 0.3.0 to 0.5.2 depended on a private engine package and do not install. Use 0.6.1.

The command is adaptorchctl. It needs Python 3.11 or later and installs its compatible SDK as a dependency.

python -m pip install --upgrade adaptorch-cli==0.1.6

It talks to https://adaptorch.com unless ADAPTORCH_API_URL says otherwise, and reads the key from ADAPTORCH_API_KEY. Start with adaptorchctl whoami and adaptorchctl capabilities.

For calling AdaptOrch from your own Python code. It needs Python 3.11 or later.

python -m pip install adaptorch-client==0.1.6

Since 0.1.5 the CLI and the SDK can download the saved report of a finished run you own (adaptorchctl run report, get_run_report).

On November 5, 2026 the latest releases on PyPI were adaptorch-mcp 0.6.1, adaptorch-cli 0.1.6 and adaptorch-client 0.1.6, and adaptorch-mcp-client --help, adaptorchctl --help and the SDK import ran from a clean install. The client source is in the public MCP client repository.

A working install is not evidence that a connection is authenticated. See the claim boundary for what AdaptOrch does and does not claim.