# BQE CORE MCP connector

Connect BQE CORE to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can read and update your accounts, activities, allocations and benefits, with each person signed in as themselves and every call logged.

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

## Facts

| | |
| --- | --- |
| Application | BQE CORE |
| Category | Accounting |
| AI tools | 599 |
| 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 BQE CORE is connected

- List every active activity in BQE CORE
- Who is allocated to the Harbor Street project this month?
- Create a new account called Software subscriptions

## Connect BQE CORE in Elaichi

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

1. Open Connections, choose Add connection, and pick BQE CORE.
2. Optionally set Share with, then press Connect.
3. Supply your own BQE CORE app, then approve. BQE CORE 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 BQE CORE tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## BQE CORE 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.

## BQE CORE 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`.

## BQE CORE 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.

## BQE CORE 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.

## BQE CORE 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 BQE CORE 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 BQE CORE 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 BQE CORE through Elaichi

### Keep the chart of accounts tidy

Finance. Ask for every account in BQE CORE, spot the duplicates and the ones nobody has posted to, then rename or retire them without clicking through each one.

### Set up new accounts in one go

Accounting. Hand over a list of new general ledger accounts and have them created in BQE CORE in a single batch, then check that each one landed correctly.

### See who is allocated to what

Project management. Ask which staff are allocated to a project this month and shift hours between people as the plan changes, straight from the chat window.

### Add activities for a new service line

Operations. When the firm starts offering a new service, create the activities in BQE CORE and update the existing ones so time is coded correctly from day one.

### Review benefits without the spreadsheet

HR. List the benefits set up in BQE CORE, confirm a new hire's benefit is in place, and add the one that is missing.

### Get a plain answer about staffing

Leadership. Ask how a team's allocations are spread across projects and get a summary from live BQE CORE records before the Monday meeting.

## Elaichi vs Zapier MCP vs Composio for BQE CORE

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

Two steps. First, connect BQE CORE in Elaichi: BQE CORE asks you to register an OAuth application inside BQE CORE itself, so one administrator brings that client ID and secret once, and everyone after that simply signs in to BQE CORE with their own login. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and BQE CORE is ready to use.

### Does BQE CORE work with ChatGPT and Cursor as well as Claude?

Yes. Once BQE CORE 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 BQE CORE once and every client picks it up.

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

It can look up, create and update the records in BQE CORE: accounts, activities, allocations and benefits. Ask for every account of a certain type, add a batch of new activities, change an allocation, or pull up a benefit by name. Rather than a long list of actions, Claude gets a search and a run, so short, concrete asks like list the active activities work better than long paragraphs.

### Does connecting BQE CORE give the AI everything in my firm's books?

No. Every call runs inside the BQE CORE access of the person who signed in, so an agent sees the accounts, allocations and benefits that person can already see in BQE CORE and nothing more. Elaichi can narrow that further with roles and restrictions, and it can never widen it.

### Can my team share one BQE CORE connection?

Yes. One person connects BQE CORE in Elaichi and shares the connection with a team, so nobody else needs the client ID, the secret, or any other credential. Each teammate still signs in as themselves, so the audit log names the person behind every change in BQE CORE.

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

Yes. Restrictions in Elaichi work per action, so you can restrict deleting accounts or changing allocations in BQE CORE for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a BQE CORE connection when someone leaves?

Offboard the person in Elaichi and their access to BQE CORE through every client ends at once. A shared BQE CORE connection keeps working for everyone else on the team. If you ever want BQE CORE gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

Yes. BQE CORE 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 BQE CORE?

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

### How is Elaichi different from Composio for BQE CORE?

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

## All 599 BQE CORE tools

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

- **List all BQE CORE accounts** (List). Use this method to retrieve a list of accounts. You can optionally pass where, orderBy, and page as query parameters to filter the result. Use the fields parameter to request a subset of the model. By default, a complete model is returned. The connector pages through all results (page=&lt;number&gt;,&lt;size&gt;; up to 1000 per page, 100 with expand).
- **Get single BQE CORE account by ID** (Get). Use this method to retrieve a specific account. Pass id as the parameter. Required: id.
- **Create a BQE CORE account** (Create). Use this method to save an account. Pass account as the parameter. Required: code, name, type.
- **BQE CORE accounts bulk create** (Create). Use this method to save multiple accounts. Pass model as the parameter.
- **Update a BQE CORE account by ID** (Update). Use this method to update an account. Pass id and account as the parameters. Required: id, code, name, type.
- **Delete a BQE CORE account by ID** (Delete). Use this method to delete an account. Pass id as the parameter. Required: id.
- **BQE CORE accounts partial update** (Update). Use this method to perform partial modifications to an account. Pass id and patch document as parameters. Required: account_id, version. Body: {"version": "&lt;the record's version&gt;", "Document": [{"op": "replace", "path": "/name", "value": "..."}]}.
- **List all BQE CORE activities** (List). Use this method to retrieve a list of activities. Optionally pass where, orderBy and page as the query parameters to filter the result. The fields parameter is used to request a flat subset of the model and the expand parameter is used to request nested properties in the model. The connector pages through all results (page=&lt;number&gt;,&lt;size&gt;; up to 1000 per page, 100 with expand).
- **Get single BQE CORE activity by ID** (Get). Use this method to retrieve a specific activity. Pass id as the parameter. Required: id.
- **Create a BQE CORE activity** (Create). Use this method to save an activity. Pass activity as the parameter. Required: code, description.
- **BQE CORE activities bulk create** (Create). Use this method to save multiple activity. Pass model as the parameter.
- **Update a BQE CORE activity by ID** (Update). Use this method to update an activity. Pass id and activity as the parameters. Required: id, code, description.
- **Delete a BQE CORE activity by ID** (Delete). Use this method to delete an activity. Pass id as the parameter. Required: id.
- **BQE CORE activities partial update** (Update). Use this method to perform partial modifications to an activity. Pass id and patch document as parameters. Required: activity_id, version. Body: {"version": "&lt;the record's version&gt;", "Document": [{"op": "replace", "path": "/name", "value": "..."}]}.
- **List all BQE CORE allocations** (List). Use this method to retrieve a list of allocations. Optionally pass where, orderBy and page as the query parameters to filter the result. Use the fields parameter to request a subset of the model. By default, a complete model is returned. The connector pages through all results (page=&lt;number&gt;,&lt;size&gt;; up to 1000 per page, 100 with expand).
- **Get single BQE CORE allocation by ID** (Get). Use this method to retrieve a specific allocation. Pass id as the parameter. Required: id.
- **Create a BQE CORE allocation** (Create). Use this method to save an allocation. Pass allocation as the parameter. Required: itemId, itemType, projectId, resourceType, startsOn, units.
- **BQE CORE allocations bulk create** (Create). Use this method to save multiple allocation. Pass model as the parameter.
- **Update a BQE CORE allocation by ID** (Update). Use this method to update an allocation. Pass id and allocation as parameters. Required: id, itemId, itemType, projectId, resourceType, startsOn, units.
- **Delete a BQE CORE allocation by ID** (Delete). Use this method to delete an allocation. Pass id as the parameter. Required: id.
- **BQE CORE allocations partial update** (Update). Use this method to perform partial modifications to an allocation. Pass id and patch document as parameters. Required: allocation_id, version. Body: {"version": "&lt;the record's version&gt;", "Document": [{"op": "replace", "path": "/name", "value": "..."}]}.
- **List all BQE CORE benefits** (List). Use this method to retrieve a list of benefits. You can optionally pass where, orderBy, and page as query parameters to filter the result. Use the fields parameter to request a subset of the model. By default, a complete model is returned. The connector pages through all results (page=&lt;number&gt;,&lt;size&gt;; up to 1000 per page, 100 with expand).
- **Get single BQE CORE benefit by ID** (Get). Use this method to retrieve a specific benefit. Pass id as the parameter. Required: id.
- **Create a BQE CORE benefit** (Create). Use this method to save a benefit. Pass benefit as the parameter. Required: name.
- **BQE CORE benefits bulk create** (Create). Use this method to save multiple benefits. Pass model as the parameter.
- **Update a BQE CORE benefit by ID** (Update). Use this method to update a benefit. Pass id and benefit as the parameters. Required: id, name.
- **Delete a BQE CORE benefit by ID** (Delete). Use this method to delete a specific benefit. Pass id as the parameter. Required: id.
- **BQE CORE benefits partial update** (Update). Use this method to perform partial modifications to a benefit. Pass id and patch document as parameters. Required: benefit_id, version. Body: {"version": "&lt;the record's version&gt;", "Document": [{"op": "replace", "path": "/name", "value": "..."}]}.
- **List all BQE CORE billing schedules** (List). Use this method to retrieve a list of billing schedules. Optionally pass where, orderBy and page as the query parameters to filter the result. Use the fields parameter to request a subset of the model. By default, a complete model is returned. The connector pages through all results (page=&lt;number&gt;,&lt;size&gt;; up to 1000 per page, 100 with expand).
- **Get single BQE CORE billing schedule by ID** (Get). Use this method to retrieve a specific billing schedule. Pass id as the parameter. Required: id.
- **Create a BQE CORE billing schedule** (Create). Use this method to save a billing schedule. Pass billing schedule as the parameter. Required: amount, projectId.
- **BQE CORE billing schedules bulk create** (Create). Use this method to save multiple billing schedule. Pass model as the parameter.
- **Update a BQE CORE billing schedule by ID** (Update). Use this method to update a billing schedule. Pass id and billing schedule as parameters. Required: id, amount, projectId.
- **Delete a BQE CORE billing schedule by ID** (Delete). Use this method to delete a billing schedule. Pass id as the parameter. Required: id.
- **BQE CORE billing schedules partial update** (Update). Use this method to perform partial modifications to a billing schedule. Pass id and patch document as parameters. Required: billing_schedule_id, version. Body: {"version": "&lt;the record's version&gt;", "Document": [{"op": "replace", "path": "/name", "value": "..."}]}.
- **List all BQE CORE bills** (List). Use this method to retrieve a list of bills. You can optionally pass where, orderBy, and page as query parameters to filter the result. Use the fields parameter to request a subset of the model. By default, a complete model is returned. The connector pages through all results (page=&lt;number&gt;,&lt;size&gt;; up to 1000 per page, 100 with expand).
- **Get single BQE CORE bill by ID** (Get). Use this method to retrieve a specific bill. Pass id as the parameter. Required: id.
- **Create a BQE CORE bill** (Create). Use this method to save a bill. Pass bill as the parameter. Required: date, number, vendorId.
- **BQE CORE bills bulk create** (Create). Use this method to save multiple bill. Pass model as the parameter.
- **Update a BQE CORE bill by ID** (Update). Use this method to update a bill. Pass id and bill as the parameters. Required: id, date, number, vendorId.
- **Delete a BQE CORE bill by ID** (Delete). Use this method to delete a bill. Pass id as the parameter. Required: id.
- **BQE CORE bills partial update** (Update). Use this method to perform partial modifications to a bill. Pass id and patch document as parameters. Required: bill_id, version. Body: {"version": "&lt;the record's version&gt;", "Document": [{"op": "replace", "path": "/name", "value": "..."}]}.
- **List all BQE CORE budgets** (List). Use this method to list the budgets. Optionally pass where, orderBy and page as the query parameters to filter the result. Use the fields parameter to request a subset of the model. By default, a complete model is returned. The connector pages through all results (page=&lt;number&gt;,&lt;size&gt;; up to 1000 per page, 100 with expand).
- **Get single BQE CORE budget by ID** (Get). Use this method to retrieve a specific budget. Pass id as the parameter. Required: id.
- **Create a BQE CORE budget** (Create). Use this method to save a budget. Pass budget as the parameter. Required: name.
- **BQE CORE budgets bulk create** (Create). Use this method to save multiple budgets. Pass model as the parameter.
- **Update a BQE CORE budget by ID** (Update). Use this method to update a budget. Pass id and budget as the parameters. Required: id, name.
- **Delete a BQE CORE budget by ID** (Delete). Use this method to delete a budget. Pass id as the parameter. Required: id.
- **BQE CORE budgets partial update** (Update). Use this method to perform partial modifications to a budget. Pass id and patch document as parameters. Required: budget_id, version. Body: {"version": "&lt;the record's version&gt;", "Document": [{"op": "replace", "path": "/name", "value": "..."}]}.
- **List all BQE CORE campaign status** (List). Use this method to retrieve a list of campaign status. You can optionally pass where, orderBy, and page as query parameters to filter the result. Use the fields parameter to request a subset of the model. By default, a complete model is returned. The connector pages through all results (page=&lt;number&gt;,&lt;size&gt;; up to 1000 per page, 100 with expand).
- ...and 549 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
