# HawkSoft MCP connector

Connect HawkSoft to Elaichi and your team can search clients, add new ones, write log notes and record receipts from Claude, ChatGPT, Cursor or Microsoft Copilot, each person inside their own access, every action logged.

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

## Facts

| | |
| --- | --- |
| Application | HawkSoft |
| Category | CRM |
| AI tools | 10 |
| 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 HawkSoft is connected

- Which HawkSoft clients changed this week?
- Add a log note to the Ramirez client about today's call
- Create a receipt for the Nguyen family's renewal payment

## Connect HawkSoft in Elaichi

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

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

## HawkSoft 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.

## HawkSoft 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`.

## HawkSoft 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.

## HawkSoft 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.

## HawkSoft 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 HawkSoft 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 HawkSoft 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 HawkSoft through Elaichi

### Set up a new client after a quote

Sales. A producer closes a call and asks Claude to create the client in HawkSoft with the name, contact details and office from their notes. The file exists before the next call starts.

### Catch the client file up after a call

Service. An account manager finishes a coverage question and dictates a log note straight onto the HawkSoft client. No switching windows, no note left for later.

### Record a premium payment as a receipt

Accounting. When a client pays at the counter or by phone, the receipt is created in HawkSoft from a one line ask, tied to the right client.

### See which clients changed this week

Operations. An operations lead asks for every HawkSoft client that changed since Monday and gets the list to review for missing notes or follow ups.

### Get a picture across agencies and offices

Leadership. An owner asks which agencies, offices and users are set up in HawkSoft and who sits where, without opening an admin screen.

### Find a client before they finish the sentence

Front desk. A walk in gives a last name and the front desk pulls the HawkSoft client file by name, phone or ID in the same breath.

## Elaichi vs Zapier MCP vs Composio for HawkSoft

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

Connect HawkSoft in Elaichi by pasting the API key from your HawkSoft account, 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. The whole thing takes a few minutes.

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

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

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

With HawkSoft connected, an agent can look up a client by name or ID, pull a batch of client files, list which clients changed recently, create a new client, add a log note to a client and record a receipt. It can also list your agencies, offices and users. Short, concrete asks such as "add a log note to the Ramirez client" work better than long paragraphs.

### Does connecting HawkSoft give the AI access to every client in the agency?

No. Each person signs in to Elaichi as themselves, so anything an agent does in HawkSoft runs inside that person's own access and nothing more. Elaichi can narrow what a role or an individual is allowed to do with HawkSoft, and it can never widen it beyond what HawkSoft already permits.

### Can my team share one HawkSoft connection?

Yes. One person connects HawkSoft in Elaichi and shares the connection with a team, and nobody else ever handles the HawkSoft API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created a client or posted a receipt, not the account that connected it.

### Can I stop an agent from creating or changing things in HawkSoft?

Yes. Restrictions in Elaichi work per action, so you can stop creating clients, log notes or receipts in HawkSoft for a role or for one person while leaving lookups alone. 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 HawkSoft connection when someone leaves?

Offboarding a person in Elaichi ends their access to HawkSoft through every client at once. If they were working through a shared HawkSoft connection, it keeps working for everyone else on the team. If you ever want HawkSoft gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

Yes. HawkSoft 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 HawkSoft?

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

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

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

## All 10 HawkSoft tools

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

- **List all HawkSoft agencies** (List). GET Agencies: Returns all agencies that have subscribed to the partner's application, with the data scopes each agency enabled.
- **List all HawkSoft changed clients** (List). GET Changed Clients: Get a list of clients changed since a date. These Client IDs can be used when calling the Get Client or Get Client List endpoints. Call it without asOf the first time to get every client ID.
- **HawkSoft clients bulk get** (Get). GET Client List: Read clients in batches of up to 200 (the client numbers from GET Changed Clients). Supports Client Includes. A POST that reads (HawkSoft's 'GET Client List'): send clientNumbers (up to 200). Required: clientNumbers.
- **Create a HawkSoft client** (Create). POST Create Client: Create a new client in the specified agency. Rate limit: 25 requests per second (429 beyond it). With BusinessDetail the client is a Commercial customer, otherwise Personal. Required: log, people.
- **Get single HawkSoft client by ID** (Get). GET Client: Read one client (see the Client model reference). Supports Client Includes. Required: id.
- **HawkSoft clients search** (Search). GET Client Search: Search an agency's clients. Currently the only supported search criteria is Policy Number. Supports Client Includes. Returns an empty list when nothing matches. Required: policyNumber.
- **Create a HawkSoft log note** (Create). POST Log Note: Create a log note (and optionally a task) on a client. HawkSoft answers with a text message: HTTP 200 'The log was created successfully.', or 202 'The request was saved and the log will be created next time the agency is connected to the cloud.' (MCP clients get it as a text-file note, not inline). Required: client_number, channel, note, refId, ts.
- **List all HawkSoft offices** (List). GET Agency Offices: Returns a list of offices defined for the agency ID.
- **Create a HawkSoft receipt** (Create). POST Create Receipts: Record a payment received by a client. A log note will be created and linked to the receipt. An optional task may be created and assigned to an agent for review. The body is a JSON array of one or more receipts. Send the receipts as items (HawkSoft's body is the JSON array itself). The response has a result per receipt (refId, code, message); when every receipt failed, the connector returns the first failure as an error. Required: client_number, items.
- **List all HawkSoft users** (List). GET Agency Users: Retrieve the agency's user list (active users only), e.g. to identify users for task assignment.
