Nylas CLI gives AI agents a real email account, working calendar, and contact across Gmail, Outlook, Exchange, Yahoo, iCloud, and IMAP through one auth flow
We built Nylas CLI because every AI agent demo I saw was hitting a wall the same way: "your agent can read your inbox" turned into 200 lines of OAuth code, a Gmail-only integration, and a token refresh bug three days later.
So we shipped one binary that solves it for 6 providers Gmail, Outlook, Exchange, Yahoo, iCloud, IMAP through a single auth flow. Run `nylas mcp install` and Claude/Cursor/your agent of choice gets 16 tools: send mail, search threads, create events, look up contacts, the lot.
A few things we got obsessed with: - One auth flow: OAuth for Google/Microsoft, app passwords for Yahoo/iCloud, server config for Exchange all hidden behind `nylas auth`. You never write provider-specific code. - MCP native: The CLI is the MCP server. No second binary, no daemon. Tools are typed, errors are structured, agents handle them well. - Open source: MIT, written in Go, single static binary. No telemetry, no signup wall.
Would love feedback especially from anyone building agents that need email/calendar access. What's the workflow we should optimize for next?
the oauth problem kills most email agent projects before they start. solid solve
How do you handle all the 2FA and frequent logouts imposed by organizational policies?
the agent layer for email + calendar is where a lot of audit conversations land. when an agent emails on behalf of a user, the question regulators are starting to ask is which trace produced which message.
how do you think about identity attribution for the agent's actions?
Congrats on the launch 🙌 Quick question: when an agent sends an email through Nylas CLI, does it appear as the user, the agent, or a delegated identity?
About Nylas CLI on Product Hunt
“Email, calendar, and contacts for AI agents”
Nylas CLI launched on Product Hunt on May 9th, 2026 and earned 78 upvotes and 8 comments, placing #14 on the daily leaderboard. Nylas CLI gives AI agents a real email account, working calendar, and contact across Gmail, Outlook, Exchange, Yahoo, iCloud, and IMAP through one auth flow
Nylas CLI was featured in Email (36.7k followers), Calendar (32k followers), Artificial Intelligence (468.7k followers) and GitHub (41.2k followers) on Product Hunt. Together, these topics include over 125.4k products, making this a competitive space to launch in.
Who hunted Nylas CLI?
Nylas CLI was hunted by Qasim Muhammad. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Nylas CLI stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Qasim Muhammad
Hey Product Hunt — Qasim from Nylas here.
We built Nylas CLI because every AI agent demo I saw was hitting a wall the same way: "your agent can read your inbox" turned into 200 lines of OAuth code, a Gmail-only integration, and a token refresh bug three days later.
So we shipped one binary that solves it for 6 providers Gmail, Outlook, Exchange, Yahoo, iCloud, IMAP through a single auth flow. Run `nylas mcp install` and Claude/Cursor/your agent of choice gets 16 tools: send mail, search threads, create events, look up contacts, the lot.
A few things we got obsessed with:
- One auth flow: OAuth for Google/Microsoft, app passwords for Yahoo/iCloud, server config for Exchange all hidden behind `nylas auth`. You never write provider-specific code.
- MCP native: The CLI is the MCP server. No second binary, no daemon. Tools are typed, errors are structured, agents handle them well.
- Open source: MIT, written in Go, single static binary. No telemetry, no signup wall.
Would love feedback especially from anyone building agents that need email/calendar access. What's the workflow we should optimize for next?
→ https://cli.nylas.com → https://github.com/nylas/cli
Use CLI today to connect your email
Command: nylas init