How MCP works in plain English
A developer (or company) publishes an MCP server that exposes a set of tools. The user adds the server to their MCP-compatible client, such as Claude Desktop, Claude Code, or any other MCP runner. Claude can then call those tools naturally during a conversation, with the request validated and the response returned in a structured format.
Why MCP matters
MCP standardises tool discovery and invocation so compatible clients can use the same server contract. It does not eliminate the need for authentication, validation, approval policies or error handling.
What MCP tools look like
Tools expose names, descriptions and input schemas. Clients can use those schemas to construct calls; servers still need to validate arguments and enforce authorisation.
MCP and Senddio
Senddio’s @senddio/mcp-server exposes five tools: send_message, get_message_status, list_recent_messages, list_inbound_messages and get_delivery_stats. Use a scoped API key; configure its agent name for attribution.