Mailsink MCP Server

What the code does

We read the source, 2 d ago · rules ccca72095570

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

# MCP servers communicate over stdio. MAILSINK_API_KEY is required to call
# MailSink APIs at tool-invocation time, but NOT needed for introspection.
ENV MAILSINK_API_KEY=""

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mailsink -- npx -y @mailsink/mcp

{
  "mcpServers": {
    "mailsink": {
      "args": [
        "-y",
        "@mailsink/mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mailsink]
command = "npx"
args = ["-y", "@mailsink/mcp"]

{
  "mcpServers": {
    "mailsink": {
      "args": [
        "-y",
        "@mailsink/mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mailsink": {
      "args": [
        "-y",
        "@mailsink/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: MAILSINK_API_KEY (Your MailSink API key. Get it at https://mailsink.dev/auth/github), MAILSINK_API_URL (Optional API base URL override (defaults to https://api.mailsink.dev)). The author declared them in the registry entry; get the values from the project itself.