Skip to content
mcp/skillhub

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

by seanfenlonio.github.seanfenlon/abovo-mcp-serverv1.1.1

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

0stdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Maintained2mo ago

Install ABOVO.co — Email-to-Web Publishing MCP server

No published package or hosted endpoint yet — see the repository README for build-from-source instructions.

Configuration

VariableRequiredSecretDescription
ABOVO_SMTP_USERyes—SMTP username / sending email address
ABOVO_SMTP_PASSyesyesSMTP 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)

Freshness

Maintained — last maintenance signal 2mo ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-08-01 · 2mo ago · GitHub

  2. Latest release

    2026-08-01 · 2mo ago · GitHub · v1.1.1

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-08-01 · 2mo ago · official registry · v1.1.1

FAQ

›Does ABOVO.co — Email-to-Web Publishing require an API key?

Yes. It expects ABOVO_SMTP_USER, ABOVO_SMTP_PASS, of which 1 is a secret.

›Can I use ABOVO.co — Email-to-Web Publishing as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is ABOVO.co — Email-to-Web Publishing in the official MCP registry?

Yes, as io.github.seanfenlon/abovo-mcp-server.

Alternatives to ABOVO.co — Email-to-Web Publishing

Other email MCP servers.

View all