# Lone Wolf Back Office MCP connector

The Lone Wolf Back Office connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent look up transactions, commissions, deposits, employees and offices, and open new transactions, with each person signed in as themselves.

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

## Facts

| | |
| --- | --- |
| Application | Lone Wolf Back Office |
| Category | Accounting |
| AI tools | 19 |
| 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 Back Office is connected

- List transactions closing this month and their offices
- Show me commission 48213 and how it is split
- Which sources of business brought in the most transactions this quarter?

## Connect Lone Wolf Back Office in Elaichi

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

1. Open Connections, choose Add connection, and pick Lone Wolf Back Office.
2. Optionally set Share with, then press Connect.
3. Paste a Lone Wolf Back Office API key. One person generates a token in Lone Wolf Back Office 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 Back Office tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

### Check a commission before cutting the check

Accounting. Pull up a commission by its number in Lone Wolf Back Office and confirm the split, the office and the agent before anything is paid out.

### Start a transaction once a deal is signed

Transaction coordination. Open a new transaction in Lone Wolf Back Office right after the contract comes in, with the right office, property type and source of business already set.

### See every transaction an office has open

Office management. List the transactions tied to one office and ask which ones are still waiting on conditions, without logging in and paging through screens.

### Confirm a deposit landed in trust

Finance. Look up a deposit by its number and check the amount and the transaction it belongs to while the agent is still on the phone.

### Find an agent's office and employee record

Brokerage operations. Ask which office an agent works out of and pull their employee record in Lone Wolf Back Office, or look up an outside agent on a co-op deal.

### Ask which sources of business close most

Leadership. Have the agent list recent transactions and group them by source of business or property type, so the answer arrives as a summary instead of a spreadsheet.

## Elaichi vs Zapier MCP vs Composio for Lone Wolf Back Office

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

Connect Lone Wolf Back Office in Elaichi by pasting in the API key from your Lone Wolf Back Office account, which is the only sign-in step; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi as yourself, and from then on it can work with your transactions, commissions and deposits.

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

Yes. Once Lone Wolf Back Office 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 Lone Wolf Back Office once and every client picks it up.

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

An agent can pull up a transaction, commission or deposit by its number, list transactions, employees and offices, and read the brokerage's own lists of property types, sources of business, classifications and condition types in Lone Wolf Back Office. It can also open a new transaction when a deal goes under contract. Short, concrete asks work best, such as asking for one commission by number rather than typing a long paragraph.

### Does connecting Lone Wolf Back Office give the AI access to every office and transaction?

No. Everything an agent does in Lone Wolf Back Office runs under the account that was connected and the person who signed in to Elaichi, so it sees the offices, transactions and commissions that access allows and nothing more. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Lone Wolf Back Office already permits.

### Can my team share one Lone Wolf Back Office connection?

Yes. One person connects Lone Wolf Back Office in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every lookup and every new transaction.

### Can I stop an agent from creating or changing things in Lone Wolf Back Office?

Yes. In Elaichi you can restrict opening new transactions in Lone Wolf Back Office, or any other action, for a role or for one person, while leaving lookups of commissions and deposits 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 Lone Wolf Back Office connection when someone leaves?

When someone is offboarded in Elaichi, their access to Lone Wolf Back Office through every client ends at once. A shared Lone Wolf Back Office connection keeps working for everyone else on the team. If you disconnect Lone Wolf Back Office once in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

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

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

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

### How is Elaichi different from Composio for Lone Wolf Back Office?

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

## All 19 Lone Wolf Back Office tools

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

- **Create a Lone Wolf Back Office access token** (Create). Obtain an access token. Exchanges the connection's OAuth client credentials for a JWT access token (Lone Wolf's /oauth/token, documented with the Transact API). 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.
- **Get single Lone Wolf Back Office business contact by ID** (Get). Get business contact details. Required: id.
- **List all Lone Wolf Back Office classifications** (List). List all classifications.
- **Get single Lone Wolf Back Office commission by ID** (Get). Get commission details. Required: id.
- **List all Lone Wolf Back Office condition types** (List). List all condition types.
- **List all Lone Wolf Back Office contact types** (List). List all contact types.
- **Get single Lone Wolf Back Office deposit by ID** (Get). Get deposit details. Required: id.
- **Get single Lone Wolf Back Office employee by ID** (Get). Get employee details. Required: id.
- **List all Lone Wolf Back Office employees** (List). List all employees. The connector pages with limit / offset (limit sets the page size, max 100).
- **Get single Lone Wolf Back Office external agent by ID** (Get). Get external agent details. Required: id.
- **Get single Lone Wolf Back Office feature by ID** (Get). Get feature details. Required: id.
- **List all Lone Wolf Back Office features** (List). List all features.
- **Get single Lone Wolf Back Office office by ID** (Get). Get office details. Required: id.
- **List all Lone Wolf Back Office offices** (List). List all offices. The connector pages with limit / offset (limit sets the page size, max 100).
- **List all Lone Wolf Back Office property types** (List). List all property types.
- **List all Lone Wolf Back Office sources of business** (List). List all sources of business.
- **Create a Lone Wolf Back Office transaction** (Create). Create a new transaction.
- **Get single Lone Wolf Back Office transaction by ID** (Get). Get transaction details. Required: id.
- **List all Lone Wolf Back Office transactions** (List). List all transactions. Filter by startDate / endDate. The connector pages with limit / offset (limit sets the page size, max 100).
