Qlik Sense MCP connector
Connect Qlik Sense to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can look up and manage Qlik Sense users, groups, roles and license assignments inside each person's own access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Qlik Sense users have a license but belong to no group?
Working in Qlik Sense with Elaichi
-
List all Qlik Sense licenses
-
List all Qlik Sense roles
-
Get single Qlik Sense role by ID
How to connect Qlik Sense to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Qlik Sense 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.
Qlik Sense 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.
Qlik Sense 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.
Qlik Sense 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.
Qlik Sense 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 Qlik Sense 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 Qlik Sense through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Qlik Sense is logged.
-
IT
Set up a new analyst in minutes
Create the Qlik Sense user, add them to the right groups and assign a license from one request. No more three tickets for one starter.
-
Finance
Find out who is holding an unused seat
Pull the Qlik Sense license assignments against the user list and reclaim seats before the next renewal. Bulk remove the ones nobody is using.
-
Analytics
Check who belongs to which group
Ask which Qlik Sense groups and roles a person holds before you share a sensitive app. Fix a wrong membership on the spot.
-
Security
Review roles before an audit
List every Qlik Sense role, see who holds it, and tighten or delete the ones nobody should have.
-
People Ops
Clean up access when someone leaves
Remove a departing employee's Qlik Sense license assignment and delete the user without waiting on a ticket.
-
Operations
Reorganize groups after a team change
Rename groups, update group settings in bulk and move people across when departments merge or split.
Try asking
- “Which Qlik Sense users have a license but belong to no group?”
- “Add Priya to the Finance group and assign her a professional license.”
- “List every role and who holds it.”
What connecting Qlik Sense gets you
6 screens from Elaichi, each doing one job for your Qlik Sense account.
Ask Elaichi to work across your apps.
Which Qlik Sense users have a license but belong to no group?
Add Priya to the Finance group and assign her a professional license.
List every role and who holds it.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Qlik Sense licenses in plain language.
Three starter prompts answer from live Qlik Sense users, groups and roles.
Copy the endpoint
AI apps
One endpoint brings Qlik Sense to every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Tool catalog
569 Qlik Sense tools, no code to write.
Users, groups, roles and license assignments are covered the day you connect.
Toolboxes
Every team gets its own Qlik Sense toolbox.
IT manages users and roles while Finance only sees licenses.
Shared connections
Teammates use Qlik Sense without touching the key.
One person connects, shares with teams and members, and the API key stays private.
Audit log
Every Qlik Sense change names who made it.
When, who, what happened, type and resource, in an append-only log.
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.
Qlik Sense digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Qlik Sense
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
Qlik Sense
Queued
Workflows
A schedule reclaims Qlik Sense licenses by itself.
License assignments are fetched, grouped, drafted into a digest, approved by a person, then posted back.
Qlik Sense health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
IT 34%
Finance 27%
Security 21%
Analytics 18%
Collections and dashboards
Qlik Sense license health, computed without a model.
Four metrics, users created over 14 days and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Qlik Sense
All three can connect Qlik Sense 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 Qlik Sense tools | Allow or restrict single Qlik Sense 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 Qlik Sense 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.
Qlik Sense tools for your AI agents
569 tools are ready to call through Elaichi's MCP endpoint the moment you connect Qlik Sense, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 344 of 569 Qlik Sense tools here. Connect Qlik Sense and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Qlik Sense to Claude?
Open Elaichi, choose Qlik Sense, and paste in a Qlik Sense API key. That is the whole sign-in step for Qlik Sense, with no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Qlik Sense users, groups, roles and licenses are ready in the chat.
Does Qlik Sense work with ChatGPT and Cursor as well as Claude?
Yes. Once Qlik Sense is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Qlik Sense once and every client picks it up.
What can an AI agent actually do with my Qlik Sense data?
An agent can list and search Qlik Sense users and groups, create or update them, and delete the ones that should go. It can list roles, create or change a role, see every license and who it is assigned to, and assign or remove licenses in bulk. Short, concrete asks work best, such as which users have a license but no group, rather than a long paragraph.
Does connecting Qlik Sense give the AI everything in my tenant?
No. Every request to Qlik Sense runs inside the access of the person who signed in to Elaichi, so an agent can only see and change what that person already could. Elaichi can narrow that further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Qlik Sense?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting Qlik Sense users or changing roles for a role or for one person while leaving lookups open. 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 Qlik Sense connection when someone leaves?
Offboarding a person in Elaichi ends their access to Qlik Sense at once, in every client they used. A shared Qlik Sense connection keeps working for everyone else on the team. If you ever want it gone, disconnecting Qlik Sense once in Elaichi removes it from every client.
Does the Qlik Sense MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Qlik Sense 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 Qlik Sense?
Yes. Both let Claude, ChatGPT or Cursor use Qlik Sense. 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 Qlik Sense call.
How is Elaichi different from Composio for Qlik Sense?
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 Qlik Sense: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Qlik Sense 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