Connect a remote MCP server as an org integration
Admins can add remote MCP servers next to GitHub, Linear, Notion and Slack, choose which tools each project sees, and let people approve writes the same way they already do.
You have tools that live outside the integrations Chief already ships with, and until now there was no way to bring them in. Remote MCP servers are now a connection type you can add yourself.
Remote MCP servers in integrations
As an org admin, you connect a remote MCP server from the same place you connect GitHub, Linear, Notion and Slack. You can sign in through OAuth or paste a static token, depending on what the server supports.
Tool and project selection
After connecting, you pick which of the server's tools to expose and which projects can see them. Everyone who uses the server signs in with their own account, so access follows the person, not the org.
Approvals per server
Auto-approve applies to a whole server rather than tool by tool. Turn it on once and writes to that server run without a prompt; leave it off and you get a confirmation card to approve or reject before anything happens.
Results in the same reply
Before, an approved write would run off to the side and Chief would tell you about it later. An approved write now runs inside the turn, so the issue link or message permalink comes back in the same answer. Chief can also offer to send work to a specific server by name.
Open your org integrations settings to add a server and choose the tools your projects should see.