willchen96 gives Mike a front door for outside tools
Users can now plug remote third-party services straight into the assistant instead of waiting for each one to be hard-coded.
willchen96 added support for Model Context Protocol connectors, a standard way for AI apps to reach external tools and data. Point Mike at a remote service and the assistant can discover and call whatever that service offers, right inside chat. What landed:
- Connectors screen to add, enable, refresh, and delete external services, with encrypted tokens and custom headers for private ones.
- Tool discovery with per-tool switches, so you decide exactly which of a service's capabilities the assistant may use.
- OAuth sign-in for services that require an account handshake before they hand over access.
- Guardrails on where connectors can point: plain-HTTP, localhost, and private-network addresses are rejected, tested against blocked targets.
- An audit log recording every tool the assistant invokes.
So what Legal-ops and product leads get a governed way to wire in outside systems without a code change for each one, with the access controls and audit trail counsel will ask about.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?