Palisade's MCP server is remote (Streamable HTTP at https://api.palisade.email/mcp). This package is a thin local bridge for stdio-based clients, using mcp-remote under the hood. Clients that support remote HTTP MCP servers with a bearer token can point at the URL directly and skip this package.

Get an API key

Create one at app.palisade.email → Settings → API keys, or programmatically via headless signup. See the developer guide.

Use it

Set PALISADE_API_KEY and run:

PALISADE_API_KEY=secret_... npx -y @palisadeemail/mcp

Client config (stdio)

{
  "mcpServers": {
    "palisade": {
      "command": "npx",
      "args": ["-y", "@palisadeemail/mcp"],
      "env": { "PALISADE_API_KEY": "secret_..." }
    }
  }
}

Direct (clients that support remote HTTP MCP)

{
  "mcpServers": {
    "palisade": {
      "type": "http",
      "url": "https://api.palisade.email/mcp",
      "headers": { "Authorization": "Bearer secret_..." }
    }
  }
}

Tools

Accounts (get_account), domains (list_domains, get_domain, add_domain, remove_domain, verify_domain), DNS setup (get_dns_records — the exact records to publish at your own DNS provider), MTA-STS (get_mta_sts, enable_mta_sts), remediation tasks (list_tasks, get_task), groups (list_groups), and billing (get_subscription, start_checkout, get_billing_portal_url).

Palisade tells you which DNS records to publish; you apply them at whatever DNS provider hosts the domain. Payment happens on Stripe-hosted pages.

Environment

PALISADE_API_KEY (required) — your Palisade API key.
PALISADE_MCP_URL (optional) — override the server URL (defaults to https://api.palisade.email/mcp).