ABOVO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ABOVO_SMTP_HOST | No | SMTP hostname | smtp.gmail.com |
| ABOVO_SMTP_PASS | Yes | SMTP password or app password | |
| ABOVO_SMTP_PORT | No | SMTP port | 587 |
| ABOVO_SMTP_USER | Yes | SMTP username / email address | |
| ABOVO_SENDER_EMAIL | No | From address (defaults to ABOVO_SMTP_USER) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_to_webA | Publish content to a public web page on ABOVO.co by emailing it through a single, server-configured SMTP identity. Accepts a subject, body, format (text or html), and an optional group. Does NOT support file attachments — the input schema is limited to subject/body/format/group. Returns a confirmation and a link to the sender's ABOVO.co page; it does NOT return the exact URL of the new post (ABOVO.co emails that permanent URL to the sending address separately). Not idempotent: repeated calls create duplicate posts. |
| get_abovo_infoA | Get information about ABOVO.co capabilities, URL formats, groups, or use cases. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| abovo://documentation |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one publishes content, the other provides information about the service. There is no overlap or ambiguity between them.
Both tools follow a verb-first pattern with underscores (publish_to_web, get_abovo_info), though one includes a preposition and the other doesn't. The style is consistent enough to be predictable.
With only two tools, the server feels thin for a general-purpose MCP server. The count is borderline, but the tools are both essential to the server's stated purpose.
The server provides a publish capability but no way to read, update, or delete published posts. The info tool helps users understand the service, but the core workflow lacks lifecycle coverage. The design seems intentional since URLs are emailed separately, but from an MCP perspective, the surface is incomplete.