# dotloop MCP connector

The dotloop connector brings loops, contacts, documents, folders, participants and task lists into Claude, ChatGPT, Cursor and Microsoft Copilot, with every call running as the signed-in person and landing in an audit log.

Source: https://elaichi.ai/connectors/dotloop/

## Facts

| | |
| --- | --- |
| Application | dotloop |
| Category | CRM |
| AI tools | 43 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once dotloop is connected

- Add the lender as a participant on the Maple Street loop.
- Which task lists on my active loops still have open items?
- Create a contact for the buyer from today's open house.

## Connect dotloop in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick dotloop.
2. Optionally set Share with, then press Connect.
3. Supply your own dotloop app, then approve. dotloop needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which dotloop tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## dotloop MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## dotloop MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## dotloop MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## dotloop MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## dotloop MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect dotloop to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a dotloop tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with dotloop through Elaichi

### Start a loop right after the offer

Agents. Ask for a new loop for the property, add the buyer, seller and lender as participants, and set up the folders before the paperwork arrives.

### Check which loops still have open tasks

Transaction coordination. Pull the task lists across every active loop and get a plain-language rundown of what is still outstanding and on which transaction.

### Keep contact records current

Office admin. Create a contact for a new client, fix a phone number or email, or remove a duplicate without opening dotloop and clicking through the contact list.

### Review a loop's documents before closing

Compliance. List the documents and folders on a loop and ask what is there and what is missing, so the file is complete before it goes to the broker.

### Catch up on loop activity

Team leads. Ask what happened on a loop in the past week and get a summary of the activity, from new documents to participant changes, without reading each entry.

### Update loop details in bulk

Brokerage operations. Change closing dates, prices or other loop details across several transactions in one request instead of editing each loop by hand.

## Elaichi vs Zapier MCP vs Composio for dotloop

All three can connect dotloop to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over dotloop tools | Allow or restrict single dotloop tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per dotloop call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect dotloop to Claude?

Connect dotloop in Elaichi first, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. dotloop connects over OAuth, but it needs an OAuth application registered inside dotloop, so one person brings a client ID and secret once and nobody else ever handles them. After that, each person signs in to dotloop as themselves.

### Does dotloop work with ChatGPT and Cursor as well as Claude?

Yes. Once dotloop is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect dotloop once and every client uses it.

### What can an AI agent actually do with my dotloop data?

It can create a loop, add or update participants, create folders and documents on a loop, look at task lists and recent activity, and create, update or delete contacts in dotloop. You ask in plain language, such as adding the lender to a loop or listing which documents a loop holds. Short concrete asks work better than long sentences.

### Does connecting dotloop give the AI access to every loop in my brokerage?

No. Access to dotloop follows the person who signed in, so an agent sees only the loops, contacts and documents that person can already see in dotloop. Elaichi can narrow that further with roles and restrictions, and it can never widen it.

### Can my team share one dotloop connection?

Yes. One person connects dotloop in Elaichi and shares it with a team, and nobody else touches the client ID, secret or any other credential. Each person still signs in as themselves, so the audit log names who created a loop or changed a contact.

### Can I stop an agent from deleting or changing things in dotloop?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting dotloop contacts or removing loop participants for a role or for one person while leaving reading and creating open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a dotloop connection when someone leaves?

Offboarding that person in Elaichi ends their dotloop access at once. A shared dotloop connection keeps working for everyone else on the team. If you disconnect dotloop in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the dotloop MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. dotloop is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for dotloop?

Yes. Both let Claude, ChatGPT or Cursor use dotloop. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every dotloop call.

### How is Elaichi different from Composio for dotloop?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to dotloop: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 43 dotloop tools

Every tool below is callable through https://api.elaichi.ai/mcp once dotloop is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all dotloop account** (List). Get Account Details. Retrieve account details. Returns one object (the connected user, with defaultProfileId), not a list. Needs the client scope account:read.
- **Create a dotloop contact** (Create). Create a Contact. Create a new contact. Needs the client scope contact:write.
- **Delete a dotloop contact by ID** (Delete). Delete a Contact. Delete an existing contact by id. Needs the client scope contact:write. Required: id.
- **Get single dotloop contact by ID** (Get). Get a Contact. Retrieve an individual contact by id. Needs the client scope contact:read. Required: id.
- **List all dotloop contacts** (List). List all Contacts. List all contacts in the user account. Needs the client scope contact:read. The connector pages with batch_size / batch_number (limit sets batch_size, max 100).
- **Update a dotloop contact by ID** (Update). Update a Contact. Update an existing contact by id. Needs the client scope contact:write. Required: id.
- **List all dotloop loop activities** (List). List all Loop Activities. List all activities for a loop. Needs the client scope loop:read. Required: profile_id, loop_id. The connector pages with batch_size / batch_number (limit sets batch_size, max 100).
- **Dotloop loop details bulk update** (Update). Update Loop Details. Update loop details by id. One object (the loop's details), not a batch: the connector names writes without a trailing record id bulk_*. Send only the sections and fields to change (e.g. {"Financials": {"purchase_sale_price": "342342"}}); names with spaces or symbols are snake_case here and the connector sends dotloop's names. Needs the client scope loop:write. Required: profile_id, loop_id.
- **Get single dotloop loop detail by ID** (Get). Get Loop Details. Retrieve loop details by id. The id is the loop id. Details come back grouped by section with dotloop's own field names (spaces included, e.g. "Property Address" &gt; "Street Name"; see the response schema). Needs the client scope loop:read. Required: id, profile_id.
- **Create a dotloop loop document** (Create). Upload a Document. Upload a individual document (binary) via multipart form post. Upload a PDF as a multipart/form-data file part; the part's file name becomes the document name. Needs the client scope loop:write. Required: profile_id, loop_id, folder_id, file.
- **Get single dotloop loop document by ID** (Get). Get a Document. Retrieve an individual document by document_id. Needs the client scope loop:read. Required: id, profile_id, loop_id, folder_id.
- **List all dotloop loop documents** (List). List all Documents. List all documents in a loop. Needs the client scope loop:read. Required: profile_id, loop_id, folder_id.
- **Create a dotloop loop folder** (Create). Create a Folder. Create a new folder. Needs the client scope loop:write. Required: profile_id, loop_id.
- **Get single dotloop loop folder by ID** (Get). Get a Folder. Retrieve an individual folder by id. Needs the client scope loop:read. Required: id, profile_id, loop_id.
- **List all dotloop loop folders** (List). List all Folders. List all folders in a loop. Needs the client scope loop:read. Required: profile_id, loop_id.
- **Update a dotloop loop folder by ID** (Update). Update a Folder. Update an existing folder by id. Needs the client scope loop:write. Required: id, profile_id, loop_id.
- **Create a dotloop loop it** (Create). Loop-It. Creates a loop in one call: property, participants (added to the contacts directory) and template. profile_id is required when the account has more than one profile; loops work on INDIVIDUAL profiles only. The response's loopUrl opens the loop on dotloop.com. Needs the client scope loop:write. Required: transactionType, status, name.
- **Create a dotloop loop participant** (Create). Add a Loop Participant. Add a new loop participant. Needs the client scope loop:write. Required: profile_id, loop_id, fullName, email, role.
- **Delete a dotloop loop participant by ID** (Delete). Delete a Loop Participant. Delete an existing participant by id. Needs the client scope loop:write. Required: id, profile_id, loop_id.
- **Get single dotloop loop participant by ID** (Get). Get a Loop Participant. Retrieve loop participants details of an individual loop participant. Needs the client scope loop:read. Required: id, profile_id, loop_id.
- **List all dotloop loop participants** (List). List all Loop Participants. List all loop participants in a loop. Needs the client scope loop:read. Required: profile_id, loop_id.
- **Update a dotloop loop participant by ID** (Update). Update a Loop Participant. Update an existing participant. Needs the client scope loop:write. Required: id, profile_id, loop_id.
- **Get single dotloop loop task list by ID** (Get). Get a Loop Task List. Retrieve an individual task list. Needs the client scope loop:read. Required: id, profile_id, loop_id.
- **List all dotloop loop task lists** (List). List all Loop Task Lists. List all task lists in a loop. Needs the client scope loop:read. Required: profile_id, loop_id.
- **Get single dotloop loop task by ID** (Get). Get a Loop Task List item. Retrieve an individual task list item. Needs the client scope loop:read. Required: id, profile_id, loop_id, task_list_id.
- **List all dotloop loop tasks** (List). List all Loop Task List Items. List all task items in a task list. Needs the client scope loop:read. Required: profile_id, loop_id, task_list_id.
- **Get single dotloop loop template by ID** (Get). Retrieve an Individual Loop Template. Retrieve an individual loop template by id. Needs the client scope template:read. Required: id, profile_id.
- **List all dotloop loop templates** (List). List all Loop Templates. List all loop templates in the profile. Needs the client scope template:read. Required: profile_id.
- **Create a dotloop loop** (Create). Create a Loop. Create a new loop. Needs the client scope loop:write. Required: profile_id.
- **Get single dotloop loop by ID** (Get). Get a Loop. Retrieve an individual loop by id. A loop merged into another answers 301 with the new loop's path in Location; the connector follows the redirect. Needs the client scope loop:read. Required: id, profile_id.
- **List all dotloop loops** (List). List all Loops. List all loops associated with a profile. Needs the client scope loop:read. Required: profile_id. The connector pages with batch_size / batch_number (limit sets batch_size, max 100).
- **Update a dotloop loop by ID** (Update). Update a Loop. Update an existing loop by id. Needs the client scope loop:write. Required: id, profile_id.
- **Create a dotloop profile** (Create). Create a Profile. Create a new profile. Needs the client scope profile:write.
- **Get single dotloop profile by ID** (Get). Get a Profile. Retrieve an individual profile by id. Needs the client scope profile:read. Required: id.
- **List all dotloop profiles** (List). List all Profiles. List all profiles associated with the user. Needs the client scope profile:read.
- **Update a dotloop profile by ID** (Update). Update a Profile. Update an existing profile by id. Needs the client scope profile:write. Required: id.
- **Get single dotloop webhook event by ID** (Get). Get an Event. Retrieve an individual event by id. Subscriptions belong to the API client that created them. Required: id, subscription_id.
- **List all dotloop webhook events** (List). List all Events. List all events associated with the subscription. Events are kept 90 days. Subscriptions belong to the API client that created them. Required: subscription_id. The connector pages with next_cursor.
- **Create a dotloop webhook subscription** (Create). Create a Subscription. Create a new subscription. Webhooks are in initial release and enabled for API clients on request. targetType PROFILE takes the event types LOOP_CREATED, LOOP_UPDATED, LOOP_MERGED, LOOP_PARTICIPANT_CREATED, LOOP_PARTICIPANT_UPDATED, LOOP_PARTICIPANT_DELETED; USER takes CONTACT_CREATED, CONTACT_UPDATED, CONTACT_DELETED, PROFILE_UPDATED, USER_PROFILE_ACTIVATED, USER_PROFILE_DEACTIVATED, USER_ADDED_TO_PROFILE, USER_REMOVED_FROM_PROFILE. Subscriptions belong to the API client that created them. Required: targetType, targetId, eventTypes, url.
- **Delete a dotloop webhook subscription by ID** (Delete). Delete a Subscription. Delete an existing subscription by id. Subscriptions belong to the API client that created them. Required: id.
- **Get single dotloop webhook subscription by ID** (Get). Get a Subscription. Retrieve an individual subscription by id. Subscriptions belong to the API client that created them. Required: id.
- **List all dotloop webhook subscriptions** (List). List all Subscriptions. List all subscriptions associated with the current user token. Subscriptions belong to the API client that created them. The connector pages with next_cursor.
- **Update a dotloop webhook subscription by ID** (Update). Update a Subscription. Update an existing subscription by id. Subscriptions belong to the API client that created them. Required: id.
