Inxmail MCP MCP Server

MCP server for the Inxmail Commerce transactional API — events, sendings, bounces, blocklist, blacklist, reactions, and delivery tracking from Claude.

Local serverstdio

What is the Inxmail MCP MCP server?

MCP server for the Inxmail Commerce transactional API — events, sendings, bounces, blocklist, blacklist, reactions, and delivery tracking from Claude. That is what the inxmail mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Events — The Events tool exposed by this server
  • Sendings — The Sendings tool exposed by this server

What it needs from you

Configuration is passed through the environment: INXMAIL_INSTANCE, INXMAIL_API_KEY_ID, INXMAIL_API_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

The server ships on npm as inxmail-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Inxmail MCP's toolset — Events, Sendings — is a fair guide to whether it matches your workflow. It is maintained by shahabazdev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Inxmail MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
EventsThe Events tool exposed by this server.
SendingsThe Sendings tool exposed by this server.

How to install the Inxmail MCP MCP server

{
  "mcpServers": {
    "inxmail": {
      "command": "npx",
      "args": ["-y", "inxmail-mcp"],
      "env": {
        "INXMAIL_INSTANCE": "your-instance",
        "INXMAIL_API_KEY_ID": "your-key-id",
        "INXMAIL_API_SECRET": "your-secret"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
INXMAIL_INSTANCEConfiguration value read at startup.Optional
INXMAIL_API_KEY_IDCredential the server authenticates with.Yes
INXMAIL_API_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Inxmail MCP to Events.
  • Use Inxmail MCP to Sendings.

Frequently asked questions

`INXMAIL_INSTANCE` (your instance subdomain), `INXMAIL_API_KEY_ID` (your API key ID), and `INXMAIL_API_SECRET` (your API secret) are all required.