LOOMAL
Claude DesktopMCP config (JSON)

Email, vault, and TOTP
in Claude Desktop.

Claude Desktop reads MCP servers from a config file. Add Loomal in five lines and Claude can send mail, read its inbox, store credentials, and pass 2FA — all from the desktop chat, no code, no extra app.

No-code MCP installSend / receive email from chatVault for API keysTOTP / 2FA codesWorks on macOS & Windows

Prerequisites

  • Loomal API key (free at console.loomal.ai)
  • Claude Desktop installed (latest version)
  • Node.js 20+ on PATH

Claude Desktop is the easiest place to try Loomal because no code is involved. The desktop app loads MCP servers from a JSON config file at startup; restart Claude and the servers' tools become available in chat.

Adding Loomal here means: ask Claude to send an email and it will. Ask it to check the inbox and it will. Ask it to fetch an API key from the vault for the next request and it will. Useful as a personal assistant; useful as a way to test Loomal before wiring it into a programmatic agent.

1. Get a Loomal API key

Sign up at console.loomal.ai. Create an identity. Copy the API key (loid-...) — you'll paste it into the Claude config in the next step.

shell
# Nothing to install — the API key is the only credential you need.

2. Open Claude's MCP config file

Claude Desktop reads from claude_desktop_config.json. The location depends on your OS:

On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows: %APPDATA%\Claude\claude_desktop_config.json. Open it in any text editor; create it if it doesn't exist.

macOS shell
# Open in your editor of choice
code "$HOME/Library/Application Support/Claude/claude_desktop_config.json"

3. Add Loomal as an MCP server

Add the Loomal block to mcpServers. If the file is empty, paste the full snippet below. If you already have other MCP servers, add the loomal entry alongside them inside mcpServers.

Paste your loid- key into LOOMAL_API_KEY. Don't quote the npx args — the JSON syntax already handles that.

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

4. Restart Claude Desktop

Quit Claude completely (Cmd+Q on macOS — closing the window isn't enough) and reopen it. Claude reads MCP config only at startup, so the new server won't show up until you restart.

After restart, you should see a hammer/tools icon in the chat input area indicating MCP tools are available. Click it and you'll see mail.*, vault.*, and identity.* tools listed.

verification
Look for the tools icon ⚒ in the chat input.
Click it → expand 'loomal' → confirm mail.send, mail.list_messages, vault.get, vault.totp are listed.

5. Use it from chat

Talk to Claude as you normally would. When the conversation needs an email, Claude will call the Loomal tool — you'll see a tool-use indicator and a request for permission the first time.

For TOTP and vault flows, pre-load the secrets via the REST API once. Then ask Claude to use them by label.

example chat prompts
Send a thank-you email to alice@example.com about today's demo.

What's in my inbox right now?

Reply to the latest support email about billing — the answer is that we prorate refunds.

What's the current 2FA code for the label 'crm-totp'?

Things to watch out for

Tools require approval per session

Claude Desktop asks before running a tool the first time per session. This is intentional — get used to it. If you want unattended use, switch to the programmatic Claude Agent SDK guide instead.

Don't put production keys in the desktop config

Anything in claude_desktop_config.json is plaintext on disk in your user library. Use a development identity for desktop; mint separate keys for production agents.

FAQ

Do I need to install @loomal/mcp globally?

No. The npx -y flag fetches it on demand. The first call takes a couple of seconds; later calls are cached. If you want zero startup latency, install it globally and reference it by absolute path.

Can I use multiple Loomal identities in Claude Desktop?

Yes — add a second entry under mcpServers with a different name (e.g. loomal-personal vs loomal-work) and a different API key in env. Each shows up as a separate tool source.

Why don't I see the tools after editing the config?

You probably didn't fully quit Claude. Closing the window keeps it running. Use Cmd+Q on macOS or right-click the tray icon → Quit on Windows, then reopen.

Loomal primitives used

mail.sendmail.list_messagesvault.getvault.totp

Ship it.

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

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