Nylas MCP connector
The Nylas connector brings your Nylas applications, connectors, grants and calendar events into Elaichi, so Claude, ChatGPT, Cursor and the Elaichi Agent can list, check, update and revoke them inside each person's own access, with every call logged.
-
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 Nylas to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Nylas once
-
Open Connections, choose Add connection, and pick Nylas.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Nylas API key. One person generates a token in Nylas 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.
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 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.
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.
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.
Use cases
What teams do with Nylas through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
Compare
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 | $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.
AI tools
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.