ADK-Rust
← MCP server registry
CommunicationPublic source

Messaging & Notifications MCP Server

Full-stack messaging for ADK-Rust Enterprise agents. Provides 20 MCP tools covering push notifications, SMS (4 regional providers), webhooks, in-app messaging with rich media, message queues, and broadcasts.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

01

Global SMS coverage — Africa's Talking, Twilio, Vonage, Sinch cover every continent.

02

Free push notifications — ntfy.sh requires zero configuration or API keys.

03

Rich messaging — HTML, images, video, audio, files, locations, reply threading.

04

Message lifecycle — send → deliver → read receipt → recall.

05

Built-in queues — priority-based message queues for async job dispatch.

06

Registry-ready — ships with mcp-server.toml for automatic ADK-Rust Enterprise onboarding.

Architecture

How Messaging & Notifications MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

Messaging & Notifications MCP Server

Validates the request and owns 20 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.

Tool catalog

What can an agent ask Messaging & Notifications MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

11 named tools shown from 20 documented tools

send_push

Send push notification via ntfy.sh

internal write
broadcast

Broadcast to multiple topics

internal write
send_sms

Send SMS via Twilio

internal write
fire_webhook

POST event to webhook URL

internal write
create_channel

Create messaging channel

internal write
send_message

Send in-app message

internal write
get_messages

Get channel messages

read only
enqueue

Add message to queue

internal write
dequeue

Remove messages from queue

internal write
queue_status

Get queue depth and status

read only
subscribe_webhook

Subscribe webhook to topic

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

9 internal write2 read only
  • The registry manifest declares internal write, read only tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install
cargo install mcp-messaging
MCP client configuration
{
  "mcpServers": {
    "messaging": {
      "command": "mcp-messaging",
      "env": {
        "AT_USERNAME": "your_username",
        "AT_API_KEY": "your_key"
      }
    }
  }
}

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.mdCHANGELOG ↗CHANGELOG.mdIssues and support ↗github.com issues

Keep exploring

More in communication.

Calendar MCP ServerThe most complete multi-backend calendar MCP server. 12 tools across 2 backends — manage events on Google Calendar and Microsoft Outlook with OAuth auto-refresh, natural language quick-add, and enterprise governance.…12 toolsEmail MCP ServerThe most complete multi-backend email MCP server. 24 tools across 5 send backends and 3 read backends — send via SMTP, AWS SES, or SendGrid while reading from any IMAP server. File attachments, OAuth with auto-refresh,…24 toolsNotifications MCP ServerMulti-channel notifications for AI agents — email, SMS, push, in-app, webhooks, Slack. Templates with variable substitution, broadcasting, user preferences, quiet hours, and delivery tracking. 13 tools.13 tools

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
1.4.0
License
Apache-2.0
Tools
20
Revision
465fdd891372
Updated
May 27, 2026
Transportsstdio