AI assistants

Let your AI assistant see your customers and your jobs.

The quote you never sent is buried in a text thread no tool can read. Put your work in Scoped and an assistant can see the same clients, jobs and pipeline your crew sees. Ask it where a job stands before you pick up the phone, because the work goes to whoever calls back first.

Two setup paths. You decide what the assistant can touch.

Two assistants you can connect today

Scoped keeps named setup paths for Codex and Claude Code. Each one is written and tested against the client’s own commands, so you follow the steps and you are done.

Codex
Add Scoped from the Codex command line, approve the connection in your browser, and it works inside the limits you set.
Claude Code
Add Scoped to Claude Code, sign in once, and the connection stays tied to the one workspace you picked.

Both connect over MCP — the standard that lets AI tools plug into the apps a business already runs on. You do not need to know anything else about it to set this up.

What a connected assistant can actually do

  • Ask where every job stands and get the answer off the live pipeline, not your memory.
  • Pull up a customer’s history before you call them back: past jobs, open deals, the notes someone left.
  • Update the next step on a job, change that step’s status, and add a comment the rest of the team sees.
  • Find the work that stalled — the quote nobody chased, the job that has not moved in weeks.

Scoped does not run the AI. The assistant runs in its own tool and Scoped is the shared workspace it plugs into: it reads the context you let it read and posts the updates you ask for. It does not go off and work on its own, and it does not send anything to your customers. Read where the agent runtime ends and Scoped begins before you connect a tool that can write.

The owner who can ask a question and get a straight answer off real records is the one who calls back first.

You stay in control of what it touches

  • You approve the connection yourself, for one workspace at a time.
  • You choose what it can reach, and the consent screen spells that out before you agree.
  • You can look at a connection whenever you want and revoke it.
  • Every change records the authorizing person and connection source, so nothing lands anonymously.
  • Revoke a workspace grant and future access through it stops.

Scoped rechecks the grant, your membership, the workspace and the scope on every request. See the authorized update example for exactly what your team reads afterwards.

Pick a setup path and start small

Open the Codex guide or the Claude Code guide. The list is short on purpose: a tool is named here only when Scoped maintains and tests the setup for it, not because the standard would technically allow it. The agent-first project management and MCP explainer covers what both guides share.

No workspace yet? Create a workspace first, put a few clients and jobs in it, then connect your assistant.

Stop losing the work

Every lead in one place.
Nothing left to memory.

  • Jobs
  • Quotes
  • Callbacks
  • Crews
  • Customers
  • Bookings