LOOMAL
CursorMCP config (JSON)

Email and credentials
in Cursor's chat.

Cursor's chat sidebar speaks MCP. Add Loomal as an MCP server in mcp.json and the AI in your editor can send email, read replies, fetch credentials from a vault, and pass 2FA — useful for triaging inbox without leaving the IDE, or scripting outbound flows in real-time.

No-plugin installCursor chat tool callsEmail send / receiveVault & TOTPPer-project config

Prerequisites

  • Loomal API key (free at console.loomal.ai)
  • Cursor 0.42+ with MCP support enabled
  • Node.js 20+ on PATH

Cursor added MCP server support to its chat sidebar in late 2024. The chat AI can call MCP tools just like Claude Desktop does — useful for any flow where you want to interleave code and email or credentials in the same editor session.

Adding Loomal here is one JSON edit. After that, the chat can send mail, monitor an inbox, and grab vault entries — handy for things like 'check the deploy notification email and grep the build log for that error', all from inside the editor.

1. Get a Loomal API key

Sign up at console.loomal.ai and create an identity. Copy the API key (loid-...).

If you'll use Loomal in multiple projects, mint one identity per project — that way revoking a project's key doesn't take down the others.

shell
# Copy the loid- key from console.loomal.ai → Identity → API Keys

2. Open Cursor's MCP config

Cursor reads MCP servers from one of two places. Project-scoped: .cursor/mcp.json in the repo root. User-scoped: ~/.cursor/mcp.json in your home directory.

Use project-scoped if you want different identities per repo (recommended). Use user-scoped if you want one shared setup across every workspace.

shell
mkdir -p .cursor
$EDITOR .cursor/mcp.json

3. Add Loomal to mcp.json

Add the loomal entry under mcpServers. Paste your API key into LOOMAL_API_KEY. The structure mirrors the Claude Desktop config, which is intentional — both are MCP clients.

.cursor/mcp.json
{
  "mcpServers": {
    "loomal": {
      "command": "npx",
      "args": ["-y", "@loomal/mcp"],
      "env": {
        "LOOMAL_API_KEY": "loid-your-api-key"
      }
    }
  }
}

4. Reload Cursor's MCP servers

Open Cursor's command palette (Cmd+Shift+P / Ctrl+Shift+P) and run 'MCP: Restart Servers'. The Loomal server starts as a subprocess; tools become available in chat within a couple of seconds.

Open the chat sidebar and check the tools panel — you should see mail.send, mail.list_messages, vault.get, vault.totp, identity.whoami listed under the loomal source.

command palette
Cmd+Shift+P → MCP: Restart Servers
Then Cmd+L (Cursor chat) → tools panel → loomal

5. Use the tools in chat

Ask Cursor's chat to do anything that involves your inbox or stored credentials. The model decides which tool to call; the first call per session prompts for permission.

Combined with Cursor's code tools, you can do useful cross-cutting things: 'check my inbox for the latest deploy notification, grab the URL, then open the relevant route file and confirm the change'.

example chat prompts
Email the latest type errors to my-manager@example.com — copy from the terminal output above.

Check my inbox for any reply from alice@example.com about the API key change.

What's the current TOTP code for the label 'aws-prod'? I need it for the deploy.

Grab the value of vault label 'github-token' and use it in this curl command.

Things to watch out for

Project-scoped config is checked in by default

If .cursor/mcp.json is committed to your repo, your loid- key is in git history. Either gitignore the file (and document the setup in README) or store the key as ${env:LOOMAL_API_KEY} and load it from the shell environment instead.

Tool approvals prompt every restart

Cursor asks for tool-use approval per session. Restarting the editor or restarting MCP servers resets the session. Live with the prompts or switch to YOLO mode if you're comfortable with the risk profile.

FAQ

Can I share the same Loomal config with Claude Desktop?

The config formats are identical, but the file paths differ. You can symlink ~/.cursor/mcp.json to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS to share — but be careful, both apps will edit it independently.

Do MCP tools count against my Cursor model usage?

Tool-call output goes into the model's context window, so yes — long mail.list_messages results consume tokens. For cheap, frequent inbox checks, ask the agent to filter aggressively (labels, since-date) before fetching.

Why does the server fail to start?

Almost always Node.js not on PATH. Cursor doesn't inherit your shell init scripts in some setups. Check by running which node from Cursor's terminal — if empty, set the absolute path to node in the command field.

Loomal primitives used

mail.sendmail.list_messagesvault.getvault.totpidentity.whoami

Ship it.

Free tier, no card. 30 seconds to first email.

Last updated: 2026-04-14 · See also: AutoGen, CrewAI, LangChain