Linq MCP connector
The Linq connector brings your Linq chats, messages, participants, attachments and phone numbers to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can read, send and tidy up conversations in plain language, inside each person's own Linq access.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize the Linq chats my team opened this week.
Working in Linq with Elaichi
-
List all Linq chats
-
Get single Linq chat by ID
-
Get single Linq message by ID
How to connect Linq to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Linq 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.
Linq 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.
Linq 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.
Linq 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.
Linq 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 Linq 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 Linq through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Linq is logged.
-
Sales
Catch up on a prospect's chat before a call
Ask for the latest Linq chat with a prospect and get the thread summarized, including any attachments they sent, so you walk into the call knowing where things stand.
-
Sales
Send a follow-up text from your notes
Dictate the gist of a follow-up and have it drafted and sent as a Linq message to the right chat, with your contact card shared alongside it when the person is new.
-
Support
Find every open chat waiting on a reply
Pull up Linq chats where the customer spoke last, mark the ones you have handled as read, and work through the rest in order.
-
Support
Add a specialist to a customer chat
When a question needs a colleague, add them as a participant in the Linq chat and post a short message bringing them up to speed, then remove them once it is resolved.
-
Customer success
Fix a message sent with a mistake
Correct a typo or a wrong date in a Linq message you already sent, or delete an attachment that went to the wrong chat, without hunting through the app.
-
Operations
Keep the team's phone numbers straight
List every Linq phone number in the organization, see which ones are in use, and update the details on a number when a rep changes territory or role.
Try asking
- “Summarize the Linq chats my team opened this week.”
- “Which Linq messages are still unread by participants?”
- “Draft a reply on the newest Linq chat thread.”
What connecting Linq gets you
6 screens from Elaichi, each doing one job for your Linq account.
Ask Elaichi to work across your apps.
Summarize the Linq chats my team opened this week.
Which Linq messages are still unread by participants?
Draft a reply on the newest Linq chat thread.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Linq chats, get real answers.
Plain language questions run against live Linq chats, messages and participants.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Linq together.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
41 Linq tools arrive ready to call.
Chats, messages, participants and contact cards are covered without custom code.
Toolboxes
Every team gets its own Linq toolbox.
Support, Sales and Ops each see the Linq tools their work needs.
Shared connections
Teammates use Linq without seeing credentials.
See who connected each Linq account and how many teams and members share it.
Audit log
Every Linq call is written down.
When, who, what happened, type and resource for each chat and message 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. Automations, collections and live dashboards come with the Black plan.
Linq digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch chats
Linq
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
Linq
Queued
Automations
A schedule fires and Linq work finishes.
Linq chats are fetched, grouped, drafted into a digest, approved, then posted back.
Linq health
Refreshed 4 minutes ago · every 15 minutes · from the chats collection
Chats
1,284 ↓ 12%
Messages
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Chats created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support APAC 27%
Sales 21%
Customer Success 18%
Collections and dashboards
Linq health reports itself on schedule.
Four metrics, 14 days of Linq chats created and a team breakdown, computed directly.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Linq
All three can connect Linq 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 Linq tools | Allow or restrict single Linq 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 Linq 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.
Linq tools for your AI agents
41 tools are ready to call through Elaichi's MCP endpoint the moment you connect Linq, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Linq to Claude?
First connect Linq in Elaichi. Linq connects with an API key, so you paste the key from your Linq account into Elaichi, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on Linq chats and messages are available in your conversations.
Does Linq work with ChatGPT and Cursor as well as Claude?
Yes. Once Linq 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 Linq once and every client you use picks it up.
What can an AI agent actually do with my Linq data?
An agent can list your Linq chats, open a specific chat or message, summarize a thread, send a new message, edit or delete one you already sent, add or remove participants, share a contact card, add an attachment or voice memo, and mark a chat as read. It can also list the phone numbers in your Linq account and update the details on one. Because Linq offers many actions, short concrete asks like "send this to the chat with Dana" work better than long multi-part instructions.
Does connecting Linq give the AI access to every chat in the workspace?
No. Every request runs inside the Linq access of the person who signed in, so the agent sees the chats, messages and phone numbers that person can already see in Linq and nothing more. Elaichi can narrow that further, for example restricting deletes for a role, but it can never widen access beyond what Linq itself allows that person.
Can I stop an agent from deleting or changing things in Linq?
Yes. Restrictions in Elaichi work per action, so you can allow reading Linq chats and sending messages while restricting deleting messages, removing participants or editing phone numbers. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
What happens to a Linq connection when someone leaves?
When you offboard someone in Elaichi, their access to Linq through every client ends at once, and the append-only audit log keeps a record of what they did while they had it. If they had shared a Linq connection with a team, it keeps working for everyone else. Disconnecting Linq once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Linq MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Linq 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 Linq?
Yes. Both let Claude, ChatGPT or Cursor use Linq. 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 Linq call.
How is Elaichi different from Composio for Linq?
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 Linq: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Linq 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