Barry. Get connected
For developers

Build on the company brain.

Barry exposes everything it knows over MCP and a REST API. Connect an AI tool in one command, or wire your own systems into the map.

Overview

Barry observes how your organisation works and builds a living process map — the company brain. Two ways in:

MCP — the fastest path. Point any MCP-capable client (Claude, ChatGPT, Cursor, VS Code) at your Barry server and query the brain conversationally.

REST API — for your own dashboards, pipelines, and integrations. Same data, plain JSON.

Responses are aggregated by default — admin roles control access to individual-level data.

Connect via MCP

Your organisation gets a dedicated MCP server:

endpoint
https://dev.staffmetrics.ai/mcp

Add it to Claude in one command:

terminal
$ claude mcp add barry https://dev.staffmetrics.ai/mcp
✓ barry connected · 6 tools available

Client setup

ChatGPT

Settings → Connectors → Add connector → paste https://dev.staffmetrics.ai/mcp and authorise with your workspace SSO.

Cursor

.cursor/mcp.json
{
"mcpServers": {
"barry": { "url": "https://dev.staffmetrics.ai/mcp" }
}
}

VS Code

settings.json
{
"mcp.servers": {
"barry": { "url": "https://dev.staffmetrics.ai/mcp" }
}
}

Authentication

API keys are issued per workspace in the admin console (Settings → Developers). Send the key as a bearer token:

curl
$ curl https://dev.staffmetrics.ai/api/v1/processes \
-H "Authorization: Bearer sk_barry_…"

Keys are scoped: read:map, read:insights, write:automations. MCP sessions inherit the scopes of the authorising user.

REST endpoints

MethodPathReturns
GET/api/v1/processesAll mapped processes, ranked by automation readiness
GET/api/v1/processes/:id/mapNode/edge graph of one process (React Flow-compatible JSON)
GET/api/v1/insightsTeam-level friction, hours, and trend data
GET/api/v1/me/dayThe caller's own private day view
POST/api/v1/automations/proposalsPropose an automation from a mapped process
response · GET /processes
{
"id": "proc_invoice_recon",
"name": "Invoice reconciliation",
"readiness": 0.84,
"hours_per_week": 42,
"teams": 3 // aggregated — never people
}

MCP tools

Connected clients see six tools:

  • barry.search_processes — find processes by name, team, or system
  • barry.get_map — fetch the node/edge graph for a process
  • barry.time_report — where hours go, team-level or (for the caller) personal
  • barry.automation_candidates — ranked list with estimated hours returned
  • barry.propose_automation — draft an automation spec for review
  • barry.ask — free-form questions against the brain

Event schema

Barry's raw unit is an event — hashed at the source, non-human-readable, no content or pixels:

event
{
"id": "evt_c81f3a",
"kind": "app_focus",
"ref": "h(4f2e…9c)", // salted hash, resolved only in aggregate
"t": "09:41:07",
"dur_s": 412
}

Raw events are not queryable through the API — only their aggregates are. See how privacy works.

Rate limits

600 requests / min per workspace on REST; MCP sessions are unmetered on the Self service plan (fair use). 429 responses carry a Retry-After header.

Questions? Book Demo — bring your security team.