Skip to content

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.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

List transactions closing this month and their offices

Working in Lone Wolf Back Office with Elaichi

  • Get single Lone Wolf Back Office business contact by ID
  • List all Lone Wolf Back Office classifications
  • Get single Lone Wolf Back Office commission by ID
Ask anything…
Governance / Audit log Last 24 hours
Lone Wolf Back Office Get single Lone Wolf Back Office commission by ID Emily Carter · Claude · 9:41 AM Done
Lone Wolf Back Office List all Lone Wolf Back Office classifications Emily Carter · Claude · 9:41 AM Done
Lone Wolf Back Office Get single Lone Wolf Back Office business contact by ID Emily Carter · Claude · 9:41 AM Done
Lone Wolf Back Office Create a Lone Wolf Back Office access token Megan Brooks · ChatGPT · 9:38 AM Done
Lone Wolf Back Office List all Lone Wolf Back Office condition types Ryan Hayes · Cursor · 9:35 AM Done

How to connect Lone Wolf Back Office to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Lone Wolf Back Office MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ 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

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 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

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Lone Wolf Back Office MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

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

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

What teams do with Lone Wolf Back Office through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lone Wolf Back Office is logged.

  • Accounting

    Check a commission before cutting the check

    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.

  • Transaction coordination

    Start a transaction once a deal is signed

    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.

  • Office management

    See every transaction an office has open

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

  • Finance

    Confirm a deposit landed in trust

    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.

  • Brokerage operations

    Find an agent's office and employee record

    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.

  • Leadership

    Ask which sources of business close most

    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.

Try asking

  • “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?”

See all 19 Lone Wolf Back Office tools →

What connecting Lone Wolf Back Office gets you

6 screens from Elaichi, each doing one job for your Lone Wolf Back Office account.

Elaichi Agent

Ask Elaichi to work across your apps.

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?

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about transactions and commissions in plain language.

Elaichi's agent answers from live Lone Wolf Back Office records, no report to run.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint reaches Lone Wolf Back Office everywhere.

Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
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.

Tool catalog

19 Lone Wolf Back Office tools, no code.

Transactions, commissions, deposits, employees and offices, ready the moment the connector is on.

ElaichiToolboxes
Name Source template Tools Created

Accounting toolbox

Lone Wolf Back Office · commissions and deposits

Lone Wolf Back Office starter 18 Mar 4, 2026

Transaction coordination toolbox

Lone Wolf Back Office · transactions and condition types

— 9 Mar 2, 2026

Office management toolbox

Lone Wolf Back Office · offices and employees

— 24 Feb 27, 2026

Finance toolbox

Lone Wolf Back Office · deposits and classifications

Lone Wolf Back Office starter 6 Feb 19, 2026

Agent services toolbox

Lone Wolf Back Office · external agents and business contacts

— 31 Jan 30, 2026

Leadership toolbox

Lone Wolf Back Office · transactions and sources of business

— 12 Jan 22, 2026

Toolboxes

Every team gets its own toolbox.

Accounting sees commissions and deposits, coordinators see transactions, each scoped to that team.

ElaichiConnections
Connection Scope Status Access
LO

Lone Wolf Back Office (Accounting)

Connected by Emily Carter

Personal • Active 1 team · 6 members
LO

Lone Wolf Back Office (Downtown office)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
LO

Lone Wolf Back Office (Coastal office)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
LO

Lone Wolf Back Office (Transaction desk)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
LO

Lone Wolf Back Office (Finance)

Connected by Ryan Hayes

Personal • Active Not shared
LO

Lone Wolf Back Office (Broker leadership)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share the connection, never the API key.

One person connects Lone Wolf Back Office and teammates work through it without seeing a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Lone Wolf Back Office Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Lone Wolf Back Office Transactions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Lone Wolf Back Office Transactions List Toolbox

Audit log

Know who touched every transaction.

Each call records when, who, what happened and which Lone Wolf Back Office record.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Lone Wolf Back Office digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch transactions

    Lone Wolf Back Office

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Lone Wolf Back Office

    Queued

Workflows

A schedule starts the transaction digest itself.

Lone Wolf Back Office transactions are fetched, grouped, drafted, approved by a person, then posted back.

Lone Wolf Back Office health

Refreshed 4 minutes ago · every 15 minutes · from the transactions collection

Live

Transactions

1,284 ↓ 12%

Commissions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Transactions created

Last 14 days

By team

Share of activity

Accounting 34%

Downtown office 27%

Coastal office 21%

Transaction desk 18%

Collections and dashboards

Transaction volume, computed without a model.

Four metrics, 14 days of transactions created and a breakdown by team, refreshed on schedule.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Lone Wolf Back Office, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Lone Wolf Back Office tools for your AI agents

19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lone Wolf Back Office, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

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.

Put Lone Wolf Back Office in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot