Public integrations
On this page
AI agents: read the complete documentation index. Append
.mdto any docs URL for its Markdown version.
Chief's public integrations let you check progress and propose work from an assistant, or share project activity with a Discord server. Work still executes through your local relay and agents.
Choose a connection
| Integration | Use it for | Setup guide |
|---|---|---|
| Chief MCP server | Ask an assistant what is waiting, look up milestones and summaries, and propose work in selected projects. | MCP connector setup |
| Chief for Discord | Share ship logs, check status, collect milestone suggestions, and review proposals from a DM. | Discord |
The public integration directory lists the currently available surfaces. Each guide links to its public install page. Assistant client setup in the MCP guide follows the verified clients listed on that page.
Prepare a project
Create a project with the quickstart, set a clear goal, and make sure you can approve and finish a small milestone. A connector can query Chief without an online relay, but executing proposed work requires the relay and a ready agent.
The project owner can control Allow connected apps in project settings. When disabled, connected assistants, access tokens and chat integrations cannot access that project. Connecting an app still requires the appropriate account sign-in and project permissions; the setting does not grant access by itself.
Scope and revoke access
Read the consent screen and select only the projects you want to share. For assistants, use Settings → Connected apps to inspect or revoke connections. The MCP guide explains revocation. A Discord channel shares titles and status for the connected project; review the Discord access model before connecting one.
If a project is missing or a connection fails, follow connector troubleshooting. Use manager tasks for decisions and reviews that still require your input.