MCP connector setup
On this page
AI agents: read the complete documentation index. Append
.mdto any docs URL for its Markdown version.
Chief's remote MCP server lets an assistant read project progress, look up milestones and propose work. You sign in to Chief and choose which projects it can access. The server URL is:
https://mcp.chiefisnext.com/mcp
Before connecting
Have a Chief account and a project you may share. Follow the quickstart to create one. The project owner must leave Allow connected apps enabled in project settings.
The MCP integration page lists connection options. The setup instructions here cover Claude, Codex and Claude Code.
Connect Claude
- In Claude's connector settings, choose Add custom connector.
- Paste the server URL above and connect.
- Sign in with your Chief account.
- Select the projects Claude may access and approve the connection.
Connectors added on claude.ai also work in Claude's mobile apps. If the client shows an authorization error, reconnect through its connector controls and complete the Chief consent flow.
Connect Codex
Run this in a terminal with Codex installed:
codex mcp add chief --url https://mcp.chiefisnext.com/mcp && codex mcp login chief
The login opens Chief sign-in in your browser. Sign in, choose the projects Codex may access, and approve. This connects Codex to Chief; it is separate from choosing Codex as a task agent.
Connect Claude Code
Add the remote server:
claude mcp add --transport http chief https://mcp.chiefisnext.com/mcp
Then run /mcp inside Claude Code and choose Authenticate. Complete Chief sign-in and select the projects to share.
Check the connection
Ask your assistant:
Use Chief to list the projects I shared, then tell me what is waiting on me.
Expected result: list_projects returns the selected projects and whats_waiting lists relevant decisions, proposals and stalled work. No online relay is required to read Chief's stored progress. relay_status checks whether the computer that will execute work is connected.
| Tools | Purpose |
|---|---|
get_updates, get_summary, list_activity | Catch up on changes, summaries and project events. |
list_milestones, get_milestone | Read status, definitions of done, dependencies and results. |
list_manager_tasks | Read your to-dos. |
propose_milestone | File work for approval in Chief. |
add_manager_task, dismiss_manager_task, reopen_manager_task | Add or manage to-dos. |
relay_status, setup_relay | Check the relay or start installation and pairing. |
Try a bounded proposal:
Propose a Chief milestone to check the README's setup instructions.
Done means a report of mismatches with file references. Do not start it.
Read the resulting proposal in Chief and use the normal milestone approval controls. A new MCP connection can read and propose; it cannot approve or start work, change billing or settings, or show your code. Your local relay runs approved work.
Manage access
Changes made through MCP are attributed to the assistant in Chief's activity feed. Open Settings → Connected apps to inspect or revoke a connection. Revocation takes effect on the assistant's next request. Reconnect and select projects again if you need a fresh grant.
Relay pairing codes from setup_relay are single-use and expire after ten minutes. Treat them as temporary credentials and follow the returned instructions. If a code expires, request a new setup flow.
If a project is missing, check the signed-in Chief account, the projects selected during consent, your project permissions and Allow connected apps. See Troubleshooting. For a server community rather than an assistant, see Discord.