Ai

SendSoon AI MCP

English | 简体中文 | 日本語

SendSoon MCP is a Model Context Protocol (MCP) server that lets Codex, Claude, and WorkBuddy use SendSoon capabilities: send email, look up public IPs, and convert local documents to Markdown.

Configure it once, then describe tasks in natural language. You usually do not need to mention SendSoon in every prompt.

What you can do

Everyday examples

Send an email to [email protected] with the subject “Meeting reminder” and the body “The meeting starts at 3 PM today.”

Look up the location and ISP for 8.8.8.8.

Convert /path/to/report.pdf to Markdown and summarize the key points.

If the agent does not select a tool automatically, say:

Use the sendsoon MCP to complete this task.

Install in your AI client

The instructions below cover Codex, Claude Desktop, and WorkBuddy.

Codex

Config file: user-level ~/.codex/config.toml (macOS / Linux) or %USERPROFILE%\.codex\config.toml (Windows).

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

[mcp_servers.sendsoon.env]
SENDSOON_API_KEY = ""

Verify: Save the file, restart Codex, and run /mcp in a chat. You should see sendsoon connected. In the desktop app, also check Settings > MCP servers.

First use: Start a new conversation and ask for a simple task (e.g. “Look up 8.8.8.8”). Approve the tool if Codex asks for permission.

Claude Desktop

Config file:

You can also open Settings > Developer > Edit Config inside Claude Desktop.

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

Verify: Save the file, fully quit Claude Desktop (including the system tray), then relaunch. Start a new chat and confirm sendsoon tools appear in the tools menu or settings.

First use: Claude may ask to approve tool access on the first invocation; allow it to continue.

WorkBuddy

WorkBuddy can add SendSoon by pasting the connector JSON directly in MCP Server Management.

Config file: %USERPROFILE%\.workbuddy-ai\mcp.json (Windows) or ~/.workbuddy-ai/mcp.json (macOS / Linux).

1. Open WorkBuddy and go to MCP Server Management.
2. Click Add MCP.
3. Paste the JSON below into the editor. Fill in SENDSOON_API_KEY if you have a Key; leave it empty for the anonymous trial.
4. Click Save.

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

The screenshot shows the WorkBuddy connector editor: the configuration file path is at the top, and the sendsoon JSON is pasted into the editor. After saving, return to the MCP list and confirm sendsoon is connected.

Verify: Start a new conversation and ask for a simple task (e.g. “Look up 8.8.8.8”). Approve the tool if WorkBuddy asks for permission.

Prepare the configuration

Optional environment variable:

Never commit a real Key to Git or share it with anyone.

Get an API Key

1. Sign up or sign in on the SendSoon registration page.
2. Open Profile and generate a Key in the API Key section.
3. Copy the one-time ssk_live_... Key immediately and enter it as SENDSOON_API_KEY in your MCP configuration.
4. Save the configuration and restart your MCP client. Requests with a valid Key do not use the anonymous IP daily quota.

If the anonymous quota is exhausted, send_email will tell you to register and configure a Key. An invalid or revoked Key is rejected and does not fall back to the anonymous quota.

Try it in Google Colab

Skip local setup and try ip_lookup, markitdown_convert, and send_email in the browser.

The notebook calls the same SendSoon HTTP APIs used by these MCP tools.

Visual local testing (MCP Inspector)

To see all three tools in a browser and click through them manually before installing into an AI client, use the MCP Inspector.

Requires Node.js 20+. Run the command below in a terminal; Inspector opens a web UI automatically:

npx @modelcontextprotocol/inspector npx -y @sendsoon/mcp

How to test

1. Wait for MCP Inspector Web is up and running in the terminal. If the browser does not open, paste the http://127.0.0.1:6274?... URL from the terminal.
2. Confirm the page header shows Connected.
3. Open the Tools tab in the top-right area of the page.
4. Select a tool from the list on the left, fill in the parameters, and click Execute Tool.
5. Read the response in the Results panel on the right. On failure, inspect error.code and error.message.

License

See LICENSE.