Mailjet Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

MCP server for Mailjet: contacts, messages, campaigns. Needs free API keys.

VerifiedSTDIODesktop onlyCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant work with Mailjet contacts, messages, and campaigns through a local MCP server.

What you can do
This is a local MCP server for Mailjet, an email marketing and delivery service. According to its registry description, it covers contacts, messages, and campaigns, so an assistant can work with those Mailjet resources on the user's behalf. No tool list is published, so the exact operations are not documented here.
When to use it
Worth considering when you already use Mailjet and want an assistant to help manage contacts, messages, or campaigns without leaving the chat. If you do not use Mailjet, or you need a documented tool list before installing, this server is not a good fit.
Requirements
Runs as a local process on the user's machine, installed from the npm package mailjet-mcp over stdio. The description says free Mailjet API keys are needed; no environment variables or headers are declared in the manifest, so how credentials are supplied is not specified. Desktop only.
Before you install
It requires Mailjet API keys, which are credentials for an account that can send email and hold contact data. The manifest declares no environment variables or headers, so it is unclear how those keys are passed or stored. No tool list is published, so what the server can read, send, or change in your Mailjet account cannot be verified from this listing.

Installation

In SourceWeft

  1. Open Mailjet Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.1LatestOct 17, 2026
  2. v1.0.0Sep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.