Mursa MCP
Allows reading, searching, and sending emails through Gmail, including listing emails, getting details, retrieving attachments, searching, sending replies, and composing new messages.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Mursa MCPList my tasks for today"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mursa MCP
Connect Claude Code, Claude Desktop, Cursor, or any MCP-compatible client to your Mursa tasks, calendar, goals, notes, habits, projects, and Gmail.
📖 Full guide with screenshots: https://mursa.me/mcp
60-second install
1. Get an API key
Open dashboard.mursa.me and sign in.
Go to Settings → API keys.
Click New key → pick a label, expiry, and scopes → Create.
Copy the key (starts with
mursa_mcp_…). You'll only see it once.
2. Add to your client
Claude Code (~/.claude.json)
{
"mcpServers": {
"mursa": {
"command": "npx",
"args": ["-y", "mursa-mcp"],
"env": { "MURSA_API_KEY": "mursa_mcp_…" }
}
}
}Restart Claude Code, run /mcp to confirm, call whoami to verify.
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
or %APPDATA%/Claude/claude_desktop_config.json (Windows) with the same block,
then restart the app.
Cursor
Settings → MCP → Add new MCP server, same JSON block.
3. That's it
Your agent now has access to whatever scopes your key has.
Related MCP server: Google Workspace MCP
Tools (28)
Group | Tools | Scope |
Meta |
| (any) |
Tasks (read) |
|
|
Tasks (write) |
|
|
Calendar |
|
|
Goals |
|
|
Notes |
|
|
Habits |
|
|
Projects |
|
|
|
| |
|
|
* as a scope grants everything.
Security
API keys are sha256-hashed at rest — the raw value is never stored.
Per-key scopes + expiry. Revoke any key instantly from the dashboard.
Per-action rate limits (60/min reads, 30/min writes, 5/min email send).
Every call audit-logged for 90 days (action, status, latency, IP — no payload).
Email attachments capped at 3 MB each / 10 MB total per email.
All traffic goes through
mursa.me/api/mcp; the Supabase function is gated by a shared proxy secret so direct hits return 403.
Run from source (advanced)
git clone https://github.com/Murali1889/Prod-Mursa.git
cd Prod-Mursa/mcp-servers/mursa
npm install
echo 'MURSA_API_KEY=mursa_mcp_…' > .envThen point your client at the absolute path:
{
"mcpServers": {
"mursa": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/mursa/server.js"]
}
}
}Override the endpoint for preview deployments or local dev:
MURSA_API_URL=https://mursa-preview.vercel.app/api/mcp(Default is https://mursa.me/api/mcp.)
Troubleshooting
Symptom | Fix |
| Mint a fresh key in the dashboard, swap |
| Your key wasn't granted that scope at mint time. Revoke and mint a new one with the scope checked. |
| Connect Gmail from the Mursa app first. |
| Slow down — strict throttle on outbound mail. |
For server-side deployment (running your own Mursa instance), see DEPLOY.md.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Murali1889/MCP-mursa'
If you have feedback or need assistance with the MCP directory API, please join our Discord server