ABOVO.co — Email-to-Web Publishing MCP Server

Publish content to the web by emailing POST@abovo.co. No API key, no signup. SMTP is the API.

Local serverstdio

What is the ABOVO.co — Email-to-Web Publishing MCP Server?

ABOVO.co — Email-to-Web Publishing is an MCP integration. Publish content to the web by emailing POST@abovo.co. No API key, no signup. SMTP is the API.

Packages and local setup

The published mcpb package is https://github.com/seanfenlon/abovo-mcp-server/releases/download/v1.1.1/abovo-mcp-server-1.1.1.mcpb, version 1.1.1. Its declared MCP transport is stdio.

The package declares ABOVO_SMTP_USER (required): SMTP username / sending email address; ABOVO_SMTP_PASS (required): SMTP password or app password; ABOVO_SMTP_HOST: SMTP hostname (default: smtp.gmail.com); ABOVO_SMTP_PORT: SMTP port (default: 587); ABOVO_SENDER_EMAIL: From address (defaults to ABOVO_SMTP_USER).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.1.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
ABOVO_SMTP_USERSMTP username / sending email addressYes
ABOVO_SMTP_PASSSMTP password or app passwordYes
ABOVO_SMTP_HOSTSMTP hostname (default: smtp.gmail.com)Optional
ABOVO_SMTP_PORTSMTP port (default: 587)Optional
ABOVO_SENDER_EMAILFrom address (defaults to ABOVO_SMTP_USER)Optional