AI tools and agents

Give your AI tools the context to do useful work.

Connect an assistant to the documents your team maintains in Company OS. It can retrieve the current customer profile, brand guidelines or process before it drafts an answer, so you spend less time copying information between tools.

Create a free company See how to connect

Let your AI tools read the company context your team maintains.

A task with company context

Write an outreach email for the right audience.

Save the customer profile and messaging in Company OS. Connect your assistant, then ask it to read those documents before drafting an outreach email in your AI tool.

When the target audience changes, update the shared profile. The assistant can retrieve that version the next time it works. Connecting a tool provides access; your prompts or agent workflow decide when it reads.

Acme Robotics · Example workspace

Agent access / A connected assistant

An example MCP workflow. Each read, write or merge requires the corresponding access.

Set up access

Connect a tool. Choose what it can do.

Company OS uses MCP, an open protocol supported by AI clients such as Claude and Cursor. Your client must support remote MCP connections. An agent key belongs to one company and can be limited by department.

1. Save your context: Create a company and add a document the assistant will need, such as your customer profile.
2. Create an agent key: Choose read access to retrieve context, or grant specific permissions for writes. Copy the key when it is shown.
3. Connect your client: Add https://www.companyos.sh/api/mcp as a remote MCP server in your client and use the key as its bearer credential. Follow the client’s remote-server setup instructions.
4. Give it a task: Ask the assistant to retrieve the relevant company documents before it starts. Check the documents and resulting work together.

Reading, writing and merging are separate choices.

A read-only connection is enough to brief an assistant. Write permission allows direct document commits, including on the shared version. A branch supports review, but a mandatory human approval step is not imposed on every agent write.

Read: Retrieve documents, search company context and read revision history.
Write and propose: Grant document-write and branch-creation permissions for agents that should contribute changes.
Merge: Grant branch-merge permission separately. Without it, the agent cannot merge its proposal into the shared version.
Revoke: Revoke a key to remove its access without removing team members or their work.

For automated workflows

Build a workflow that responds to changes.

An agent can request changes since the last event it read. You can also configure a webhook endpoint to receive signed change notifications.

Use these signals in your own workflow, for example to refresh a sales brief after a pricing change. Company OS supplies the change history; your connected workflow decides what to do next.

For Cadre, choose a bot webhook and the company events it should receive. Company OS sends a short brief with a link to the changed document or branch.

Explore the Cadre connection

Acme Robotics · Example workspace

Company documents / History

Every saved change keeps its author, message and earlier version.

MCP reference

Tools for reading and updating company context.

These core tools cover documents, branches, search and the change history. The server’s tools/list response provides the current schemas, including additional tools for tables, canvases and other product areas.

Tool	Permission	What it does
config_pull	context:read	The cold-start call. Returns the company, its schema and the documents the key may read, with paging.
document_get	context:read	One document at head or at a revision, as typed JSON with its hash.
document_list	context:read	Documents by department, with head sequence and freshness.
document_history	context:read	The revision log for one document.
document_put	context:write	Commit new content against a base hash. Refused if the head moved.
document_revert	context:revert	Commit an earlier revision's content forward.
branch_create	branch:create	Open a branch to propose changes on.
branch_list	context:read	Open and merged branches.
branch_diff	context:read	Field-level diff of a branch against main.
branch_merge	branch:merge	Merge with a resolution per conflict. Writes a receipt.
merge_list	context:read	Merge receipts.
merge_revert	branch:merge	Undo a merge, forward.
context_search	context:read	Search inside the company's index. Filtered by tenant before ranking.
context_changes	context:read	A cursor over the event stream since a sequence.
schema_describe	context:read	The typed registry: kinds, fields, hints, layouts.
run_append	run:append	Append-only log of what the agent did and why.

Document writes include the version the agent read. If it has changed in the meantime, the write is refused so the agent can retrieve the latest version before trying again.

Start with one useful document.

Save your customer profile, connect an assistant, and use it to brief your next task.

Create a free company Compare plans