Back to Glossary Index
Core ConceptEvent / Notification Layer

MCP Notification

Industry Definition Set • Entity Resolution Path: /glossary/mcp-notification

Quick Answer / TL;DR

A one-way JSON-RPC message from server to client (or client to server) that does not expect a response.

Key Takeaways

  • One-way JSON-RPC message with no response expected.
  • No `id` field in the message.
  • Used for events like progress, cancellation, and list changes.
  • Sender does not wait for acknowledgement.
Definitive Statement: A one-way JSON-RPC message from server to client (or client to server) that does not expect a response.

Technical Context & Protocol Usage

Detailed Explanation
Notifications are fire-and-forget messages used for events like `initialized` (client confirms handshake), `cancelled` (server cancels a request), or `progress` (server reports progress). The `id` field is absent, and the receiver must not send a response. Notifications are essential for event-driven workflows in MCP.

Format & Payload Metadata

Format: JSON-RPC message without `id`

Latency: No overhead; one-way delivery

Real-World Implementation Use Case

A server sends a `notifications/progress` notification to update the client on a long-running tool's progress.

M
MCPserver.in Engineering

Platform Team

Published: 2026-07-20
Updated: 2026-07-20

References & Technical Specifications

Cite This Page

MLA Style:

MCPserver.in Engineering. "MCP Notification." MCPserver.in Knowledge Hub, 20 July 2026, mcpserver.in/glossary/mcp-notification.