Nylas MCP Server

io.usefulapi/nylas

not responding

Nylas is listed as active in the registry but did not answer our last check. It exposes 15 tools. Last commit 1 Aug 2026.

MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.

Uptime history 42 hours of history · worst hour 0%

42 hours agonow

26.4%

Uptime 24h

24 of 91 checks

Tools

read from the server

182 ms

Response time

average over 24h

Stars

last commit 1 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add nylas --transport http https://nylas.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "nylas": {
      "url": "https://nylas.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.nylas]
url = "https://nylas.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "nylas": {
      "url": "https://nylas.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "nylas": {
      "url": "https://nylas.usefulapi.io/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

nylas

nylas_create_draft

Creates a draft email (does NOT send — safe/additive). Nylas v3: POST /v3/grants/{grant_id}/drafts.

nylas_create_event

Creates a calendar event (may send invites to participants). Requires calendar_id (sent as a query param). Nylas v3: POST /v3/grants/{grant_id}/events.

nylas_get_calendar

Get a single calendar by id. Nylas v3: GET /v3/grants/{grant_id}/calendars/{calendar_id}.

nylas_get_contact

Get a single contact by id. Nylas v3: GET /v3/grants/{grant_id}/contacts/{contact_id}.

nylas_get_event

Get a single calendar event by id. Requires calendar_id (sent as a query param). Nylas v3: GET /v3/grants/{grant_id}/events/{event_id}.

nylas_get_grant

Get details for a single connected account (grant). Nylas v3: GET /v3/grants/{grant_id}.

nylas_get_message

Get a single email message by id. Nylas v3: GET /v3/grants/{grant_id}/messages/{message_id}.

nylas_list_calendars

List calendars for the connected account (each has a calendar_id used by the events tools). Nylas v3: GET /v3/grants/{grant_id}/calendars.

nylas_list_contacts

List contacts for the connected account, with optional email/phone filters. Nylas v3: GET /v3/grants/{grant_id}/contacts.

nylas_list_drafts

List draft emails for the connected account. Nylas v3: GET /v3/grants/{grant_id}/drafts.

nylas_list_events

List calendar events. Requires calendar_id (sent as a query param). Nylas v3: GET /v3/grants/{grant_id}/events.

nylas_list_folders

List mail folders/labels for the connected account. Nylas v3: GET /v3/grants/{grant_id}/folders.

nylas_list_grants

List the connected accounts (grants) on this Nylas application, each with a grant_id used to scope other tools. Not grant-scoped. Nylas v3: GET /v3/grants.

nylas_list_messages

List email messages for the connected account, with optional filters. Nylas v3: GET /v3/grants/{grant_id}/messages.

nylas_send_message

SENDS a real email via the connected account. This dispatches an actual message. Nylas v3: POST /v3/grants/{grant_id}/messages/send.

Endpoints

URL	Transport	State	Latency	Checked
https://nylas.usefulapi.io/mcp	streamable-http	answering	51 ms	9 min ago

Nylas — questions

Answers built from our own checks of this server.

What can Nylas do?

It exposes 15 tools, read directly from the server on our last check. Among them: nylas_create_draft, nylas_create_event, nylas_get_calendar, nylas_get_contact, nylas_get_event, nylas_get_grant and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Nylas working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 24 of 91 checks got a reply (26.4%), average response time 182 ms. The bar chart above shows every period we have measured.

The registry lists Nylas as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Nylas?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Nylas need an API key?

No. Nylas completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Nylas?

It answers our handshake in 182 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Nylas open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.