# OpenClaw and other personal AI assistants

Your assistant can be the place you do supported DoorOps work: ask for a morning brief, find a door's service history or prepare a quote from reviewed findings. Engineers keep using the DoorOps app, and the company records stay together.

For [Grok Bot](/docs/integrations/grok-bot), [Claude](/docs/integrations/claude), [ChatGPT and OpenAI dots](/docs/integrations/chatgpt), [Cursor](/docs/integrations/cursor) or an [OpenAI API application](/docs/integrations/openai), use the dedicated guide.

## OpenClaw

OpenClaw documents remote MCP connections and OAuth for compatible runtimes. Configure DoorOps as an outbound remote server in your OpenClaw setup, using:

```text
https://doorops.com/mcp/connect
```

Choose Streamable HTTP and OAuth with scope `mcp:use`. Follow [OpenClaw's transport and OAuth instructions](https://docs.openclaw.ai/cli/mcp/transports) to save the server and sign in. Configuration alone does not prove your chosen runtime can use the tools: check discovery and ask which DoorOps company and role are connected before using company records.

DoorOps permits loopback callbacks for local clients. A hosted agent may need a verified callback added by DoorOps; [contact us](/contact) if sign-in is refused. Each member of staff needs their own authorised DoorOps connection, rather than a shared owner's credential.

This is configuration guidance, not a verified end-to-end OpenClaw installation. Test a read first, then a small permitted change with its exact proposal and your confirmation.

## Meta Muse

Meta documents [custom connectors](https://www.meta.com/help/superintelligence/1687253048996149/) for services outside its connector list. **A DoorOps connection through Muse has not yet been verified.** Contact us to check the connection method, sign-in callback and availability for your account before relying on it for company work. This is not a claim that DoorOps is listed or approved in Meta's connector directory.

## Another assistant or agent

A direct DoorOps connection needs remote MCP over Streamable HTTP, DoorOps OAuth sign-in and support for reviewing and approving consequential actions. Give the person configuring your assistant the [MCP guide](/docs/developers/mcp) and [workflow skill library](/developers/skills). An assistant that only answers questions or accepts uploaded files cannot operate DoorOps records through those features alone.

After connecting, ask:

> Confirm my DoorOps company, my role and what I can access. Do not change records.

Then try:

> Give me this morning's office brief and link each item to its DoorOps record.

## What still needs a screen

Initial sign-in and approval, some account and payment tasks, credentials and larger-file workflows still use their normal secure screens. Supported day-to-day tasks can happen in the conversation. Available actions depend on the person's role, company features and assistant setup.

Review the exact records, changes and consequences before approving writes. Revoke access under **DoorOps Settings → Connected apps**, and disconnect in your assistant too.

Connection requirements checked **27 October 2026** against the provider documentation linked above. Provider capabilities, runtime support and availability can change.