Redash MCP connector
The Redash connector brings your dashboards, alerts, subscriptions and access lists into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can find, update and share them as the person who signed in.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Redash alerts fired this week and who subscribes to them?
Working in Redash with Elaichi
-
Get single Redash acl by ID
-
List all Redash acls
-
List all Redash alerts
How to connect Redash to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Redash 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.
Redash 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.
Redash 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.
Redash 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.
Redash 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 Redash 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 Redash through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Redash is logged.
-
Data
Tidy up dashboards before the quarterly review
Ask which Redash dashboards carry the finance tag, rename the stale ones and share the right ones with leadership, without clicking through each page by hand.
-
Operations
Find out which alerts fired overnight
Get a plain summary of the Redash alerts that triggered, who subscribes to each one and which are currently muted, before the morning standup.
-
Finance
Fork a dashboard for the new cost center
Copy the existing spend dashboard in Redash, retitle it for the new cost center and hand the fork to the team that owns it.
-
Support
Mute a noisy alert during planned maintenance
Tell the agent to mute the queue depth alert in Redash for the maintenance window, then confirm who is subscribed so nobody is surprised when it comes back.
-
Sales
Share the pipeline dashboard with a new rep
Give a new hire access to the Redash pipeline dashboard and the alert on stalled deals, and check the access list reads the way the manager expects.
-
Leadership
See what the company is actually watching
List the favorite Redash dashboards across the organization and the alerts tied to them, so you know which numbers people check every day.
Try asking
- “Which Redash alerts fired this week and who subscribes to them?”
- “List the dashboards tagged finance and who they are shared with”
- “Mute the churn alert until Monday and tell me who subscribes”
What connecting Redash gets you
6 screens from Elaichi, each doing one job for your Redash account.
Ask Elaichi to work across your apps.
Which Redash alerts fired this week and who subscribes to them?
List the dashboards tagged finance and who they are shared with
Mute the churn alert until Monday and tell me who subscribes
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your dashboards, get live answers.
Type a plain question and the agent reads Redash dashboards and alerts as they stand now.
Copy the endpoint
AI apps
One endpoint brings Redash to every client.
Claude, ChatGPT and Cursor reach Redash through one governed endpoint, with no SDK or shared key.
Tool catalog
All 109 Redash tools, ready without code.
Dashboards, alerts, subscriptions and access lists, covered in one catalog nobody had to build.
Toolboxes
Every team gets its own Redash toolbox.
Finance sees its dashboards, Support sees its alerts, each team scoped to what it needs.
Shared connections
Share a Redash connection, never the key.
One person connects Redash, teammates work through it, and nobody else sees the API key.
Audit log
Every Redash change names who made it.
When, who, what happened and which dashboard or alert, kept 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.
Redash digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch dashboards
Redash
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
Redash
Queued
Workflows
A schedule starts the work, a person approves.
Alerts are fetched, grouped and drafted into a digest, approved, then posted back to Redash.
Redash health
Refreshed 4 minutes ago · every 15 minutes · from the dashboards collection
Dashboards
1,284 ↓ 12%
Alerts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Dashboards created
Last 14 days
By team
Share of activity
Data Platform 34%
Operations 27%
Finance 21%
Support 18%
Collections and dashboards
Redash health numbers arrive without anyone asking.
Four metrics, a 14 day chart and a team breakdown, computed on schedule with no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Redash
All three can connect Redash 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 Redash tools | Allow or restrict single Redash 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 Redash 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.
Redash tools for your AI agents
109 tools are ready to call through Elaichi's MCP endpoint the moment you connect Redash, 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 Redash to Claude?
Connect Redash in Elaichi by pasting your Redash API key, the one found under your Redash profile, and nothing else, since there is no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and your Redash dashboards and alerts are available in the chat.
Does Redash work with ChatGPT and Cursor as well as Claude?
Yes. Once Redash 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 Redash once and every client sees it.
What can an AI agent actually do with my Redash data?
It can list, open, create, update, fork and share Redash dashboards, add and remove tags and favorites, and set up or change alerts, alert subscriptions and mutes. It can also read and update the access lists that say who can see what in Redash. Short, concrete asks such as "mute the churn alert until Monday" work better than long paragraphs.
Does connecting Redash give the AI access to every dashboard and alert?
No. The agent works inside the Redash access of the person who signed in, so it sees the dashboards and alerts that person could already open in Redash. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what Redash itself allows.
Can I stop an agent from deleting or changing things in Redash?
Yes. Restrictions in Elaichi apply per action, so you can restrict deleting Redash dashboards or alerts for a role or for one person while leaving reading and sharing 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 Redash connection when someone leaves?
Offboarding that person in Elaichi ends their access to Redash through every client at once. A Redash connection shared with the team keeps working for everyone else. If you want it gone entirely, disconnecting Redash once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Redash MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Redash 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 Redash?
Yes. Both let Claude, ChatGPT or Cursor use Redash. 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 Redash call.
How is Elaichi different from Composio for Redash?
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 Redash: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Redash 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