Docs · MCP

Your company brain, for any agent.

Clearly is an MCP server — not a plugin. Agents connect out to it. Once connected, Claude Code / Cursor / any MCP client can search your org’s context, write decisions back so they compound, schedule their own follow-ups, and inherit your team’s skills. The server is hosted at relay.clearly.sh/mcp — nothing to deploy or run.

Connect an agent

Mint a token, then point a client at the hosted endpoint. Both paths below need a token.

1 · Mint a token

Settings → Developers → Create MCP token. Shown once, revocable, rate-limited (120/min). Pick least privilege.

https://relay.clearly.sh/mcp
rpc:read   ·   rpc:write   ·   admin

rpc:read — search + read. rpc:write — also create documents + schedule wakes. admin — owner-only.

Want the token to act as a specific agent (gated by that agent’s access + attributed in activity)? Mint it from the agent’s card in the Agents modal → Connect over MCP. See Agent identity below.

2 · Install

Claude Code: the plugin wires the server AND ships the skills. Any other client: drop the endpoint + token into its config.

export CLEARLY_MCP_TOKEN="ck_mcp_..."
/plugin marketplace add clearly-sh/clearly-plugin
/plugin install clearly@clearly
/clearly:init
claude mcp add --transport http clearly https://relay.clearly.sh/mcp \
  --header "Authorization: Bearer ck_mcp_..."
{
  "mcpServers": {
    "clearly": {
      "url": "https://relay.clearly.sh/mcp",
      "headers": { "Authorization": "Bearer ck_mcp_..." }
    }
  }
}

~/.cursor/mcp.json or claude_desktop_config.json

What your agents gain

The headline tools — plus the full ~200-action workspace surface via the catalog.

Company brain
  • clearly_context_search— One ranked search across prompts, docs, decisions + facts — this workspace, or the whole org with scope:"org".
  • clearly_context_write— Write a PRD / decision back so the next agent finds it (private:true keeps it workspace-local).
  • clearly_context_map— Orient: brain stats, recurring topics, and the orgs it can federate across.
Self-prompting
  • clearly_schedule_wake— Write a prompt for its future self + schedule a wake — one-shot (runAt) or recurring (cron), inline or by reference.
Skills
  • clearly_skill_list— Discover the workspace’s reusable procedures.
  • clearly_skill_get— Load one skill’s full step-by-step instructions on demand.
Guidance
  • clearly_guide— The Company Brain usage playbook — call it once on connect to learn how to use the rest.
Everything else
  • clearly_workspace_catalog— List all ~200 workspace actions, with schemas + examples.
  • clearly_workspace_invoke— Run any workspace action by name.

Agent identity & sessions

Make an MCP connection behave like the desktop daemon — an agent acting as itself.

Agent-scoped tokens

Mint from the Agents modal → Connect over MCP, or create-mcp-token { agentId }.

A normal token acts as you. An agent-scoped token acts as one of your agents: every call is gated by that agent’s own scope / tool-allowlist (a read-only agent can’t mutate even though you can) and attributed to it in the activity log.

Sessions

Streamable-HTTP transport.

initialize issues an Mcp-Session-Id; clients echo it on subsequent calls so a session’s tool calls correlate. Stateless if absent — every client keeps working unchanged.

The usage playbook

How to actually work the brain — available to every client, no plugin.

Call clearly_guide (or the clearly-workflows MCP prompt, surfaced as a slash command in Claude Code) to get the loop:

1. context_map        — orient
2. context_search     — read before you write (scope:"org" to federate)
3. context_write      — file decisions back so they compound
4. schedule_wake      — write a prompt for your future self
5. skill_list/get     — follow the team's procedures, don't improvise

Rules of thumb: read → act → write back; scope:"org" for cross-team questions; private:true for sensitive writes; promptRef over inline so the latest version fires.

Skills your agents inherit

Claude-style procedures — a name, a when-to-use trigger, a step-by-step body.

A connected agent calls clearly_skill_list to see your team’s skills, then clearly_skill_getto load one when its trigger matches — so it works the way your workspace works, not from a blank slate.

Clearly ships no default skills — the library is grown: authored by hand, generated when you create an agent, or researched autonomously by a skill-research scheduled run (web-grounded, with sources). It compounds as your team works.

From the terminal (CLI)

The beehaven CLI drives the same workspace from your shell (needs the Hive desktop app running).

beehaven connect home
beehaven actions                                    # everything you can call
beehaven call context-search '{"query":"roadmap"}'  # search your brain
beehaven call schedule-wake '{"prompt":"Review the launch","runAt":1751000000000}'
← Connect your Claude planAll docs →