Email, vault, and 2FA
for Claude Agent SDK agents.

1. Provision a Loomal identity

Sign up at console.loomal.ai and create an identity. You'll get an API key in the form loid-... and a routable email address like agent-x8k2m@loomal.ai. The identity is the principal your agent will act as — every email it sends will be from this address, and every vault entry will be scoped to this identity.

Keep the API key in your local environment for development. In production, mint a separate identity per deployment so you can revoke them independently.

export LOOMAL_API_KEY="loid-your-api-key"
export ANTHROPIC_API_KEY="sk-ant-..."

2. Install the Loomal MCP server

The MCP server runs as a subprocess of the Claude Agent SDK. You don't need to install it globally — npx will fetch the latest version on every run, which keeps tool schemas up to date as new primitives are added.

npm install @anthropic-ai/claude-agent-sdk
npx -y @loomal/mcp --version  # warm the cache

3. Register the MCP server with the SDK

The Claude Agent SDK accepts MCP servers in its options. Each server is launched as a subprocess; the SDK handles the JSON-RPC handshake and exposes every tool the server advertises to the model.

Setting allowedTools is optional but recommended. By default the model can call any tool the MCP server provides; if you only want this agent sending email (not deleting messages, for example), restrict the surface explicitly.

import { query } from "@anthropic-ai/claude-agent-sdk";

const result = query({
  prompt: "Send a follow-up email to alice@example.com thanking her for the demo today.",
  options: {
    mcpServers: {
      loomal: {
        command: "npx",
        args: ["-y", "@loomal/mcp"],
        env: { LOOMAL_API_KEY: process.env.LOOMAL_API_KEY! },
      },
    },
    allowedTools: [
      "mcp__loomal__mail_send",
      "mcp__loomal__mail_list_messages",
      "mcp__loomal__mail_reply",
    ],
  },
});

for await (const message of result) {
  console.log(message);
}

4. Read inbound mail and reply in-thread

Replies happen in the same thread automatically — you don't manage In-Reply-To headers, and the model doesn't need to either. mail.list_messages with labels=unread gives the agent its work queue; mail.reply sends a response that lands in the right thread on the recipient's side.

const result = query({
  prompt: "Check unread support emails. Answer billing questions yourself, label anything else 'needs-human'.",
  options: {
    mcpServers: { loomal: { command: "npx", args: ["-y", "@loomal/mcp"], env: { LOOMAL_API_KEY: process.env.LOOMAL_API_KEY! } } },
    allowedTools: [
      "mcp__loomal__mail_list_messages",
      "mcp__loomal__mail_get_thread",
      "mcp__loomal__mail_reply",
      "mcp__loomal__mail_update_labels",
    ],
  },
});

5. Use the vault for credentials and 2FA

If your agent needs to log into a service that requires 2FA, store the TOTP secret in the vault once and call vault.totp(label) whenever a code is needed. The shared secret never returns in plaintext; the agent only sees the current six-digit code.

Store API keys for downstream services the same way. The vault is scoped to this identity, so revoking the identity revokes every credential in one operation — no manual cleanup.

// One-time setup (run from your dev box, not the agent):
//   curl -X POST https://api.loomal.ai/v0/vault \
//     -H "Authorization: Bearer $LOOMAL_API_KEY" \
//     -d '{"label": "crm-totp", "otpauth": "otpauth://totp/..."}'

// In the agent prompt, instruct the model to call vault.totp when needed:
const result = query({
  prompt: "Log into the CRM. The TOTP secret label is 'crm-totp'. Pull yesterday's leads.",
  options: {
    mcpServers: { loomal: { command: "npx", args: ["-y", "@loomal/mcp"], env: { LOOMAL_API_KEY: process.env.LOOMAL_API_KEY! } } },
    allowedTools: [
      "mcp__loomal__vault_get",
      "mcp__loomal__vault_totp",
      "mcp__loomal__mail_list_messages",
    ],
  },
});