402 tools on your record
Operator can use every tool on your record, from CRM to the ledger, with the rights each has in the app and your approval on every write and send.
0
tools across nine domains
- CRM0
- Funds & capital0
- Portfolio & reporting0
- Dealflow & network0
- Communications & events0
- Platform & people0
- Hiring0
- Ledger & expenses0
- Documents & data rooms0
Find the right tool
Operator picks from every tool on your record, and you can browse them in the app, your terminal or your agent.
Your team’s playbooks
Give Operator your team’s own instructions, like how you write an LP update, and each job follows the version it started with.
CLI & MCP
Tools in your terminal
List tools by domain, search them by what you need and read a tool’s inputs before you use it, from your terminal or your agent over MCP.
# List the tools in a domain
$operator tools --domain funds
# Find tools by what they do
$operator tools search "capital call"
# Read one tool’s inputs and rules
$operator tool funds.capital_call.draft
# Your skills assigned to Operator
$operator skills
# Start a job that follows a skill
$operator run "Draft the Q3 LP update" --skill /lp-update
- tools_searchFind tools by what they do
- skills_listSkills assigned to Operator
- runStart a job, with a skill if you like
Install with npx @allocator-one/operator · add it to any MCP client with operator mcp
The catalogue
What each tool does
A selection from Operator’s catalogue by domain, each tool running with your rights and waiting for your approval on writes and sends.
Showing 42 of 42 examples · 402 tools in all
Every tool, by domain
- CRM108
46 reads · 62 writescrm.party.search
- Funds & capital69
55 reads · 14 writesfunds.capital_call.draft
- Portfolio & reporting62
59 reads · 3 writesportfolio.performance.read
- Dealflow & network46
40 reads · 6 writesdealflow.selection_case.get
- Communications & events43
30 reads · 13 writescommunications.email.send
- Platform & people29
18 reads · 11 writesplatform.team.list
- Hiring26
15 reads · 11 writeshiring.candidate_list.search
- Ledger & expenses10
9 reads · 1 writeledger.book.review
- Documents & data rooms9
8 reads · 1 writedocuments.dataroom.publish
Rules for every tool
Whatever a tool touches, it follows the same rules.
- Tools accept only the inputs they declare
- A tool accepts only the inputs it declares and returns a result of bounded size. Nothing open-ended goes in or comes out.
- The same permission as the app
- Each tool checks the permission its page in Infra One checks, at the scope you have there.
- Results re-checked against your access
- What Operator read is checked against your access again before it reaches the model or the job’s room.
- Every write approved and read back
- Every write is approved as one exact change, and read back from the record once it’s applied.
- Turn off any tool
- Your organization can turn off a single tool, or Operator as a whole, and it stops at once.
- Every new tool declares how it’s used
- Every new tool declares how Operator uses it before it ships: as a read, a write, a send, or not at all.
More on Operator
Four views of Operator
Each page covers one part of how Operator works.
Plans
Plans across Operator and your team
Chains of work that run for days or weeks, across Operator and your team, with the waits between them.
See plansApprovals
Every write waits for your approval
Every write waits for an exact approval, and every change is checked after it lands.
See approvalsCLI & MCP
Operator in your terminal, CI or agent
Run Operator from your shell, your scripts and your CI, or hand it to your own agent over MCP.
See the CLI
Common questions
A tool does one thing on your record, like reading a capital account or drafting a call. A skill is your team’s own instructions for a kind of work, like how you write an LP update. Operator follows the skill and uses the tools.
No. Every tool runs with the rights of the person Operator is working for, and they’re checked again at every step.
You add your own skills. Tools come from Infra One, so each one carries the same permission checks and approvals as the rest of the catalogue.
This page shows a selection. The counts by domain cover every tool that reads or changes your record; tools that only steer the chat, like navigating the app or naming a conversation, aren’t counted.
No. Every call runs inside one organization: the one the job belongs to.
Your approval of the exact message: sender, recipients, wording and attachments. Change any of it and Operator asks again.
Tools under your rights
Every tool runs with your rights, and writes and sends wait for your approval.