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.
- Connects over OAuth
- Free 14-day trial
- No credit card
List every active activity in BQE CORE
Working in BQE CORE with Elaichi
-
List all BQE CORE accounts
-
Get single BQE CORE account by ID
-
List all BQE CORE activities
How to connect BQE CORE to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
BQE CORE MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
BQE CORE MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
BQE CORE MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- 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 BQE CORE to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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 BQE CORE through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in BQE CORE is logged.
-
Finance
Keep the chart of accounts tidy
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.
-
Accounting
Set up new accounts in one go
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.
-
Project management
See who is allocated to what
Ask which staff are allocated to a project this month and shift hours between people as the plan changes, straight from the chat window.
-
Operations
Add activities for a new service line
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.
-
HR
Review benefits without the spreadsheet
List the benefits set up in BQE CORE, confirm a new hire's benefit is in place, and add the one that is missing.
-
Leadership
Get a plain answer about staffing
Ask how a team's allocations are spread across projects and get a summary from live BQE CORE records before the Monday meeting.
Try asking
- “List every active activity in BQE CORE”
- “Who is allocated to the Harbor Street project this month?”
- “Create a new account called Software subscriptions”
What connecting BQE CORE gets you
6 screens from Elaichi, each doing one job for your BQE CORE account.
Ask Elaichi to work across your apps.
List every active activity in BQE CORE
Who is allocated to the Harbor Street project this month?
Create a new account called Software subscriptions
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about allocations in plain language.
Elaichi's agent reads live BQE CORE accounts, activities and allocations and answers in plain words.
Copy the endpoint
AI apps
BQE CORE works in every MCP client.
One governed endpoint for Claude, ChatGPT and Cursor, with no SDK and no shared API key.
Tool catalog
599 BQE CORE tools, no code needed.
Accounts, activities, allocations and benefits, every resource and method, ready without custom code.
Toolboxes
Every team gets its own BQE CORE toolbox.
Finance, HR and project managers each work from a toolbox scoped to their team.
Shared connections
Share BQE CORE without sharing a credential.
One person connects BQE CORE, teammates work through it, and nobody else sees a secret.
Audit log
Every BQE CORE change names who did it.
The audit log records when, who, what happened and which account or allocation was touched.
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.
BQE CORE digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
BQE CORE
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
BQE CORE
Queued
Workflows
A schedule starts the work in BQE CORE.
Allocations are fetched, grouped and drafted into a digest, approved by a person, then posted back.
BQE CORE health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Activities
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Finance 34%
Accounting 27%
Project managers 21%
HR 18%
Collections and dashboards
BQE CORE numbers, refreshed without asking.
Four metrics, fourteen days of accounts created and a split by team, computed with no model.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
BQE CORE tools for your AI agents
599 tools are ready to call through Elaichi's MCP endpoint the moment you connect BQE CORE, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 316 of 599 BQE CORE tools here. Connect BQE CORE and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
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 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.
Put BQE CORE 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