GitHub & Code
brief
Push an Update with a Brief
Push an update the one way every update is pushed: a brief in plain words, then the technical body, then the chip the server signs.
Ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "push an update", and it calls brief.
Example call
The MCP tools/call params, with the required arguments only.
{
"arguments": {
"kind": "<kind>"
},
"name": "brief"
}Arguments
accountstringoptionalpullRequest: connected GitHub login to act as. Defaults to the Primary account.basestringoptionalpullRequest, when opening: the branch to merge intobodystringoptionalThe technical body (markdown), drawn under the brief. Code, paths and names belong here.briefobjectoptionalThe brief that opens this update, in plain words a person reads: an opening of one plain sentence of at most 200 characters, then five rows of 4 words to 300 characters each (who it affects, what was wrong, what changes, why it matters,…citationRefstringoptionalpullRequest: the BuildDoc, Task or ticket this implements, as openPullRequest takes itdryRunbooleanoptionaltrue returns the drawn text and any problems and writes nothing. Works for every kind and needs no target.headstringoptionalpullRequest, when opening: the feature branch with the changeskindstringrequiredWhat is being pushed. "pullRequest" and "issue" are built; "ticket", "page" and "comment" are reserved for part 2 and refuse.labelsstring[]optionalissue: labels to applyownerstringoptionalRepository ownerpullNumbernumberoptionalpullRequest: pass it to update that open pull request (with `body`, the brief and body are both replaced; without, only the brief is and the rest of the body is kept); omit it to open a new onereaderstringoptionaldryRun only: who reads the rendering. "person" (default) draws the table and needs every pull request, ticket and page as a named link; "ai" draws plain lines with each raw address on its own line. A GitHub pull request or issue is always…repostringoptionalRepository nametitlestringoptionalThe title; required to open a pull request or an issue
Returns
dryRun: true returns the drawn text and the problems and writes nothing; reader: "ai" previews the rendering for another AI.
Ask for it
The Cloud routes these requests to this verb.
- push an update
- open a PR with a brief
- file this issue
- check my brief
Pair it with
The verbs that finish the job.
Questions
What does brief do?
Push an update the one way every update is pushed: a brief in plain words, then the technical body, then the chip the server signs. It is one of the tools The Cloud MCP server gives every connected AI.
How do I use brief from Claude or ChatGPT?
Connect your AI to The Cloud at https://mcp.thecloud.so/mcp and sign in once. Then ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "push an update", and it calls brief.
Is brief safe to let an AI call?
brief changes your workspace. What an AI creates is Private until you share it. It reaches a system outside The Cloud on your behalf.
Connect
One endpoint gives your AI this tool and every other one: connect Claude, ChatGPT, Cursor or Gemini, read what The Cloud is, or see pricing.