adaptorch-mcp

# adaptorch-mcp Installable Python wrapper for the AdaptOrch MCP server. The package runs a hardened facade over `adaptorch.mcp_server`, so routing and synthesis stay aligned with AdaptOrch core without copying those algorithms into the wrapper. The default `remote` exposure profile keeps local topology and trace oracles out of the public MCP surface. ## Install ```bash pip install adaptorch-mcp ``` If AdaptOrch is not published to your package index yet: ```bash pip install "adaptorch[api] @ git+https://github.com/dmae97/adaptorch.git" pip install adaptorch-mcp ``` One-shot with `uvx`: ```bash uvx adaptorch-mcp --help uvx --with "adaptorch[api] @ git+https://github.com/dmae97/adaptorch.git" adaptorch-mcp --help ``` For contributors inside this monorepo: ```bash uv sync --all-packages --extra dev uv run adaptorch-mcp --help ``` ## Run stdio MCP Use stdio for Claude Code, Claude Desktop, and other local MCP hosts. The upstream token is the AdaptOrch API key issued at `https://adaptorch.com/app/api-keys` (`ado_live_*`, or `ado_test_*` for test mode; legacy `ak_*` keys remain accepted). ```bash export ADAPTORCH_CONTROL_PLANE_TOKEN="<ado_live_your-key>" adaptorch-mcp --transport stdio --base-url https://adaptorch.com ``` Runs submitted through this wrapper are stamped `metadata.connector_source="mcp"` by the engine, so they appear in the dashboard MCP status card and `https://adaptorch.com/app/runs` for the key's tenant. ## Run HTTP MCP Use HTTP for local gateways, reverse proxies, or remote MCP clients. Keep the client-facing MCP token separate from the upstream AdaptOrch token. ```bash export ADAPTORCH_CONTROL_PLANE_TOKEN="<upstream-adaptorch-token>" export ADAPTORCH_MCP_HTTP_AUTH_TOKEN="<client-facing-mcp-token>" # must differ from upstream adaptorch-mcp \ --transport http \ --base-url https://adaptorch.com \ --http-host 127.0.0.1 \ --http-port 8765 \ --http-auth-token "$ADAPTORCH_MCP_HTTP_AUTH_TOKEN" ``` Health and metrics require the …