Ticketing
Linq MCP connector
The Linq connector brings your Linq chats, messages, participants, attachments and phone numbers to Claude, ChatGPT, Cursor and any MCP client, so your team can read, send and tidy up conversations in plain language, inside each person's own Linq access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Linq to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Linq once
-
Open Connections, choose Add connection, and pick Linq.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Linq API key. One person generates a token in Linq and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Linq to 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.
Connect Linq to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect Linq to 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.
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.
Use cases
What teams do with Linq through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Linq gets you
6 screens from the product, each doing one job for your Linq account.
The agent
Ask about Linq chats, get real answers.
Plain language questions run against live Linq chats, messages and participants.
- chats
- messages
- participants
- contact cards
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Linq together.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
41 Linq tools arrive ready to call.
Chats, messages, participants and contact cards are covered without custom code.
- List all Linq chats
- Create a Linq chat
- Get single Linq chat by ID
- Update a Linq chat by ID
Toolboxes
Every team gets its own Linq toolbox.
Support, Sales and Ops each see the Linq tools their work needs.
- Support
- Sales
- Customer Success
- Operations
Shared connections
Teammates use Linq without seeing credentials.
See who connected each Linq account and how many teams and members share it.
- Support EMEA
- Support APAC
- Sales
- Customer Success
Audit log
Every Linq call is written down.
When, who, what happened, type and resource for each chat and message touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and Linq work finishes.
Linq chats are fetched, grouped, drafted into a digest, approved, then posted back.
Linq digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Linq
Queued
Collections and dashboards
Linq health reports itself on schedule.
Four metrics, 14 days of Linq chats created and a team breakdown, computed directly.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking deletes for a team, 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 blocking deleting messages, removing participants or editing phone numbers. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
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 and every other client at the same time.
Put Linq in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.