Skip to main content
Glama
enesjakozh
r3-yamauchi

blastengine-mailer

by r3-yamauchi
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

blastengine-mailer MCP Server

Blastengine APIを使用してメールを送信するModel Context Protocol (MCP) サーバー

このJavaScriptベースのMCPサーバーは、LLM（大規模言語モデル）がBlastengine APIを通じてメールを送信できるようにします。

機能

ツール

  • send_email - Blastengine APIを使用してメールを送信

    • 必須パラメータ:

      • to: 送信先メールアドレス

      • from: 送信元メールアドレス

      • subject: メールの件名

      • text: メール本文

    • 送信成功時はdelivery_idを返します

    • エラー時は詳細なエラーメッセージを返します

Related MCP server: Scrapbox MCP Server

前提条件

  • Node.js (ESモジュール対応)

  • Blastengine APIアカウントとAPIキー

開発

依存関係のインストール:

npm install

サーバーのビルド:

npm run build

開発時の自動リビルド:

npm run watch

インストールと設定

Claude Desktopでの使用

Claude Desktopで使用するには、以下の設定ファイルにサーバー設定を追加します:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "blastengine-mailer": {
      "command": "node",
      "env": {
        "BLASTENGINE_USER_ID": "userid-of-blastengine",
        "BLASTENGINE_API_KEY": "apikey-of-blastengine"
      },
      "args": [
        "/path/to/blastengine-mailer/server.js"
      ]
    }
  }
}

デバッグ

MCPサーバーはstdio経由で通信するため、デバッグが困難な場合があります。MCP Inspectorの使用を推奨します:

npm run inspector

インスペクターは、ブラウザでデバッグツールにアクセスするためのURLを提供します。

使用例

Claude Desktopで設定後、以下のようにメールを送信できます:

「test@example.comに『テストメール』という件名でメールを送信して」

ライセンス

このプロジェクトはプライベートプロジェクトです。

Available Tools

1 tool
send_emailC

Send an email using Blastengine API

ParametersJSON Schema
NameRequiredDescriptionDefault
fromYesSender email address
subjectYesEmail subject
textYesEmail body
toYesRecipient email address

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the API but fails to describe critical traits like rate limits, authentication requirements, error responses, or whether the email is sent immediately or queued. This leaves significant gaps for an agent to understand operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words, front-loading the core purpose. It is appropriately sized for a straightforward tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of an email-sending tool with no annotations and no output schema, the description is inadequate. It lacks details on behavioral traits, error handling, and response format, leaving the agent with incomplete context for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with clear documentation for all four parameters (from, to, subject, text). The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high coverage without extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Send an email') and the resource ('using Blastengine API'), providing a specific verb+resource combination. However, with no sibling tools mentioned, there's no opportunity to distinguish from alternatives, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool, such as for transactional vs. marketing emails, prerequisites like API setup, or error handling scenarios. It simply states what the tool does without context for application.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'send_email' has a clear and distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The naming is trivially consistent as there is only one tool, 'send_email', which follows a clear verb_noun pattern. There are no other tools to compare against, so no inconsistency can exist.

Tool Count2/5

A single tool is too few for a mailer server's apparent scope, which typically involves operations like listing emails, managing templates, or checking statuses. This minimal set limits functionality and may cause agent failures due to lack of essential operations.

Completeness2/5

The tool surface is severely incomplete for an email service domain. While 'send_email' covers a core action, there are significant gaps such as retrieving sent emails, managing recipients, handling attachments, or error checking, which are essential for comprehensive email workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Email Sending MCP

    resend
    A
    license
    A
    quality
    A
    maintenance
    A simple MCP server that enables users to send emails using Resend's API, integrating with tools like Cursor and Claude Desktop for seamless email composition and delivery.
    102
    21,862
    566
    MIT

  • protonmail-mcp

    amotivv
    A
    license
    Not graded
    quality
    D
    maintenance
    This MCP server provides email sending functionality using Protonmail's SMTP service. It allows both Claude Desktop and Cline VSCode extension to send emails on your behalf using your Protonmail credentials.
    50
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/r3-yamauchi/mcp-server-blastengine-mailer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server