Documentation
Setu is a hosted MCP server. There is nothing to install and no config file to edit — you add one URL to your assistant and sign in with Google.
Install
Everything starts from one URL. The /mcp on the end matters — without it the client won't find the server.
https://api.mimanasa.online/mcpClaude
- 1Settings → Connectors → Add custom connector
- 2Paste the URL, click Connect
- 3Sign in with Google when the popup opens
ChatGPT
Custom connectors require Developer mode and a paid plan (Plus, Pro, Team, or Enterprise). They aren't available on the free tier.
- 1Settings → Connectors → Advanced → enable Developer mode
- 2Settings → Connectors → Create
- 3Name it
Setu, paste the URL, set auth to OAuth - 4Click Create → sign in with Google
Claude Code
claude mcp add --transport http setu https://api.mimanasa.online/mcpVS Code
VS Code (Copilot agent mode) supports remote MCP servers with OAuth natively. Add this to .vscode/mcp.json in your project, or to your user-level mcp.json:
{
"servers": {
"setu": { "type": "http", "url": "https://api.mimanasa.online/mcp" }
}
}On first use, a browser opens for Google sign-in — the same flow as Claude.
Windsurf
Windsurf supports remote MCP servers with OAuth. Add this to ~/.codeium/windsurf/mcp_config.json (Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json):
{
"mcpServers": {
"setu": { "serverUrl": "https://api.mimanasa.online/mcp" }
}
}Antigravity
Antigravity's native OAuth for remote MCP servers is currently broken (it sends the initialize request without the bearer token). Until that's fixed, connect through the mcp-remote bridge, which handles the Google sign-in locally. Settings → Customizations → Open MCP Config:
{
"mcpServers": {
"setu": {
"command": "npx",
"args": ["mcp-remote", "https://api.mimanasa.online/mcp"]
}
}
}The mcp-remote bridge works in any MCP client whose built-in OAuth misbehaves — Cursor and Cline included. Requires Node.js installed.
Google will call this app unverified
You'll see “Google hasn't verified this app”. Click Advanced → Go to Setu (unsafe).
“Unsafe” is Google's wording for “hasn't finished our review”, not a finding about Setu. The screen after it is the one that actually matters — it lists exactly one permission: Send email on your behalf. That is the whole of what Setu can do to your account.
Save your resume
Setu appends your resume link to every application, so save it once before sending. Ask your assistant:
Save my resume link: https://drive.google.com/file/d/…/viewShare the file as “Anyone with the link” first. Setu fetches the URL to check, and rejects a private link — otherwise HR clicks it, sees “Request access”, and you never learn the application went nowhere.
Using it
Setu doesn't write anything — your assistant does. Give it the context a good application needs and it will do the research itself.
Find fintech startups in Bangalore hiring backend engineers.
For each one, find their careers email and draft an
application using my resume. Show me the list and one full
draft before you send anything.Asking to see a draft first is worth the extra turn. The assistant is writing as you, to someone who may decide whether to interview you.
Limits
These are enforced by the server, not suggested to the model.
| Limit | Value | Why |
|---|---|---|
| Per day | 80 | Gmail's ceiling is higher, but staying under it protects your sending reputation |
| Per batch | 25 | Small enough that you review as you go |
| Delay | 5s | A burst is a pattern Gmail reads as automation |
| Resume | required | An application with no resume wastes the contact |
| Duplicates | blocked | Every send is recorded, across sessions |
Troubleshooting
- The client can't connect
- Check the URL ends in
/mcp. That's the usual one. - “Google hasn't verified this app”
- Expected. Advanced → Go to Setu. See the note above.
- My resume link was rejected
- It isn't public. Drive → Share → “Anyone with the link” → Viewer.
- It refuses to send
- Either no resume link is saved, or today's 80 are spent. Ask your assistant to check your profile.
- I want to revoke access
- myaccount.google.com/permissions → find Setu → remove. Immediate, and you don't need to ask us.