# Lone Wolf Transact MCP connector

The Lone Wolf Transact connector brings your transaction folders, contacts, documents, offers, and form libraries to Claude, ChatGPT, Cursor, and Microsoft Copilot through one governed endpoint, with every request running as the person who signed in.

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

## Facts

| | |
| --- | --- |
| Application | Lone Wolf Transact |
| Category | CRM |
| AI tools | 49 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| 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 Lone Wolf Transact is connected

- List the offers on the 14 Elm Street transaction folder
- Add the buyer from today's showing as a contact
- Which documents are still missing from the Harper listing folder?

## Connect Lone Wolf Transact in Elaichi

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

1. Open Connections, choose Add connection, and pick Lone Wolf Transact.
2. Optionally set Share with, then press Connect.
3. Paste a Lone Wolf Transact API key. One person generates a token in Lone Wolf Transact and pastes it once. Everyone else works through Share with, and never sees it.

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

## Lone Wolf Transact 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.

## Lone Wolf Transact 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`.

## Lone Wolf Transact 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.

## Lone Wolf Transact 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.

## Lone Wolf Transact 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 Lone Wolf Transact 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 Lone Wolf Transact 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 Lone Wolf Transact through Elaichi

### Catch the transaction up after a showing

Agents. Ask for the folder on a listing, add the buyer as a contact, and update the folder details without opening a second tab.

### See which offers came in on a listing

Transaction coordination. List the offers on a transaction folder, pull up the one the seller asked about, and read its details back in plain language.

### Find the right form in the library

Transaction coordination. Search the form libraries for the disclosure a deal needs and preview a page before anyone fills it in.

### Set up a new transaction folder in seconds

Brokerage ops. Create the folder, attach the parties as contacts, and add the first documents from a single request.

### Check a file for missing documents

Compliance. List what is in a transaction folder, compare it against the office checklist, and flag what still needs to be uploaded.

### Keep contact records clean across deals

Office admin. Look up a client, fix an outdated phone number or email, and remove duplicate contacts in Lone Wolf Transact.

## Elaichi vs Zapier MCP vs Composio for Lone Wolf Transact

All three can connect Lone Wolf Transact 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 Lone Wolf Transact tools | Allow or restrict single Lone Wolf Transact 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 Lone Wolf Transact 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 Lone Wolf Transact to Claude?

Connect Lone Wolf Transact in Elaichi by pasting in your Lone Wolf Transact API key, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Claude asks you to sign in to Elaichi once, and from then on it can work with your transaction folders, contacts, documents, and offers.

### Does Lone Wolf Transact work with ChatGPT and Cursor as well as Claude?

Yes. Lone Wolf Transact is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. There is nothing to set up again for each client.

### What can an AI agent actually do with my Lone Wolf Transact data?

An agent can open a transaction folder in Lone Wolf Transact, list the documents and offers in it, look up or add a contact, create a new folder or document, and find a form in your form libraries. Short, concrete asks such as list the offers on 14 Elm Street work better than a long paragraph of instructions. Deleting a contact, folder, document, or offer is also possible, unless your organization restricts it.

### Does connecting Lone Wolf Transact give the AI every transaction in the office?

No. Every request runs under the Lone Wolf Transact access of the person who signed in, so an agent sees the transaction folders and contacts that person can already see in Lone Wolf Transact, and nothing more. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Lone Wolf Transact itself allows.

### Can my team share one Lone Wolf Transact connection?

Yes. One person connects Lone Wolf Transact in Elaichi with the API key, then shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names who opened a folder or created an offer, not just a shared account.

### Can I stop an agent from deleting or changing things in Lone Wolf Transact?

Yes. Restrictions in Elaichi are set per action, on a role or on one person, so you can let agents read and create in Lone Wolf Transact but stop them deleting folders, documents, contacts, or offers. 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 Lone Wolf Transact connection when someone leaves?

Offboarding someone in Elaichi ends their access to Lone Wolf Transact through every connected client at once. A shared Lone Wolf Transact connection keeps working for everyone else on the team. If you want to remove Lone Wolf Transact entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client.

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

Yes. Lone Wolf Transact 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 Lone Wolf Transact?

Yes. Both let Claude, ChatGPT or Cursor use Lone Wolf Transact. 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 Lone Wolf Transact call.

### How is Elaichi different from Composio for Lone Wolf Transact?

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 Lone Wolf Transact: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 49 Lone Wolf Transact tools

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

- **Create a Lone Wolf Transact access token** (Create). Obtain an access token. The connector calls it on connect and every hour with the saved client ID, secret and Lone Wolf client GUID (no body needed); returns access_token and expires_in.
- **Create a Lone Wolf Transact contact** (Create). Create a contact. Creates a new contact on a transaction for the user specified in the request body. The acting user and transaction go in the body. Required: userId, transactionId.
- **Delete a Lone Wolf Transact contact by ID** (Delete). Delete a contact. Deletes the specified contact. Required: id, userId.
- **Get single Lone Wolf Transact contact by ID** (Get). Get a contact. Returns a single contact by its key. Required: id, userId.
- **List all Lone Wolf Transact contacts** (List). List contacts. Returns the transaction contacts visible to the specified user. Required: userId.
- **Update a Lone Wolf Transact contact by ID** (Update). Update a contact. Applies a partial update to a contact. Only the fields present in the body are modified. Required: id, userId.
- **Get single Lone Wolf Transact document file by ID** (Get). Download a document file. Returns the binary file content of the specified document. Returns the file itself (binary). Required: id, userId.
- **Create a Lone Wolf Transact document** (Create). Upload a document. Uploads a document file to a transaction. The request is sent as `multipart/form-data`. Required: name, file, transactionId, userId.
- **Delete a Lone Wolf Transact document by ID** (Delete). Delete a document. Deletes the specified document. Required: id, userId.
- **Get single Lone Wolf Transact document by ID** (Get). Get a document. Returns a single document's metadata by its key. Required: id, userId.
- **List all Lone Wolf Transact documents** (List). List documents. Returns the documents visible to the specified user. filter / expand are sent as OData $filter / $expand. Required: userId.
- **Create a Lone Wolf Transact folder** (Create). Create a folder. Creates a new folder within a transaction for the user specified in the request body. Required: userId, transactionId, name.
- **Delete a Lone Wolf Transact folder by ID** (Delete). Delete a folder. Deletes the specified folder. Required: id, userId.
- **Get single Lone Wolf Transact folder by ID** (Get). Get a folder. Returns a single folder by its key. Required: id, userId.
- **List all Lone Wolf Transact folders** (List). List folders. Returns the transaction folders visible to the specified user. Required: userId.
- **Update a Lone Wolf Transact folder by ID** (Update). Update a folder. Applies a partial update to a folder. Only the fields present in the body are modified. Required: id, userId.
- **List all Lone Wolf Transact form libraries** (List). List form libraries. Returns the form libraries available to the specified user, including field schema information. Required: userId.
- **Get single Lone Wolf Transact form page image by ID** (Get). Stream a form page image. Streams the rendered image of a single page of a form. Returns the page image (binary). The id is the page number. Required: id, userId, imageId.
- **Get single Lone Wolf Transact library form by ID** (Get). Get a library form. Returns a single form from the specified library. The id is the form id; libId is the library. Required: id, userId, libId.
- **List all Lone Wolf Transact library forms** (List). List library forms. Returns the forms in the specified library. Required: userId, libId.
- **Create a Lone Wolf Transact offer** (Create). Create an offer. Creates a new offer on a transaction for the user specified in the request body. The acting user and transaction go in the body. Required: userId, transactionId.
- **Delete a Lone Wolf Transact offer by ID** (Delete). Delete an offer. Deletes the specified offer. Required: id, userId.
- **Get single Lone Wolf Transact offer by ID** (Get). Get an offer. Returns a single offer by its key. Required: id, userId.
- **List all Lone Wolf Transact offers** (List). List offers. Returns the offers visible to the specified user. Required: userId.
- **Update a Lone Wolf Transact offer by ID** (Update). Update an offer. Applies a partial update to an offer. Only the fields present in the body are modified. Required: id, userId.
- **List all Lone Wolf Transact offices** (List). List offices. Returns the offices belonging to the specified client account. clientId is your Lone Wolf client GUID. Required: clientId.
- **Create a Lone Wolf Transact share group** (Create). Create a share group. Creates a new, empty share group. Use the update endpoint to add members and share opportunities. Required: userId, name.
- **Get single Lone Wolf Transact share group by ID** (Get). Get a share group. Returns a single share group by its key. Use `expand=members` and/or `expand=opportunities` to embed group members and shared opportunities in the response. filter / expand are sent as OData $filter / $expand. Required: id, userId.
- **List all Lone Wolf Transact share groups** (List). List share groups. Returns the share groups visible to the specified user. Supports OData `expand` (e.g. `expand=opportunities`) and `filter`, including lambda expressions such as `filter=opportunities/any(o: o/opportunityId eq &lt;guid&gt;)`. filter / expand are sent as OData $filter / $expand. Required: userId.
- **Update a Lone Wolf Transact share group by ID** (Update). Update a share group (add members and share). Replaces the share group definition, including its member list and the opportunities shared with the group. Required: id, userId.
- **List all Lone Wolf Transact signed documents** (List). List signed documents. Returns the signed documents for the signing. Required: userId, signingId.
- **List all Lone Wolf Transact signing certificates** (List). List signing certificates. Returns the signing certificates for the signing's documents. Required: userId, signingId.
- **List all Lone Wolf Transact signing documents** (List). List original signing documents. Returns the original (unsigned) documents attached to the signing. Required: userId, signingId.
- **Lone Wolf Transact signing participants bulk create** (Create). Add signing participants (batch). Adds multiple participants to a signing in a single request. The `type` field on each participant controls their role (e.g. signer vs. carbon-copy recipient). Required: userId, participants.
- **Get single Lone Wolf Transact signing SSO link by ID** (Get). Get a signing SSO link. Returns a single-sign-on link that opens the specified signing in the Authentisign UI. Required: id, userId.
- **Create a Lone Wolf Transact signing** (Create). Create a signing. Creates a new signing with one or more documents. The request is sent as `multipart/form-data`. Repeat the Files part for several documents. Required: userId, api-version, Name, Files.
- **List all Lone Wolf Transact signings** (List). List signings. Returns the signings belonging to the specified user. Required: userId, api-version.
- **Lone Wolf Transact transaction forms bulk create** (Create). Add forms to a transaction. Adds one or more library forms to the transaction's form package. Required: userId, transactionId, forms.
- **Get single Lone Wolf Transact transaction form by ID** (Get). Get a transaction form PDF. Returns the PDF rendering of a form attached to the transaction. Returns the form as a PDF (binary). Required: id, userId, transactionId.
- **List all Lone Wolf Transact transaction forms** (List). List transaction forms. Returns the forms attached to the specified transaction's form package. Required: userId, transactionId.
- **Update a Lone Wolf Transact transaction form by ID** (Update). Move a form to another folder. Updates the parent folder of a form within the transaction's form package. Moves the form to another folder (parentId). Required: id, userId, transactionId, parentId.
- **Get single Lone Wolf Transact transaction template by ID** (Get). Get a template. Returns a single transaction template by its key. Required: id, userId.
- **List all Lone Wolf Transact transaction templates** (List). List templates. Returns the transaction templates available to the specified user. Required: userId.
- **Create a Lone Wolf Transact transaction** (Create). Create a transaction. Creates a new transaction for the user specified in the request body. The acting user goes in the body (userId). Required: userId.
- **Delete a Lone Wolf Transact transaction by ID** (Delete). Delete a transaction. Deletes the specified transaction. Required: id, userId.
- **Get single Lone Wolf Transact transaction by ID** (Get). Get a transaction. Returns a single transaction by its key. Required: id, userId.
- **List all Lone Wolf Transact transactions** (List). List transactions. Returns the transactions visible to the specified user. Supports OData `filter` (e.g. `filter=opportunityId eq &lt;guid&gt;`). filter / expand are sent as OData $filter / $expand. Required: userId.
- **Update a Lone Wolf Transact transaction by ID** (Update). Update a transaction. Applies a partial update to a transaction. Only the fields present in the body are modified. Required: id, userId.
- **List all Lone Wolf Transact users** (List). List users. Returns the users belonging to the specified client account. clientId is your Lone Wolf client GUID; the users' ids are the userId every other call takes. Required: clientId.
