MCP server for email (Nylas API based)
If you already use Inbox MCP, the inbox mcp mcp server is the piece that lets your assistant work with it directly. MCP server for email (Nylas API based).
Transform your inbox into an intelligent, LLM-powered assistant—instantly.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: NYLAS_ACCESS_TOKEN, NYLAS_GRANT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by darinkishore; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"inbox": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"NYLAS_ACCESS_TOKEN": "your-value",
"NYLAS_GRANT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| NYLAS_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| NYLAS_GRANT_ID | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.