Skip to content
Nearlysent
Docs menu

Use with Claude

Add Nearlysent as a custom connector in Claude (claude.ai, Claude Desktop or Claude Code) and let Claude draft replies on your own Claude plan, without an API key. Steps, approval, revoking, example prompts, limits and privacy.

Nearlysent works as a custom connector in Claude: in claude.ai, in Claude Desktop and in Claude Code. You connect it once, and then you can ask Claude to work through your inbox. Claude runs on your own Claude plan, so you do not need an API key in Nearlysent.

Through the connector Claude can:

  • list the emails that need a reply (subject, sender, when it arrived, and whether a draft already exists);
  • read a thread, oldest message first, as plain text;
  • search your knowledge in Nearlysent and cite the passages it uses;
  • read the current draft of a thread;
  • save a reply draft for a thread.

There is no send tool. Claude cannot send email, delete anything, or change your mailbox or settings. A draft Claude saves shows up in the Nearlysent Inbox with the badge Draft by Claude, and a person in your team reviews it, edits it if needed and sends it, exactly like any other draft.

Two ways to get drafts

Your own API key Through Claude
How Add a key under Settings → AI provider Add the connector in Claude and ask Claude
When Automatically, for every new email On demand, when you ask Claude
Who pays Your AI provider, per use Your Claude plan
New mail sorted (triage) Yes No, new threads stay unsorted

You can use both in the same workspace. Without an API key the Inbox shows the hint Claude mode: ask Claude to draft replies, and new mail is imported but not sorted or drafted automatically. See Pricing for what an API key costs.

Before you start

  • An account in Nearlysent and a workspace with a connected mailbox (see Getting started). Add some knowledge, so Claude has something to cite.
  • A Claude plan on which you can add custom connectors. On a Team or Enterprise plan, an owner of your Claude organization may have to allow or add custom connectors first.
  • Any member of the workspace can connect; the connection only reaches the workspace you choose.

1. Copy the connector URL

  1. In Nearlysent, open your workspace and go to Settings → Claude connector.
  2. Next to Connector URL, click Copy. The URL is the address of Nearlysent followed by /mcp:
https://app.nearlysent.com/mcp

The same page has these steps with your URL filled in, the Claude Code command ready to copy, and the list of Connected clients.

2. Add the connector in Claude

claude.ai

  1. Open claude.ai → Settings → Connectors.
  2. Choose Add custom connector, name it Nearlysent and paste the connector URL.
  3. Click Connect.
  4. Log in to Nearlysent if asked, pick the workspace and approve (see Approve the connection).

Claude Desktop

  1. Open Claude Desktop → Settings → Connectors.
  2. Choose Add custom connector, name it Nearlysent and paste the connector URL.
  3. Click Connect.
  4. Log in to Nearlysent if asked, pick the workspace and approve.

Claude Code

  1. Run in your terminal (the name is up to you; Settings → Claude connector suggests one):
claude mcp add --transport http <name> https://app.nearlysent.com/mcp
  1. Then type /mcp in Claude Code, choose the connector and Authenticate.
  2. Your browser opens. Log in to Nearlysent if asked, pick the workspace and approve.

Approve the connection

When Claude connects, your browser opens Nearlysent. If you are not logged in, you log in first and come straight back. The approval page shows:

  • the name of the app that asks, in quotes, for example “Claude” wants to access your Nearlysent inbox. The app chose that name itself, so check that you just started this connection;
  • Sends you back to: where your approval goes. If it says the approval goes to an app on this computer (localhost), only approve if you just started the connection yourself, for example from Claude Code;
  • If you approve, it can: read the email threads of the workspace you choose, search the knowledge of that workspace and save reply drafts for you to review. It cannot send email, delete anything or change settings;
  • Workspace: the workspaces you are a member of. Pick the one Claude may use.

Click Approve to connect, or Deny to stop; Claude then reports that access was denied. One connection reaches one workspace. To use Claude with a second workspace, add the connector a second time under another name and pick the other workspace.

If the page says This connection cannot continue, the request expired (after 10 minutes), was already answered, or the app is not known. Start connecting again from Claude. The read-only demo cannot be connected.

Example prompts

  • “Which emails need a reply?”
  • “Draft answers from our knowledge base and save them as drafts.”
  • “Show me the draft for the newest thread.”
  • “Read the email from Sam about the helmet and draft a short, friendly reply. Cite our return policy.”
  • “Which open emails ask about delivery times? Summarise them in a table.”

Then open the Inbox in Nearlysent: threads with a draft from Claude show Draft ready and Draft by Claude under Needs review. Open the thread, check the reply and its sources, edit it, and click Send (or Save to my mailbox drafts). Nothing is sent until you do.

Revoke access

  • In Nearlysent: Settings → Claude connector → Connected clients → Revoke next to the client, and confirm. Access ends at once; Claude has to be connected and approved again to use it. Members see their own connections; admins and owners see and can revoke everyone’s in the workspace.
  • In Claude: remove the connector under Settings → Connectors in claude.ai or Claude Desktop, or run claude mcp remove <name> in Claude Code. This stops Claude from using it, but only revoking in Nearlysent ends the access on our side, so do both.

Access also ends by itself when you change or reset your password, when you leave or are removed from the workspace, and when your account is disabled or deleted.

Limits

  • Claude can only read your mail and knowledge and save drafts. It cannot send, delete, change mailboxes, members or settings, or mark mail as read.
  • Rate limit: about 60 tool calls per minute per connection. Above that, Claude is told to wait a moment.
  • Claude saves drafts only for open threads. A draft from Claude replaces the open draft of that thread (earlier versions are kept), and it never replaces a reply that is being sent.
  • Long emails are shortened for Claude (about 8,000 characters per message), and very long threads leave out the oldest messages.
  • Claude drafts have no confidence level; check the reply and its sources as you would any draft.
  • Without an API key, new mail is not sorted (no category or priority) and Generate draft in the app needs a key. Claude’s drafts do not.
  • Sign-in for the connector lasts up to 30 days of no use; after that, Claude asks you to authenticate again.

Privacy

  • Whatever Claude reads through the connector (the email threads, the knowledge passages and the drafts it asks for) is sent to Anthropic, under the terms of your own Claude account, like anything else you share in a Claude chat. Your Claude plan’s privacy settings apply. Using the connector is your choice; Nearlysent itself does not send your data to Claude.
  • Nearlysent stores only what it needs for the connection: which app you approved, for which workspace, when it was last used, and the access tokens as one-way hashes. Each tool call is logged with ids and counts only, never the content.
  • Email text and documents are given to Claude clearly marked as untrusted content, with a note not to follow instructions inside them. Since Claude has no send tool, the worst a malicious email can do is make a bad draft, which you see before anything happens.

More on how your data is handled: Security & privacy and the privacy policy.

Something unclear or missing in the docs?Tell us.