CommunicationPublic source

Notifications MCP Server

Multi-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.

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.

Provides notifications capabilities through a typed MCP contract.

Architecture

How 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.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Notifications MCP Server

Validates the request and owns 13 documented tool contracts.

→

Domain system

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

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

Notifications MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask 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.

13 named tools

send_notification

Send via any channel (email, sms, push, in_app, webhook, slack)

internal write

send_from_template

Send using template with variable substitution

internal write

broadcast

Send to multiple recipients

internal write

schedule_notification

Schedule for future delivery

internal write

list_notifications

List sent notifications

read only

get_status

Get delivery status

read only

retry_notification

Retry a failed notification

internal write

list_templates

List notification templates

read only

get_template

Get template details

read only

create_template

Create a notification template

internal write

get_preferences

Get user notification preferences

read only

update_preferences

Update user preferences

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.

7 internal write6 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-notifications

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-notifications",
    ["mcp-notifications"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

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.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring