IntegrationsConnect DoorOps to Cursor
Connect DoorOps to Cursor
Configure DoorOps as a remote MCP server in Cursor, sign in with OAuth and use company records with your normal permissions.
Cursor can use DoorOps through a custom remote MCP server. Your DoorOps company needs MCP access enabled, and your Cursor workspace must permit the connection.
Set up the connection
- Create or update
~/.cursor/mcp.jsonfor access across projects, or.cursor/mcp.jsonfor one project. Preserve any existing server entries. - Add the DoorOps entry below.
- Open Customize in Cursor, find DoorOps and complete its OAuth sign-in in the browser.
- Check the company and requested access before allowing the connection. Enable the server for your task.
{
"mcpServers": {
"DoorOps": {
"url": "https://doorops.com/mcp/connect"
}
}
}
No password, access token or client secret belongs in this configuration. DoorOps supports automatic OAuth client registration.
Start with:
Tell me which DoorOps company and role I am connected as, and what I can access.
What to ask
- “Show the open jobs at this site.”
- “Find this customer's latest submitted forms.”
- “Show this door's service history.”
- “Prepare this customer update, then show the exact changes for my confirmation.”
Cursor's available models use the same connected tools; changing the model does not change your DoorOps permissions. Keep human confirmation for creations, edits, sends, scheduling, merges and deletions. See the MCP guide for previews and business safeguards.
Team setup and recovery
Team administrators can distribute MCP servers through Dashboard → Plugins & MCPs. Workspace MCP policy can restrict which servers are allowed. Each person should complete their own DoorOps OAuth sign-in.
If tools are missing, check that DoorOps is enabled, refresh the connection and verify MCP access for the correct company. Reconnect if sign-in expires. For HTTP 429, wait for Retry-After before retrying once.
Disable/remove the server in Cursor and revoke it under DoorOps → Settings → Connected apps to stop access. Custom configuration does not require a marketplace listing.
Guidance checked 7 October 2026 against Cursor's official MCP documentation.