Connect any MCP client to Chief at mcp.chief.bot
Point Claude, Cursor, or any other MCP client at mcp.chief.bot and work with your Chief actions, memories, projects, live sessions, and skills from outside Chief.
Using Chief from another tool used to mean running an MCP server yourself and keeping it up to date. You can now connect to one Chief hosts.
Hosted MCP endpoint
Add https://mcp.chief.bot/mcp as a remote MCP server in your client of choice and connect. You get the same tools as the MCP server we maintain publicly, without installing or updating anything locally.
More resources over the API
The public API now covers actions, memories, projects, live sessions, and skills, so your own scripts, SDKs, and command line tools can read and work with the same things you see in Chief.
Consistent paging across resources
Every one of those resources pages the same way, which means one approach to walking a long list instead of a different quirk per endpoint.
Load more on live sessions
The live sessions list previously tried to show everything at once. It now loads a batch at a time with a Load more button at the bottom, and a failure to load shows an error rather than looking like you have no sessions.
If you already work in an MCP-capable editor or assistant, add the endpoint and your Chief context follows you there.