Whats up Product Hunt — Qasim from Nylas right here.
We constructed Nylas CLI as a result of each AI agent demo I noticed used to be hitting a wall the similar manner: “your agent can learn your inbox” was 200 traces of OAuth code, a Gmail-only integration, and a token refresh malicious program 3 days later.
So we shipped one binary that solves it for six suppliers Gmail, Outlook, Alternate, Yahoo, iCloud, IMAP via a unmarried auth drift. Run `nylas mcp set up` and Claude/Cursor/your agent of selection will get 16 gear: ship mail, seek threads, create occasions, glance up contacts, the lot.
A couple of issues we were given obsessive about:
– One auth drift: OAuth for Google/Microsoft, app passwords for Yahoo/iCloud, server config for Alternate all hidden in the back of `nylas auth`. You by no means write provider-specific code.
– MCP local: The CLI is the MCP server. No 2nd binary, no daemon. Gear are typed, mistakes are structured, brokers deal with them smartly.
– Open supply: MIT, written in Pass, unmarried static binary. No telemetry, no signup wall.
Would like comments particularly from any person development brokers that want electronic mail/calendar get admission to. What is the workflow we must optimize for subsequent?
→ https://cli.nylas.com → https://github.com/nylas/cli
Use CLI as of late to glue your electronic mail
Command: nylas init
