FeaturesConnect AI tools

Connect your AI tools

Ask Claude, ChatGPT and other AI tools about your workshop’s jobs, bookings and vehicles, and let them make changes where you allow it. They work in RobotRoo as you, in the areas you choose.

Changes are off until an owner or manager turns them on. Risky ones wait for a person’s OK, and every change is listed in RobotRoo with Undo where possible.

Start in RobotRoo

What it does

Ask about your workshop

Ask your AI tool about jobs, bookings and vehicles in RobotRoo, such as what’s booked this week or where a job is up to.

Make changes where you allow it

At the second address, you choose Read or Read and change for each area. Read and change is never ticked for you.

As you, in the areas you choose

It works as the person who connected it: only what their role allows, and only the areas they chose when connecting.

Activity, changes and Disconnect

Open a connection in Settings › Other › Integrations to see its calls in the last 7 days, the changes it made with Undo, and its history. Disconnect it there at any time.

First, in RobotRoo

A workshop owner turns on Outside AI tools in Settings › Other › Integrations. This is done once for the workshop.

Then each person connects their own AI tool, as themselves. Owners and managers can connect, and the owner can let staff connect too.

The addresses.Settings › Other › Integrations shows both with a Copy button. Add the one you need, or both as separate connections.
Connection keys.Made in the same place with Create a key. Name it after the agent, choose what it may do (Read only, or Read and change), its areas and how long it works, then confirm with your password and code. RobotRoo shows the key once.
A key goes in a header.Send it as Authorization: Bearer rrk_.... Put it in the environment variable ROBOTROO_KEY yourself. Don’t paste it into a chat or write it into a file you share.
Keys expire.RobotRoo reminds you a week before. Keys are listed with connected apps, and disconnected the same way.

Making changes

An owner or manager turns on AI apps can make changes in Settings › Other › Integrations. While it’s off, every connected app can only read. Turning it off and on again gives no app its changes back: each person gives their own app changes again, with their password.

Connect the tool to https://mcp-change.robotroo.ai/mcp, as its own connector or server. When you sign in, choose Read or Read and change for each area, as far as your role allows.

Some changes wait for an OK.Removing or cancelling something, finalising an invoice, recording a payment and sending any email wait on the Approvals screen for a person who may make that change. The AI tool is told it’s waiting. A waiting change expires after 24 hours.
Ask me first.On your connection, tick an area under Ask me first and every change it makes there waits for your OK. Owners and managers can hold an area for every app with Hold every app’s changes.
Changes it made.Each connection lists its changes, newest first, with Undo where the change can be undone. Ended connections stay listed under Ended connections, with their changes.
Giving it more takes your password.Adding Read and change to an area later, or taking off Ask me first, asks for your password, and your code if you sign in with one.

Steps for your AI tool

Open your tool to see its steps. The addresses and the steps in RobotRoo above apply to every tool.

Claudeclaude.ai, the desktop and phone apps, and Claude Code

Claude on the web, the desktop app and the phone apps share one list of connectors. Add RobotRoo on the web or in the desktop app. It appears in the phone app after you next sign in there.

Plans. Custom connectors work on every Claude plan. Free allows one, so it can have the read address or the change address, not both. On Team, an Owner or Primary Owner adds it. On Enterprise, an Owner, a Primary Owner or a role that can manage the library adds it.

claude.ai and the desktop app

Go to Customize › Connectors.
Select Add, then Add custom connector.
Name it RobotRoo, enter https://mcp.robotroo.ai/mcp and select Continue.
Keep the sign-in options Claude marks Detected.
Select Add, then Connect. Sign in to RobotRoo, choose the areas and allow.

In a chat, turn it on or off under + › Connectors. Claude asks before it uses a tool, and Always allow stops the question for that tool.

To make changes, add a second connector the same way, named RobotRoo (changes), with https://mcp-change.robotroo.ai/mcp. Leave Always allow off for its change tools and Claude asks before each change.

Team and Enterprise

An Owner adds it in Organization settings › Connectors: Add, Custom, Web, then the name and address. Each member then finds it in Customize › Connectors, selects Connect and signs in to RobotRoo, so each person chooses their own areas.

Claude Code

Add RobotRoo, then sign in:

claude mcp add --transport http robotroo https://mcp.robotroo.ai/mcp

In a session, run /mcp, choose robotroo and sign in in the browser. Or run claude mcp login robotroo, adding --no-browser on a machine without one. claude -p runs can’t sign in, so sign in once in a session first.

To make changes, add the change address as a second server:

claude mcp add --transport http robotroo-changes https://mcp-change.robotroo.ai/mcp

With a connection key instead, in .mcp.json with ROBOTROO_KEY set in the environment. The file names the variable, so the key isn’t written into it:

{
  "mcpServers": {
    "robotroo": {
      "type": "http",
      "url": "https://mcp.robotroo.ai/mcp",
      "headers": { "Authorization": "Bearer ${ROBOTROO_KEY}" }
    }
  }
}

A key made for Read and change goes with the change address.

ChatGPTSign in from ChatGPT on the web

ChatGPT connects by signing in to RobotRoo. It can’t use connection keys.

Plans. OpenAI lists custom MCP servers for Business, Enterprise and Edu workspaces, and for Pro. OpenAI lists changes (write actions) for Business, Enterprise and Edu only. Pro is listed for reading only. If Add custom MCP server isn’t on your Plugins page, your plan doesn’t include it. Check your plan before adding the change address. In a Business workspace, admins and owners add it, and each member connects with their own RobotRoo sign-in.

Go to chatgpt.com/plugins.
Select +, then Add custom MCP server.
Enter the name RobotRoo and a short description.
Under Connection, choose the public endpoint and enter https://mcp.robotroo.ai/mcp.
Choose OAuth for authentication. Read the warning and select I understand and want to continue.
Select Create as a plugin, then sign in to RobotRoo and choose the areas.
In a chat, type @ and choose RobotRoo.

To make changes, add a second server the same way, named RobotRoo (changes), with https://mcp-change.robotroo.ai/mcp. ChatGPT may ask you to confirm a change before it sends it, depending on the action.

CodexThe CLI, the IDE extension and the ChatGPT desktop app

The Codex CLI, its IDE extension and the ChatGPT desktop app share one MCP setup, in ~/.codex/config.toml. Add RobotRoo once for all three.

Sign in

codex mcp add robotroo --url https://mcp.robotroo.ai/mcp
codex mcp login robotroo

A browser opens for RobotRoo’s sign-in. Add --no-browser on a machine without one.

Connection key

In ~/.codex/config.toml:

[mcp_servers.robotroo]
url = "https://mcp.robotroo.ai/mcp"
bearer_token_env_var = "ROBOTROO_KEY"

Set ROBOTROO_KEY to the key in the environment Codex runs in. Codex sends it as Authorization: Bearer with the key.

Making changes

Add the change address as a second server. With default_tools_approval_mode = "writes", Codex asks before each change and runs reading tools without asking:

[mcp_servers.robotroo-changes]
url = "https://mcp-change.robotroo.ai/mcp"
default_tools_approval_mode = "writes"

Then run codex mcp login robotroo-changes, or add bearer_token_env_var with a key made for Read and change.

OpenClawWith a connection key

OpenClaw connects with a connection key. Its setup is in ~/.openclaw/openclaw.json, under mcp.servers.

Set transport to "streamable-http". Without it OpenClaw uses SSE, which RobotRoo doesn’t serve.

In ~/.openclaw/openclaw.json:

{
  mcp: {
    servers: {
      robotroo: {
        url: "https://mcp.robotroo.ai/mcp",
        transport: "streamable-http",
        headers: { Authorization: "Bearer ${ROBOTROO_KEY}" },
      },
    },
  },
}

Or from the command line, then check the connection:

openclaw mcp set robotroo '{"url":"https://mcp.robotroo.ai/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${ROBOTROO_KEY}"}}'
openclaw mcp doctor robotroo --probe

OpenClaw reads ROBOTROO_KEY from its environment, ./.env or ~/.openclaw/.env. The variable name must be upper case.

Making changes

Make a key for Read and change and add it as a second server, robotroo-changes, with https://mcp-change.robotroo.ai/mcp and its own variable, such as ROBOTROO_CHANGE_KEY.

On OpenClaw’s own agent runtime, a change it asks for runs without a prompt in OpenClaw. RobotRoo’s own holds still apply: changes that wait for an OK, and Ask me first areas, still wait on the Approvals screen. To keep some change tools away from the agent, list them in the server’s toolFilter (include or exclude), which hides them.

If your agent runs on the Codex app-server runtime, this makes OpenClaw ask before every call to the server:

openclaw mcp configure robotroo-changes --approval prompt

GrokThrough xAI’s API, with a connection key

Through xAI’s API, add RobotRoo as a remote MCP tool in each request to https://api.x.ai/v1/responses, with a connection key.

xAI’s servers call RobotRoo, so the key passes through xAI. The API has no approval step: Grok uses the tools as it decides.

Changes. At the change address, a change Grok asks for runs without a prompt in Grok. RobotRoo’s own holds still apply: changes that wait for an OK, and Ask me first areas, still wait on the Approvals screen.

In the request’s tools:

{
  "type": "mcp",
  "server_url": "https://mcp.robotroo.ai/mcp",
  "server_label": "robotroo",
  "headers": { "Authorization": "Bearer <value of ROBOTROO_KEY>" }
}

Have your code read the key from ROBOTROO_KEY and put it in headers, with Bearer in front of it. In xAI’s own SDK the field is extra_headers.

To make changes, use https://mcp-change.robotroo.ai/mcp as server_url, with a key made for Read and change.

Other MCP appsAny app or agent that connects to remote MCP servers

Any app or agent that connects to remote MCP servers over Streamable HTTP can use the addresses. If it supports MCP sign-in, it opens RobotRoo’s sign-in. If not, make a connection key and send it in the Authorization header.

An agent that can read web pages can set itself up from robotroo.com.au/agents.md, which also tells it how to keep a key safe. Tell it: “Read https://robotroo.com.au/agents.md and connect to RobotRoo.”

Read     https://mcp.robotroo.ai/mcp
Change   https://mcp-change.robotroo.ai/mcp
Header   Authorization: Bearer <value of ROBOTROO_KEY>

For developers

Transport: Streamable HTTP
Sign-in: OAuth with a client ID metadata document or dynamic client registration, PKCE (S256), and refresh tokens
Redirects to localhost are accepted on any port
Protected resource metadata: https://mcp.robotroo.ai/.well-known/oauth-protected-resource/mcp
Reading tools are marked read-only (readOnlyHint)
A change that waits for a person’s OK answers waiting_for_approval

Questions

Can an AI tool change anything in RobotRoo?

Only at the change address, only while the workshop allows AI apps to make changes, and only in the areas the person chose Read and change for. At the read address it can’t create, edit, send or delete anything.

Which changes wait for an OK?

Changes that are hard to take back always wait: removing or cancelling something, finalising an invoice, recording a payment, and sending any email. So does every change in an area marked Ask me first, or held for every app. They wait on the Approvals screen for 24 hours.

Can I undo a change an AI tool made?

Open the connection in Settings › Other › Integrations. Changes it made lists each change, with Undo where the change can be undone.

Who can connect an AI tool?

Once an owner turns on Outside AI tools, owners and managers can connect. The owner can let staff connect too. Each person connects as themselves, and the tool uses only what that person’s role allows.

Can I change the areas later?

Yes. Open the connection in Settings › Other › Integrations. Taking areas away happens at once. Adding areas or Read and change asks for your password, and your code if you sign in with one.

How do I disconnect an AI tool?

In Settings › Other › Integrations, open the connection and choose Disconnect. A connection key is disconnected the same way. Its changes stay listed under Ended connections.

I lost a connection key. Can I see it again?

No. RobotRoo shows a key once. Disconnect the lost key and create a new one.

See the other features

Customers, vehicles, the Job Centre, quotes and invoices, bookings, reports and more.

All features Register interest