pi-dispatch now lets self-hosted coding-agent jobs use selected MCP servers
Version 4.2.0 lets an operator offer MCP servers to individual pi agent jobs while checking names, credential references and egress before the job starts.
Tools for a background agent
pi-dispatch 4.2.0 adds MCP servers to the jobs it runs for the pi coding agent. An operator lists available servers in an overlay, then a trigger names which of them a particular job may connect. The project says both streamable HTTP and stdio servers are supported. A GitHub or GitLab trigger can also offer its forge’s MCP server using the job’s existing token. Jobs with no named server keep their earlier behavior. The release matters for teams that run coding agents from issues or schedules and need access to a documentation server or another controlled tool without making it available to every job.
The limits are part of the release
The release notes say server credentials must be supplied through references, and a job is refused before model spend if it names an unavailable server, lacks a required variable or cannot reach an allowed endpoint. This is the project’s documented behavior, not a security audit by AITrending. Operators must update the job image and workers before assigning servers; the release also calls for a receiver update so trigger settings are not silently lost. A job cannot complete an interactive OAuth sign-in. The new feature is therefore a configurable route for existing self-hosted deployments, not a promise that any MCP server works automatically or safely with an arbitrary coding task.