Most CMS servers give an agent create and update against live content, and the only safety net is whoever notices afterwards. Working on a branch and merging turns a content edit into something a person approves — the same review model developers already have. The documentation tools are the other well-judged part: query and mutation guides mean the agent can look up the shape of a call rather than guessing at a GraphQL schema.
BaseHub's own endpoint. Content is versioned like a repository — the agent can commit a change, work on a branch, check out a ref and merge — which is unusual for a CMS.
- query_content, and create, update or delete blocks
- Version control: commit, branch, checkout, merge
- Repository information — refs, branches and the content structure
- Asset uploads via a signed upload URL
- Developer documentation search, with query and mutation guides for getting the calls right
A user-level BaseHub MCP token with read and write rights. Dashboard → Developers → Connect writes the URL and token into Cursor in one click; other clients are configured by hand. The server URL is not a public address, so it comes from your dashboard.