Day AI MCP connector
The Day AI connector lets Claude, ChatGPT, Cursor and the Elaichi Agent search and update your Day AI contacts, organizations and opportunities, read meeting recordings, and draft notes, tasks and emails, all inside each person's own access.
-
How it connects. Connects over OAuth. 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 Day AI to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Day AI once
-
Open Connections, choose Add connection, and pick Day AI.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Day AI. Day AI's own window opens. Whoever approves it decides what this connection can reach.
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.
Day AI 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.
Day AI 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 today. The plugin directory lives at chatgpt.com/plugins.
Day AI 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.
Connect Day AI 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 Day AI through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Catch the opportunity up after a call
Ask what was agreed in this morning's meeting recording, then have the opportunity, the next step and a follow-up task updated in Day AI without opening it.
-
Sales
Draft the follow-up email before lunch
Pull the key points from the recording and create an email draft in Day AI that the rep reviews and sends in their own words.
-
Customer Success
Prepare for a renewal conversation
Search the account's contacts, recent meetings and open tasks in Day AI and get a one-page brief before the call starts.
-
Revenue Operations
Find the opportunities that have gone quiet
Ask for opportunities with no meeting or note in three weeks, then add a task for the owner of each one.
-
Leadership
Get the week's pipeline in plain words
Ask what moved this week across Day AI opportunities and what customers raised in meetings, without waiting for a report.
-
Marketing
Turn customer meetings into messaging
Read recent meeting recordings in Day AI to find the words customers use for their problems, then save a note on each organization.
Try asking
- “Summarize yesterday's meeting with Acme and add a follow-up task.”
- “Which opportunities closing this quarter have no meeting in two weeks?”
- “Draft a renewal email to Northwind's contacts from our last call.”
Compare
Elaichi vs Zapier MCP vs Composio for Day AI
All three can connect Day AI 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 Day AI tools | Allow or restrict single Day AI 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 Day AI 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 | $15 per user per month. | 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.
See it in Elaichi
What connecting Day AI gets you
5 screens from the product, each doing one job for your Day AI account.
The agent
Ask Day AI questions in plain language.
Three starter prompts answer from live Day AI contacts, opportunities and meeting recordings.
- contacts
- organizations
- opportunities
- meetings
Ask Elaichi to work across your apps.
Summarize yesterday's meeting with Acme and add a follow-up task.
Which opportunities closing this quarter have no meeting in two weeks?
Draft a renewal email to Northwind's contacts from our last call.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Day AI in every client.
Claude, ChatGPT and Cursor reach Day AI through one governed endpoint, no SDK, no shared key.
Copy the endpoint
Toolboxes
Each team gets its own Day AI toolbox.
Sales, Customer Success and Leadership each see a toolbox scoped to their Day AI work.
- Sales
- Customer Success
- Revenue Operations
- Leadership
Shared connections
Teammates use Day AI without seeing a credential.
One person connects Day AI, teams and members work through it without handling a token.
- Sales AMER
- Sales EMEA
- Customer Success
- RevOps
Audit log
Every Day AI change names who made it.
The log records when, who, what happened and which Day AI record was 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 turns Day AI meetings into digests.
Meetings are fetched, grouped, drafted into a digest, approved by a person, posted to Day AI.
Day AI digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch contacts
Day AI
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
Day AI
Queued
Collections and dashboards
Day AI health, computed without a model.
Four metrics, fourteen days of opportunities created and a team breakdown, refreshed on a schedule.
Day AI health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Organizations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Sales AMER 34%
Sales EMEA 27%
Customer Success 21%
RevOps 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Day AI to Claude?
Connect Day AI in Elaichi first, which opens Day AI's own sign-in screen and asks you to approve access, with no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi, and your Day AI contacts, opportunities and meeting recordings are available in the chat.
Does Day AI work with ChatGPT and Cursor as well as Claude?
Yes. Once Day AI 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 Day AI once and every client you sign into picks it up.
What can an AI agent actually do with my Day AI data?
With Day AI connected, an agent can look up contacts, organizations and opportunities, update them after a conversation, read what was said in a meeting recording, and create notes, tasks and email drafts for you to review. Short, concrete asks work best, such as summarizing one meeting or updating one opportunity, rather than a long paragraph of instructions.
Does connecting Day AI give the AI everything in my workspace?
No. The AI sees only what you can see in Day AI, because every call runs as the person who signed in, with Day AI's own permissions applied. Elaichi can narrow that further with restrictions, and it never widens access beyond what your Day AI account already allows.
Can I stop an agent from deleting or changing things in Day AI?
Yes. Restrictions in Elaichi apply per action, so you can allow searching and reading Day AI meeting recordings while blocking updates to opportunities or contacts. A restricted action is never advertised to the AI client, so no prompt, however worded, can reach it.
What happens to a Day AI connection when someone leaves?
Offboarding a person in Elaichi ends their Day AI access from every client at once. A shared Day AI connection keeps working for everyone else on the team. If you disconnect Day AI in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.
Does the Day AI MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Day AI 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, 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 Day AI?
Yes. Both let Claude, ChatGPT or Cursor use Day AI. 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 Day AI call.
How is Elaichi different from Composio for Day AI?
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 Day AI: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Day AI in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.