query_contentLABSCO SUMMARY
Branching is what makes agent-written content reviewable instead of published.
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.
What it is
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.
What you get
- 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
Requirements
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.
USE CASES
01
Drafting content without touching live
Branch, make the edits, then merge once someone has read them.
02
Bulk-updating structured blocks
Query the content, update the blocks that match, and commit the change in one pass.
03
Getting the query right first time
Search the developer docs for the query or mutation shape before calling it.
17 tools
Listed in project docs. Your client may show a different list.
create_blocksupdate_blocksdelete_blockscommitmerge_branchcreate_branchcheckout_branchget_current_reflist_branchesget_upload_urlget_content_structureget_example_content_structureget_query_guidelinesget_mutation_guidelinessearch_developer_docsget_tokenBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
User-level BaseHub MCP token with read and write rights; the Dashboard Connect flow writes the server URL and token into your client config
INSTALLATION
Connect your client
BaseHub does not publish the server URL — the Connect flow writes it, together with your own read-write MCP token, into the client config.
Server setup
In the BaseHub dashboard, open Developers → Connect.
Choose Add to Cursor — BaseHub writes the server URL and your MCP token into the Cursor config for you.
For any other client, such as Claude Desktop, copy your BaseHub MCP token and set the server up by hand.
