Your desktop assistant
Grok Bot
Add DoorOps as a remote MCP connection, then sign in. Grok in the browser has its own connector setup, covered in the guide.
Grok Bot setup guideTry Door Ops free. No card. No automatic charge. Build better door-company software with us.
Free beta & paid plansDoorOps AI integrations
Connect your assistant to your DoorOps company. Look up jobs, inspect door history and prepare operational changes with the same company permissions and a clear review before updates.
Setup guides
Each guide covers the connection, sign-in and a first safe request. Connections are included on every DoorOps plan, within your role and subscribed features; your provider’s plan and workspace permissions are separate.
Your desktop assistant
Add DoorOps as a remote MCP connection, then sign in. Grok in the browser has its own connector setup, covered in the guide.
Grok Bot setup guideChat with your company records
Connect a custom MCP app on the web. Developer mode, workspace approval and read or write access depend on your ChatGPT plan.
ChatGPT setup guideA custom connector for your team
Add DoorOps through Claude’s custom connectors and sign in. Team and Enterprise workspaces may need an owner to add it first.
Claude setup guideBuild your own assistant
Use the Responses API with DoorOps’ remote MCP server. Your application handles DoorOps OAuth and asks the user to approve changes.
OpenAI API setup guideConnect from your workspace
Add the DoorOps MCP address in Cursor and complete OAuth. Keep operational requests scoped to the company you signed in to.
Cursor setup guideThese guides use custom connections. Provider features and menus can change, and a custom connection does not require a public marketplace listing. Other clients need compatible remote MCP and DoorOps OAuth support.
One connection address
Use this address in your chosen assistant’s remote MCP setup. It opens DoorOps sign-in and authorisation for your account.
This address is public. Your company records require DoorOps sign-in.
Ask your DoorOps owner to check your role and subscribed features. Check that your AI provider permits custom connections.
Follow the provider guide, choose OAuth and sign in on DoorOps. Read the consent screen before authorising access.
Confirm your company and role, then ask for a job summary or asset history. Review any proposed change before approving it.
Try a useful request
Use the jobs and records you already have permission to access. These example requests show how to separate finding information from approving a change.
Give your connected assistant the workflow for each task from the feature skill library. Read skills by URL or download standard skill folders for agents that support them. Your company permissions still apply.
Office
“Show jobs awaiting office review. Summarise the worksheet findings and link each summary to its job.”
“Use the reviewed findings on this job to prepare a quote. Show the customer, line items and prices for my approval before saving.”
Dispatch
“Review tomorrow’s jobs and engineer availability. Show a proposed schedule and any clashes before making changes.”
“Show my team’s timesheets for this week and flag missing entries. Ask me before editing any timesheet.”
Engineer
“Show the door asset history for this job, including previous visits and unresolved findings.”
“Read my worksheet submission and help me draft a correction for office review. Do not amend or send it.”
You approve the action. Check the record, changes, recipients and consequences before an edit, delete or send. DoorOps checks company access, role permissions and enabled features; the assistant cannot grant itself more access.
Questions before you connect
Keep your company’s records under the same DoorOps permissions, whichever supported assistant you choose.
Yes. Add the DoorOps remote MCP address in Grok Bot and complete DoorOps OAuth sign-in. MCP connections are included on every DoorOps plan, within your role and subscribed features. Grok Bot and Grok in the browser use different setup paths; the Grok guide explains both.
Yes, through a custom remote MCP connection. Your provider must support custom connectors on your plan or workspace. ChatGPT’s read and write availability varies by plan. The setup guides explain the requirements without needing a public app-directory listing.
A DoorOps account on any plan, permission and subscribed features for the records and actions you need, and an AI provider plan that supports the connection. Your AI provider subscription is separate from DoorOps. A workspace owner may need to approve the connector.
Available tools can read records and prepare supported changes across DoorOps workflows, including jobs, quotes, forms, scheduling and timesheets. Write access depends on your role, enabled features and AI provider. Review the exact change before approving an edit, delete, send or other consequential action.
No. DoorOps checks the signed-in company, role and enabled features on the server. The connection cannot bypass those permissions. Begin a new connection by asking it to confirm your company and role, and reconnect if you need to use a different authorised company.
Revoke its access in DoorOps Settings, under Connected apps, and disconnect it in your AI provider. Never paste your DoorOps password, API keys or OAuth tokens into a conversation.
Start with your company’s real workflow. We can help you choose the right connection and check your role and subscribed features.
Building an integration? Read the MCP technical guide, REST API docs or CLI guide.