Signals

2026-10-13 / Pi Coding Agent

Pi's CLI connects MCP servers and composes their tools in JavaScript

Edited by Michael Ruescher

0.99.0 (2026-09-29) brings built-in MCP and codemode to the CLI; current stable is 1.2.0. Scripts compose registered tools without a private MCP bridge. Enabled MCP servers with default exposure can activate codemode; SDK sessions do not load these built-ins automatically. Nested tool calls traverse hooks, while script classifier and image-model operations use session credentials outside the individual tool-call hooks.

What this changes for operators

  • CLI integrators: try a configured MCP server and one multi-tool script on 1.2.0 before maintaining an equivalent bridge. Compare accepted outcomes, setup and review time before removing it; no net time saving or current-version quality comparison was measured.
  • Read global and trusted-project mcp.json before launch. Stdio servers inherit Pi’s environment and run beside the harness, so contain the whole process or scrub its environment. --no-mcp disables built-in MCP; autoEnableCodemode: false only prevents its automatic codemode activation.
  • Keep authorization in hooks and govern script model credentials. Tool declarations and codemode-only presentation do not prove a callable-set restriction. Denial tests covering root calls, nested calls and model spend would settle a particular deployment’s boundary; watch for tagged repairs to issue 10426 before relying on only-mode enforcement.

Primary sources

Signal metadata

Source findings

Featured in

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-13-pi-coding-agent-native-mcp-and-tool-scripting

Research evidence and publication history are open in the repository.