Skip to content
Model Context Protocol server

सेतु

Setu

Setu — Connect AI to Gmail
in minutes.

एक मार्गदर्शक, आपके सपनों और अवसरों के बीच।

Setu is an MCP server that lets Claude, ChatGPT, or Cursor send job applications from your own Gmail — researched by the assistant, written for the actual posting, approved by you before it leaves.

Get startedGitHub

Start with 5 free emails. No install — it's a URL.

setu — connect

How it works

Six steps, once. After that it's a sentence in a chat window.

  1. 1

    Add the URL

    One connector URL into Claude, ChatGPT, or any MCP client. Nothing to install.

  2. 2

    Sign in with Google

    Grant one permission — send email. That's the whole auth step.

  3. 3

    Save your resume link

    Setu checks it's publicly openable, then appends it to every application.

  4. 4

    Ask in plain language

    “Find fintech startups hiring backend engineers and apply.” Your assistant does the research.

  5. 5

    Read the drafts

    Every recipient and a full draft, before anything leaves. You approve.

  6. 6

    Sent as you

    Setu delivers through Gmail, paced and logged. Replies go straight to you.

Works with any MCP client

Claudeclaude.ai connectorstestedClaude CodeCLItestedChatGPTDeveloper mode, paid planstestedCursorremote MCPVS CodeMCP extensionWindsurfremote MCPClineremote MCPContinue.devremote MCP

Setu speaks standard Streamable HTTP MCP with OAuth, so any compliant client should connect. “Tested” marks the ones we've actually run — the rest are expected to work but unverified. These are integrations, not endorsements: none of these vendors sponsor or affiliate with Setu.

What is MCP?

An AI assistant can write a good application email. What it can't do, on its own, is send one — it has no hands. Every tool it touches has to be wired in, and until recently every assistant needed its own wiring.

Model Context Protocol is the standard that fixed that. A tool exposes its capabilities once, over MCP, and any compatible client can use them — the same way a website works in any browser.

Setu is one of those servers. It exposes six things an assistant can do with your Gmail, and the assistant decides when to use them.

  1. You

    “apply to these 10”

  2. Claude

    researches, writes

  3. Setu

    verifies, limits, sends

  4. Your Gmail

    your account

  5. HR

    receives it from you

100% Secure for your inbox. Setu is designed with strict security limits—it will never read your inbox. It only has permission to send emails on your behalf.

Nothing here holds your password, and nothing stores a token. Claude asks Setu to send; Setu asks Google, using a permission you granted and can revoke at any time. The mail leaves your account — so replies come back to your inbox, not ours.

Why this one

Setu owns the parts a language model shouldn't be trusted with: who you are, what's already been sent, how much is too much, and the send itself.

Sends from your Gmail

Not a noreply@ nobody answers. It leaves your account, shows in your Sent folder, and replies come back to your inbox.

Cannot read your inbox

Setu asks Google for one permission: gmail.send. Reading mail needs a scope it never requests and cannot use.

Resume link, checked

Paste it once and it rides along on every application. Setu fetches it first — a Drive file you forgot to share gets rejected here, not silently in someone's inbox.

Address verification

Optional MX and citation checks catch addresses a model invented from a naming pattern. Those bounce, and bounces cost you deliverability.

Batches with a ceiling

25 per call, 80 per day. Small enough that you review as you go instead of finding out afterwards.

Paced sending

A 5s gap between sends by default. A burst is one of the patterns Gmail reads as automation.

No duplicate sends

Every send is recorded. Setu can check a fresh list against that history before a single email goes out.

OAuth, no passwords

You sign in on Google's page. Setu never sees a password, and stores no token — the OAuth layer issues a fresh one per request.

Open source

Server, desktop version, and this site are all in the repo. Self-host with your own Google credentials if you'd rather.

What Setu can and can't do

Most tools ask you to trust a privacy policy. The list below isn't policy — it's the permission Setu holds. The things in the right column aren't things Setu declines to do. They're things it has no mechanism for.

Can

  • Can: Send an email as you, when you approve it
  • Can: Read your name and email address
  • Can: Store your resume link and send history

Cannot

  • Cannot: Open your inbox or read a single message
  • Cannot: See replies from HR — those go only to you
  • Cannot: Know your password. Google handles login
  • Cannot: Keep access after you revoke it

No tokens at rest

The OAuth layer supplies a fresh access token per request. There is no credential in the database to steal.

Limits in code

80/day and 25/batch are enforced by the server, not suggested to the model.

Revoke anytime

myaccount.google.com/permissions → remove Setu. The token dies immediately, without asking us.

Questions

Model Context Protocol — an open standard for connecting AI assistants to external tools. Instead of every assistant building its own Gmail integration, a tool exposes an MCP server once and any compatible client can use it. Setu is such a server.

One URL. Two minutes.

Add the connector, sign in with Google, paste your resume link. That's the entire setup.

Read the docs