Nylas MCP connector
The Nylas connector brings your Nylas applications, connectors, grants and calendar events into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can list, check, update and revoke them inside each person's own access, with every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Nylas grants stopped syncing in the last week?
Working in Nylas with Elaichi
-
List all Nylas applications
-
List all Nylas applications redirect uris
-
Get single Nylas applications redirect uris by ID
How to connect Nylas to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Nylas 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.
Nylas 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.
Nylas 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.
Nylas 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.
Nylas 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 Nylas 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 Nylas through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Nylas is logged.
-
Support
Find out why a customer's mailbox stopped syncing
Look up the customer's grant, see its status and the provider behind it, and tell the customer what to do next without opening the Nylas dashboard.
-
Engineering
Add a redirect URI before a release
Ask for the redirect URIs on your Nylas application, add the new staging address, and confirm it took effect, all from the editor you already have open.
-
Security
Revoke a reported grant right away
When someone reports a compromised account, find the grant and revoke its access in one step, then check the token information to confirm nothing is still live.
-
Product
See which providers your customers connect
List the connectors set up for Google, Microsoft and other providers, and detect which provider a given email address belongs to before you plan a rollout.
-
Operations
Clean up stale connectors in bulk
Pull the full list of Nylas connectors, pick the ones nobody uses, and update or remove them together instead of one at a time.
-
Customer success
Pull a customer's events before a call
List the events attached to a customer's grant and have a summary of what is on their calendar ready before the check-in starts.
Try asking
- “Which Nylas grants stopped syncing in the last week?”
- “Add a redirect URI for staging to our Nylas application.”
- “List the connectors we have set up for Google and Microsoft.”
What connecting Nylas gets you
6 screens from Elaichi, each doing one job for your Nylas account.
Ask Elaichi to work across your apps.
Which Nylas grants stopped syncing in the last week?
Add a redirect URI for staging to our Nylas application.
List the connectors we have set up for Google and Microsoft.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about grants and get live answers.
Which grants failed this week? The Elaichi Agent reads live Nylas records and answers.
Copy the endpoint
AI apps
Nylas works in Claude, ChatGPT, Cursor and Microsoft Copilot.
One governed endpoint, signed in over OAuth, with no SDK and no shared API key.
Tool catalog
212 Nylas tools, no custom code to write.
Applications, connectors, grants, redirect URIs and events, every method ready the moment you connect.
Toolboxes
Every team gets its own Nylas toolbox.
Support sees grants, Engineering sees connectors and redirect URIs, each scoped to the team.
Shared connections
Share a Nylas connection, not the API key.
One person connects, teammates work through it, and nobody else ever sees a credential.
Audit log
Every Nylas call is on the record.
When, who, what happened and which grant, in an audit log nobody can edit.
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.
Nylas digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch grants
Nylas
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
Nylas
Queued
Workflows
A schedule starts the work, a person approves.
Grants are fetched, grouped, drafted into a digest, approved, then written back to Nylas.
Nylas health
Refreshed 4 minutes ago · every 15 minutes · from the grants collection
Grants
1,284 ↓ 12%
Connectors
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Grants created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Support 21%
Engineering 18%
Collections and dashboards
Nylas health, computed on a schedule.
Grants created over 14 days, four live metrics and a breakdown by team, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Nylas
All three can connect Nylas 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 Nylas tools | Allow or restrict single Nylas 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 Nylas 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.
Nylas tools for your AI agents
212 tools are ready to call through Elaichi's MCP endpoint the moment you connect Nylas, 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 Nylas to Claude?
In Elaichi, choose Nylas from the connector catalog and paste your Nylas API key; there is 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 https://api.elaichi.ai/mcp. Claude signs you in through Elaichi, and Nylas appears alongside everything else you have connected.
Does Nylas work with ChatGPT and Cursor as well as Claude?
Yes. Nylas is connected once in Elaichi and reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. There is nothing extra to set up per client.
What can an AI agent actually do with my Nylas data?
With Nylas connected, an agent can list your Nylas applications, connectors and grants, look up a single grant to check its status, update or revoke it, add or remove redirect URIs, detect the provider behind an email address, and list the events attached to a grant. Short, concrete asks such as "revoke the grant for this address" work better than long paragraphs.
Does connecting Nylas give the AI access to every application and grant?
No. Nylas access follows the API key the person connected and what that key is allowed to do in Nylas, so the agent sees the same applications, connectors and grants that person would see. Elaichi can narrow that access further for a role or a toolbox, and it can never widen it.
Can I stop an agent from deleting or changing things in Nylas?
Yes. Restrictions in Elaichi work per action, so you can allow listing Nylas grants and connectors while restricting deletes, revocations or bulk updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Nylas connection when someone leaves?
Offboarding a person in Elaichi ends their access to Nylas at once, across every client they used. A shared Nylas connection keeps working for everyone else on the team. If you disconnect Nylas in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Nylas MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Nylas 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 Nylas?
Yes. Both let Claude, ChatGPT or Cursor use Nylas. 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 Nylas call.
How is Elaichi different from Composio for Nylas?
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 Nylas: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Nylas 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