distribution.techdistribution.tech

MCP tool

Company context

brain_get

Your company context as confirmed in the workspace (name, summary, audience), its version and the version history.

Overview

Your company context as confirmed in the workspace (name, summary, audience), its version and the version history. Optionally one section.

Server
https://app.distribution.tech/api/mcp
Scope
brain:read
Changes data
No, a read
REST endpoint
GET /brain

Arguments

Arguments of brain_get
NameTypeRequiredDescription
sectionone of "name", "summary", "audience"NoOne section. Leave out for the whole context.

Call with curl

The server speaks streamable HTTP, so one JSON-RPC tools/call request runs the tool. Set DISTRIBUTION_API_KEY to a key from Developers with the brain:read scope; the arguments shown are the required ones.

curl
curl -X POST "https://app.distribution.tech/api/mcp" \
  -H "Authorization: Bearer $DISTRIBUTION_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "brain_get",
    "arguments": {}
  }
}'

Result

The answer's structuredContent follows the tool's output schema (the same JSON is in its text content). It has these fields:

Result fields of brain_get
NameTypeRequiredDescription
versionintegerYes
confirmed_atstring (date-time) or nullYes
contextobjectYes
versionsarray of objectYes
structuredContent, every field with its type
{
  "version": 0,
  "confirmed_at": "<date-time>",
  "context": {
    "name": "<string>",
    "summary": "<string>",
    "audience": "<string>"
  },
  "versions": [
    {
      "version": 0,
      "created_at": "<date-time>"
    }
  ]
}

Get access

Keys are created in Developers once your brand is approved. Connect an agent to ask for access, then read the agent guide for the full flow.