Try Door Ops free. No card. No automatic charge. Build better door-company software with us.
Free beta & paid plansMCP technical guide
Connect an assistant to DoorOps with OAuth.
DoorOps provides a remote MCP server for authenticated company operations. Use the shared connection address, complete OAuth and confirm the signed-in company before requesting records or changes.
Requirements
Access follows the signed-in member.
MCP connections are included on every DoorOps plan. Use your DoorOps account and a client that supports remote MCP with OAuth. AI provider plans and workspace approvals are separate from DoorOps access.
- Complete DoorOps OAuth with the
mcp:usescope. - Confirm the connected company, role and enabled features before operating.
- Review the exact proposed edit, delete, send or other consequential action before approving it.
- Revoke the connection under DoorOps Settings, Connected apps.
Use the correct server address
- Company operations, shared address
https://doorops.com/mcp/connectUse this in the provider guides. OAuth binds access to your authorised DoorOps company.
- Company subdomain address
https://{tenant}.doorops.com/mcpAn authenticated alternative for a specific company. Use the address shown in its AI agent settings.
- Public product information
https://doorops.com/mcpProduct facts and consent-bound enquiries. It does not expose your company’s operational records.
Provider instructions
Follow the guide for your client.
Connection menus and provider entitlements differ. These guides cover the current setup, first identity check and approval behaviour in one place.
Discover, read, prepare, approve
Use the tools available to this account.
Discover the live tool catalogue instead of hard-coding a list. DoorOps checks the company, role, policies and enabled features on the server; a client cannot bypass them.
Begin with who-am-i-tool to verify identity. Workflow discovery and descriptions help the assistant find the supported operation and its requirements before preparing a change.
Read operations can inspect jobs, asset history and worksheet submissions within the member’s permissions. For supported writes, prepare a preview and have the user approve its exact contents before execution. Provider-level approval controls are additional to DoorOps checks.
Read the operate-doorops skill for authenticated agent behaviour. Keep tokens in your application’s secure credential storage; never ask a user to paste a password or token into chat.
Prefer a script or a custom integration?
Use the DoorOps CLI or REST API with the appropriate organisation-scoped access. The same company permissions apply.