Mailjino MCP Server

Standalone MCP server for any IDE or AI client with MCP support.

It talks to the Mailjino Agent API over HTTPS using a scoped Bearer API key.

What It Is For

Mailjino MCP exists for development-time automation.

Use it when an AI agent needs to:

• provision Mailjino backend configuration for a website
• create or update the backend site, recipient mailbox, and form mapping
• fetch the exact public endpoint and integration snippets required to patch website code

Do not use it for runtime customer submissions.

Production websites must submit directly to the public Mailjino endpoint returned by the integration bundle. The Agent API key must stay inside the MCP runtime or another trusted environment and must never be exposed to browser code.

Install

npm install -g mailjino-mcp

Run

MAILJINO_AGENT_API_KEY=your_agent_api_key \
mailjino-mcp

Generic MCP config

{
  "mcpServers": {
    "mailjino": {
      "command": "mailjino-mcp",
      "env": {
        "MAILJINO_AGENT_API_KEY": "your_agent_api_key"
      }
    }
  }
}

Agent API base URL is hardcoded to https://da1473771a5.vps.myjino.ru.

Tools

• mailjino_get_usage_guide Explains why the MCP server exists, when to use each tool, the recommended workflow, and the form-field alias guide used in notification emails.
• mailjino_provision_form Default one-shot tool. Creates or updates the site, recipient mailbox, and form in one idempotent call, then returns the integration bundle.
• mailjino_create_site Lower-level tool for managing the site record only.
• mailjino_create_recipient_mailbox Lower-level tool for managing the recipient mailbox only.
• mailjino_create_form Lower-level tool for managing the form mapping only after the site and mailbox already exist.
• mailjino_get_integration_bundle Fetches the public endpoint and code snippets for an already existing form.

Notification Field Aliases

Mailjino notification emails map common technical field names to readable labels in Russian.

• Matching supports snake_case, kebab-case, and camelCase.
• Unknown keys are shown with a readable fallback label instead of being dropped.

Examples:

• name, firstName, full_name -> Имя / Имя и фамилия
• email, emailAddress -> Email
• phone, mobile, tel -> Телефон
• company, organization -> Компания
• message, comment, details -> Сообщение / Комментарий / Детали
• preferredContactTime, callback_time -> Удобное время для связи / Время для звонка
• utm_source, utm_medium, utm_campaign, utm_term, utm_content -> UTM Source/Medium/Campaign/Term/Content
• gclid, yclid, fbclid, referrer -> click-id and referrer labels

Complete alias catalog is available directly from mailjino_get_usage_guide in submissionFieldAliasGuide.

Recommended Agent Workflow

1. Call mailjino_get_usage_guide if the agent is unsure which Mailjino tool to use.
2. In the common case, call mailjino_provision_form.
3. Read the returned endpoint, htmlSnippet, javascriptSnippet, and agentPrompt.
4. Patch the existing website form without changing its visual design unless needed.
5. Use mailjino_get_integration_bundle later when provisioning is already done and only the website code needs updating.