# Sign in to the Nylas MCP server with OAuth

Source: https://developer.nylas.com/docs/changelogs/2026-11-20-mcp-server-sign-in/

The [Nylas MCP server](/docs/dev-guide/mcp/) now supports OAuth. Add it to Claude Code, ChatGPT, Cursor, Codex CLI, or any other MCP client by URL, then sign in with your Nylas account. You don't need to create or paste an API key.

## New

- **Sign in with your Nylas account.** Add `https://mcp.us.nylas.com` or `https://mcp.eu.nylas.com` to your client with no `Authorization` header. The client opens the Nylas Dashboard in your browser, where you choose an organization, pick up to 5 connected accounts, and choose **Read only**, **Read and write**, or custom permissions. Your Dashboard role caps the access you can give.
- **Limit a sign-in with an IAM principal.** Organization owners and admins can pick an [IAM principal](/docs/v3/auth/nylas-iam/) when they sign in. The agent then gets only what both the sign-in and the principal allow.
- **Short-lived tokens.** Access tokens last 15 minutes, and the client refreshes them until you disconnect it.

API keys still work. Use them for agents your backend hosts for your users, with one [IAM API key](/docs/v3/auth/nylas-iam/#create-and-manage-iam-api-keys) per user bound to that user's accounts, as shown in [Limit an AI agent to one user's accounts](/docs/cookbook/ai/mcp/limit-agent-to-one-user/).

## Documentation

- **Nylas MCP server.** [The MCP server page](/docs/dev-guide/mcp/) now covers signing in and connecting with an API key separately, with setup for each client. The tools table shows which tools work with a sign-in. The page also explains when to use the [Nylas CLI](/docs/v3/getting-started/cli/) instead.
- **Claude Code and Codex CLI.** The Claude Code and Codex CLI cookbook guides include the sign-in option.
- **New cookbook guides.**
  - [Use Nylas MCP with Cursor](/docs/cookbook/ai/mcp/cursor/) covers signing in, or connecting with an API key read from an environment variable.
  - [Limit an AI agent to one user's accounts](/docs/cookbook/ai/mcp/limit-agent-to-one-user/) gives each user's hosted agent its own IAM key, bound to a workspace of that user's mailboxes and Agent Account.
  - [Give an AI agent read-only email access](/docs/cookbook/ai/mcp/read-only-email-agent/) creates a key that reads one mailbox and can't send or delete.
  - [Rotate an AI agent's API key](/docs/cookbook/ai/mcp/rotate-agent-api-key/) replaces a key before it expires or after a leak, with no downtime.