Set up your agent

Set up your agent for a project

CompanyOS plugs into your AI coding agent — Claude Code and any MCP client — so it reaches for the company brain whenever it searches for or saves project information. Setup is per project and opt-in: you only wire the projects where you want it, and your other work is untouched.

Quick setup (one command)

From the root of a project you want connected, fetch the setup script, review it, and run it:

# from the root of a project you want connected
curl -fsSL https://company.chele.bi/companyos-agent-init.sh -o companyos-agent-init.sh
bash companyos-agent-init.sh

It writes the three pieces below and is safe to re-run (it refreshes its own managed block rather than duplicating):

• .mcp.json — a project-scoped connection to the CompanyOS MCP (OAuth; no token is stored in the file).
• CLAUDE.md — a marked CompanyOS block that tells the agent to search and save in CompanyOS first.
• .claude/skills/companyos/SKILL.md — an on-demand skill with the tool map and when to use it.

Authorize once

1. 1
   Open the project

   Open it in Claude Code (or your MCP client). It detects .mcp.json and asks to approve the companyos server.
2. 2
   Run /mcp

   Run /mcp and approve companyos. A browser opens for CompanyOS consent — pick your workspace and grant access (tick Root / Admin for the full tool surface).
3. 3
   Done

   Your agent now uses CompanyOS for project search and save in this project, and nowhere else.

Prefer to wire it by hand?

The script only writes these three things — you can paste them yourself, which also works for Cursor, Claude Desktop, and other MCP clients.

1. .mcp.json at the project root:

{
  "mcpServers": {
    "companyos": {
      "type": "http",
      "url": "https://api.company.chele.bi/api/v1/mcp"
    }
  }
}

2. A CompanyOS block in CLAUDE.md (or your client's project rules file):

## CompanyOS (company brain)

CompanyOS is the source of truth for this org's projects, tasks, meetings,
notes, calendar, and activity.

- Search CompanyOS (`mcp__companyos__*`) before answering anything about the
  company, a project, a task, a person, or a deadline.
- Save tasks, notes, decisions, and follow-ups to CompanyOS, not just locally.
- Treat it as authoritative; local memory should point to it, not duplicate it.

3. Optionally, a skill at .claude/skills/companyos/SKILL.md whose description triggers on project search/save and lists the mcp__companyos__* tools.

Other clients

Cursor and Claude Desktop also read a project .mcp.json (or their own MCP settings) plus a project rules file. Use the same three pieces, putting the routing block in that client's rules file instead of CLAUDE.md.